NetBackup 7.0.1 and above attempts to use the PBX port for connections, after delays, will fall back to vnetd, daemon, and legacy ports.

Problem

NetBackup 7.0.1 and above attempts to use the PBX port for connections before falling back to vnetd, daemon, and legacy ports.

Error Message

None.  However the debug log for the process, typically bpbrm, will show delays making the connection to the daemon or legacy ports if the PBX is not running on the remote host or port 1556 is not open through the network.

11:43:11.582 [14365] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1998] VN_REQUEST_SERVICE_SOCKET 6 0x6
11:43:11.582 [14365] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2012] service bpcd
...delay while attempting the PBX port before attempting the vnetd port
11:43:19.902 [14365] <2> logconnections: BPCD CONNECT FROM 1.1.1.1.35062 TO 3.3.3.3.13724 fd = 4
11:43:19.910 [14365] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 146 0x92
11:43:19.966 [14365] <8> do_vnetd_service: [vnet_connect.c:2038] connect VNETD CONNECT FROM 1.1.1.1.35064 TO 3.3.3.3.13724 fd = 5
11:43:19.967 [14365] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:443] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
11:43:19.976 [14365] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:460] ipc_string /tmp/vnet-21960396028831262520000000000-Eyaa5Q

 

Solution

Overview:

After applying the NB_7.0.1 release update, the default destination port changes for most legacy connections.  The initial attempt to connect is made to the PBX port.  If a firewall or other issue prevents the connection, it reverts to the legacy connect option selection, which makes it reverse compatible with NetBackup versions 7.0, 6.5, and 6.0.

Note: The NB_7.0.1 release update also contains a new version of PBX.

Troubleshooting:

The bptestbpcd command (servers) and bptestnetconn (servers and clients) and NetBackup debug logs show when port 1556 is used in place of 13724 or other daemon ports.  For example:

# admincmd/bptestbpcd
1 1 1
10.80.74.69:51164 -> 10.80.74.69:1556
10.80.74.69:51165 -> 10.80.74.69:1556

If a firewall does not permit connections to vnetd and daemon ports, the PBX port must be used.  You should then enable logging for PBX (product id 50936) OID 103 and NetBackup (product id 51216) OID 137.
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)