1. Support
  2. Knowledge base
  3. 100037973

Using bptestnetconn to test connectivity between NetBackup hosts

Article: 100037973
Last Published: 2013-04-30
Ratings: 0 2
Product(s): NetBackup & Alta Data Protection

Description

The information below is accurate for the specific version of NetBackup that is targeted.  The details relevant to each NetBackup version can be found in this article:

000017676
Best Practices for bptestnetconn including arguments and outputs by NetBackup version

Using the following command can test a connection from a NetBackup host, a master server for example, to another NetBackup host, like a media server and to a service that should be running on that host. Here is an example command:

$ bptestnetconn -v -cnbrmms/DiskPollingService.DPS -t 10 -o 5 -H mymm
 
If there is a perceived problem with the master server polling disk pools on a media server, a test to the nbrmms service can be done.  This example shows SUCCESS, so the remote host is reachable and the service is running.
 
$ bptestnetconn -v -cnbrmms/DiskPollingService.DPS -t 10 -o 5 -H mymm
adding hostname = mymm
------------------------------------------------------------------------
Connecting to 'nbrmms/DiskPollingService.DPS'
CN: mymm :     80 ms  [SUCCESS] PBX: Yes VNETD: Yes BPCD: Yes
------------------------------------------------------------------------
Total elapsed time: 0 sec
 
 
The connection test will make a connection to PBX which is passed to the nbrmms service.  Here is what the behavior should look like in the logs when a successful connection is made:
 
From the PBX debug log on from the media server:
Log Location: -
If Unix/Linux server: - /opt/VRTSpbx/log/
If Windows server: - C:\Program Files (x86)\VERITAS\VxPBX\log\
 
12/07/2011 07:58:08.013 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Manager:: handle_input with fd = 7
12/07/2011 07:58:08.013 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] hand_off looking for proxy for =
12/07/2011 07:58:08.013 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Warning] No proxy found.
12/07/2011 07:58:08.013 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Client_Proxy::handle_close
12/07/2011 07:58:08.024 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Manager:: handle_input with fd = 7
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Client_Proxy::parse_line, line = ack=1  From 10.10.6.101
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Client_Proxy::parse_line, line = extension=nbrmms  From 10.10.6.101
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] hand_off looking for proxy for = nbrmms
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] is_accepting about to return true
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] Client Expects an ACK, sent one.
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] Proxy found.
12/07/2011 07:58:08.025 [Application] VxICS 50936 103 PID:2591 TID:47774493297840 File ID:103 [No context] [Info] PBX_Client_Proxy::handle_close
 

Because the connection to PBX is passed to the nbrmms service, the nbrmms debug log will show the connection arriving from the IP address of the master server.

Log Location: -
For Unix/Linux server: - /usr/openv/logs/nbrmms
For Windows: - <install path>\netbackup\logs\nbrmms
 
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1370: 1123518784: found in cache name: 10.10.6.101
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1371: 1123518784: found in cache service: NULL
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1370: 1123518784: found in cache name: 10.10.6.101
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1371: 1123518784: found in cache service: NULL
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1514: 1123518784: found in file cache name: masterserver.name.local
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1515: 1123518784: found in file cache service: NULL
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1370: 1123518784: found in cache name: 10.10.6.101
12/07/2011 07:58:08.027 [Debug] NB 51216 libraries 137 PID:28355 TID:1123518784 File ID:222 [No context] 1 [vnet_cached_getaddrinfo_and_update] ../../libvlibs/vnet_addrinfo.c.1371: 1123518784: found in cache service: NULL 
 
 
The verbose (-v) argument to bptestnetconn also caused a connection to the bpcd process on the media server.  This is a single connection to prove bpcd is reachable, and does not attempt to bring up a a call-back connection so the bpcd debug log shows the initial connection and then a failure when bptestnetconn closes the initial socket without providing the information for the call-back connection.
 
Log Location: -
For Unix/Linux server: - /usr/openv/netbackup/logs/bpcd
For Windows: - <install path>\netbackup\logs\bpcd
 
07:58:08.020 [20273] <2> logconnections: BPCD ACCEPT FROM 10.10.6.101.33729 TO 10.10.6.102.13782 fd = 0
...snip...
07:58:08.028 [20273] <2> bpcd peer_hostname: Connection from host masterserver.name.local (10.10.6.101) port 33729
07:58:08.028 [20273] <2> bpcd valid_server: comparing masterserver.name.local and masterserver.name.local
07:58:08.028 [20273] <4> bpcd valid_server: hostname comparison succeeded
07:58:08.028 [20273] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1514: 0: found in file cache name: masterserver.name.local
07:58:08.028 [20273] <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1515: 0: found in file cache service: NULL
07:58:08.028 [20273] <16> process_requests: read failed: No such file or directory
 
 
Similarly the verbose (-v) argument also causes a connection to the vnetd service on the media server.  Once the connection is complete, bptestnetconn closes the connection without negotiating the vnetd protocol or sending across a vnetd command as show in the vnetd debug log on the media server.
 
Log Location: -
For Unix/Linux server: - /usr/openv/netbackup/logs/vnetd
For Windows: - <install path>\netbackup\logs\vnetd
 
07:58:08.015 [20272] <2> ProcessRequests: vnetd.c.587: 0: msg: VNETD ACCEPT FROM 10.10.6.101.41796 TO 10.10.6.102.13724 fd = 9
07:58:08.015 [20272] <2> vnet_pop_byte: ../../libvlibs/vnet.c.1159: 0: errno: 0 0x00000000
07:58:08.015 [20272] <2> vnet_pop_byte: ../../libvlibs/vnet.c.1161: 0: Function failed: 9 0x00000009
07:58:08.015 [20272] <2> vnet_pop_string: ../../libvlibs/vnet.c.1241: 0: Function failed: 9 0x00000009
07:58:08.015 [20272] <2> vnet_pop_signed: ../../libvlibs/vnet.c.1285: 0: Function failed: 9 0x00000009
07:58:08.015 [20272] <2> vnet_version_accept: vnetd.c.1023: 0: Function failed: 9 0x00000009
07:58:08.015 [20272] <2> ProcessRequests: vnetd.c.591: 0: version_accept failed: 9 0x00000009
07:58:08.015 [20272] <2> main: vnetd.c.519: 0: ProcessRequests returned: 9 0x00000009
 
   
The bptestnetconn program can be used to test connectivity to any valid CORBA using service/object.  See the Related Articles for a list of some of the services and objects.
 
 
All configured NetBackup servers can be tested at one time by replacing the host (-H host) argument with the server (-s) argument.
 
$ bptestnetconn -v -c -o 5 -t 10 -s
SERVER = mymaster
SERVER = myadmin
SERVER = myoldmm
MEDIA_SERVER = mymm
------------------------------------------------------------------------
Connecting to 'nbsl/HSFactory'
CN:    mymaster : 11 ms  [SUCCESS] PBX: Yes VNETD: Yes BPCD: Yes
CN:     myadmin :  4 sec [TRANSIENT] PBX: Yes VNETD: Yes BPCD: Yes
CN:     myoldmm :  4 sec [TRANSIENT] PBX: No VNETD: No BPCD: No
CN:        mymm : 12 ms  [SUCCESS] PBX: Yes VNETD: Yes BPCD: Yes
------------------------------------------------------------------------
Total elapsed time: 17 sec
 
 
In the above example, the orbtimeout (-t 10) and orbobjtimeout (-o 5) arguments were specified. These limit the time permitted for the connection to the PBX and the service/object respectively.  When a connection fails, the length of the timeout will indicate which portion of the connection failed.
 
In the above test we see two hosts with SUCCESS and two hosts with TRANSIENT. The myadmin host is showing TRANSIENT because it does not run the nbsl service because it is a Windows Administration Console host.  The myoldmm host is on the network, but both PBX and NetBackup are shutdown, ideally this host should be removed from the NetBackup configuration.  The 4 second timeout confirms that a network route exists, but that the service and/or object was not available.

Was this content helpful?

Article Languages