Client doesn't see images - RedHat

If bpclntcmd -pn is not working then there is comms issue between client and master.

Have you checked PBX port (1556) - this must be opened both ways!

PBX port is working

and filesystem backup is running properly

[root@P001 ~]# telnet -e q bknbu 1556

Telnet escape character is 'q'.

Trying 164.26.211.178...

Connected to bknbu (164.26.211.178).

Escape character is 'q'.

root@bknbub:/root# telnet p001bk 1556

Trying 2.142.33.11...

Connected to p001bk.

Escape character is '^]'.

Check bp.conf on client.

Ensure master is 1st SERVER entry.

The ports are also wrong - you need 1556 (PBX) and 13724 (vnetd).

See http://www.symantec.com/docs/TECH136090

The vnetd process is still listening on TCP port 13724 but also registered with PBX.  Connections that previously contacted the vnetd port will now prefer to use PBX port 1556.  If the PBX port is unreachable, then the vnetd port will be used.  Note that the Java console to master server uses the vnetd port for connection to bpjobd and the PBX port for all other connections.  For efficiency, internal sockets on the loopback interface to processes on the same host use the daemon ports instead of passing through vnetd or PBX.

See page 105 in the Symantec NetBackup 7.5 Security and Encryption Guide

http://www.symantec.com/docs/DOC5185

or 

http://www.symantec.com/docs/TECH136090

quote: 

The vnetd process is still listening on TCP port 13724 but also registered with PBX.  Connections that previously contacted the vnetd port will now prefer to use PBX port 1556.  If the PBX port is unreachable, then the vnetd port will be used.  Note that the Java console to master server uses the vnetd port for connection to bpjobd and the PBX port for all other connections.  For efficiency, internal sockets on the loopback interface to processes on the same host use the daemon ports instead of passing through vnetd or PBX.

On the master run:

bpclntcmd -hn <client_name>

The IP that is returned must be the IP that the client uses

Run on client

bpclntcmd -ip <ip returned by master of your client name>

is it your client name?

On Client run:

bpclntcmd -hn <master hostname>

Is it returning the correct IP address of the master?

bpclntcmd -ip <ip of master>

is it the returning the master name?

Please bear in mind that comms when initiated from a client is a bit different to server-initiated comms.

Client needs to connect to the master's bprd process (via vnetd or PBX) in order to list images.

The only way it 'knows' where to connect to, is the 1st SERVER entry in bp.conf.

Please double-check client's config. From master, run:

bpgetconfig -M <client-name>

Please create bplist log folder, then run bplist command again. Check bplist log.

I have just done a test. This is what I get in my bplist log file:

<couple of lines with failed host_cache details - since I haven't tried to connect lately...>
16:24:58.449 [6488.6116] <2> vnet_pbxConnect: pbxConnectEx Succeeded
16:24:58.463 [6488.6116] <2> logconnections: BPRD CONNECT FROM 10.5.1.170.51178 TO 10.5.4.130.1556 fd = 456

PS: You may want to add VERBOSE = 5 to client's bp.conf for additional troubleshooting.

root@bknbub:/export/home/makacmar# bptestbpcd -verbose -client p001bk

1 1 1

164.26.211.179:43275 -> 2.142.33.11:1556

164.26.211.179:43279 -> 2.142.33.11:1556

PEER_NAME = bknbua

HOST_NAME = p001bk

CLIENT_NAME = p001bk

VERSION = 0x07100000

PLATFORM = linuxR_x86_2.6

PATCH_VERSION = 7.1.0.3

SERVER_PATCH_VERSION = -1.-1.-1.-1

MASTER_SERVER = bknbu

EMM_SERVER = bknbu

164.26.211.179:43305 -> 2.142.33.11:1556

root@bknbub:/export/home/makacmar#

i have found that client is listening via pbx port, and not via vnetd

that is ok

master server is first in bp.conf

when i try to:

from master:

root@bknbua:/root# telnet p001bk vnetd
Trying 2.142.33.11...
Connected to p001bk.
Escape character is '^]'.
 

i cannot close connection

in hosts poperties on master server in client attributes i have set in connection options

BPCD connect back: VNETD port

but this doesn't help

from client port is listening:

[root@P001 ~]# telnet -e q bknbu 13724

Telnet escape character is 'q'.

Trying 164.26.211.178...

Connected to bknbu (164.26.211.178).

Escape character is 'q'.

root@bknbua:/root# bptestbpcd -verbose -client p001bk
1 1 1
164.26.211.178:54934 -> 2.142.33.11:1556
164.26.211.178:54938 -> 2.142.33.11:1556
PEER_NAME = bknbu
HOST_NAME = p001bk
CLIENT_NAME = p001bk
VERSION = 0x07100000
PLATFORM = linuxR_x86_2.6
PATCH_VERSION = 7.1.0.3
SERVER_PATCH_VERSION = -1.-1.-1.-1
MASTER_SERVER = bknbu
EMM_SERVER = bknbu
164.26.211.178:54942 -> 2.142.33.11:1556