Problem

Executing the command "vmoprcmd -h MASTER_SERVER" from a media server results in Media Manager Status Code 39.

Error
network protocol error (39)

Solution
As an example, where the master server's name is northpeak and the media server's name is dali, when executing the command
vmoprmcd -h northpeak on the host dali

the following is what results:

root@dali:/# vmoprcmd -h northpeak network protocol error (39)

Examining the /usr/openv/volmgr/debug/daemon log on northpeak shows:

12:56:31.397 [2495] <2> mm_accept_daemon_socket: netconf.c.1336: accept()ed traditional connection from 10.82.105.97 12:56:31.398 [2495] <2> vmd: could not set TCP_NODELAY 12:56:31.398 [2495] <4> peer_hostname: Connection from host dali.min.veritas.com, 10.82.105.97, port 30027 12:56:31.398 [2495] <2> pooldb_name_to_num: poolnum for Scratch is 4 12:56:31.400 [2495] <4> validate_host: hostname comparison succeeded 12:56:31.403 [2495] <2> vauth_acceptor: vauth_comm.c.356: no methods for address: no authentication required 12:56:31.403 [2495] <2> listen_loop: connection is not authenticated, but being accepted from allowed server dali.min.veritas.com 12:56:31.412 [2495] <2> vnet_check_vxss_server_magic: vnet_vxss_helper.c.452: VxSS magic: 661292220 0x276a84bc 12:56:31.412 [2495] <2> vnet_check_vxss_server_magic: vnet_vxss_helper.c.453: remote_vxss: 43 0x0000002b 12:56:31.414 [2495] <2> vnet_check_vxss_server_magic: vnet_vxss_helper.c.481: Client ignores/server requires VxSS auth: 38 0x00000026 12:56:31.415 [2495] <16> process_request: vnet_check_vxss_server_magic(dali.min.veritas.com) failed: 38 12:56:31.415 [2495] <16> listen_loop: abnormal exit: 58

A situation could exist where the VERITAS NetBackup (tm) master server's bp.conf file could contain the following NetBackup Access Control (NBAC) related entries:
USE_VXSS = AUTOMATIC VXSS_NETWORK = northpeak.min.veritas.com REQUIRED VXSS_NETWORK = dali.min.veritas.com REQUIRED

AUTHENTICATION_DOMAIN = northpeak.min.veritas.com "passwd lookups for northpeak" PASSWD northpeak 0 AUTHENTICATION_DOMAIN = min.veritas.com "NIS lookups for min.veritas.com" NIS northpeak 0 AUTHENTICATION_DOMAIN = ENTERPRISE "Windows Domain lookups for ENTERPRISE" WINDOWS ferello.min.veritas.com 0 AUTHORIZATION_SERVICE = northpeak 0

These entries are the typical entries that would be expected. The basic principle behind these entries is as follows: The following indicates that VxSS/NBAC should be automatically detected and used:
USE_VXSS = AUTOMATIC

The following two entries indicate that for the hosts specified, VxSS/NBAC must be used:
VXSS_NETWORK = northpeak.min.veritas.com REQUIRED VXSS_NETWORK = dali.min.veritas.com REQUIRED

The following three entries indicate which host is performing each type of authentication:
AUTHENTICATION_DOMAIN = northpeak.min.veritas.com "passwd lookups for northpeak" PASSWD northpeak 0 AUTHENTICATION_DOMAIN = min.veritas.com "NIS lookups for min.veritas.com" NIS northpeak 0 AUTHENTICATION_DOMAIN = ENTERPRISE "Windows Domain lookups for ENTERPRISE" WINDOWS ferello.min.veritas.com 0

The following indicates which host is the authorization server:

AUTHORIZATION_SERVICE = northpeak 0

If the USE_VXSS entry is either removed or commented out, connections between the servers could fail. To correct this situation, it is necessary to correctly configure VxSS/NBAC. It could be as simple as ensuring that both hosts in question have the same configurations for when to use VxSS. In the example above, uncommenting the USE_VXSS = AUTOMATIC entry corrects the media manager status code 39 problem.

Problem
GENERAL ERROR: Trying to create a new media server and getting error "Couldn't add entry to the Global Device Database."

Error

<16> getrequestack: unable to get request ack string: I/O error (5), stat=-9 <16> globdb_begin: unable to send request to server: network protocol error (39) <16> get_glob_list: unable to obtain globalDB handle: network protocol error (39)

Solution
Overview: Trying to add a media server to a VERITAS NetBackup (tm) environment can fail when the network path is not available or not configured correctly. This can occur due to routing issues or other issues that can prevent a connection from the master server to the media server. The tpconfig or tpautoconf command can fail with the error "Couldn't add entry to the Global Device Database." This error can appear on the command line or within the NetBackup Java Administration console. Troubleshooting: On the media server use the tpautoconf command to try and discover and configure devices on the server. This will fail with an error for each drive discovered if the media server cannot connect to the master.
# /usr/openv/volmgr/bin/tpautoconf -a Couldn't add entry to the Global Device Database. TPAC45 - STK~~~~~T9940B~~~~~~~~~~1.34 /dev/rmt/1cbn -1~-1~-1~-1 1 2 - - - 10 - - - 479000024871 - 3 2048 0 mastersrv - mediasrv 0 - - 4 Couldn't add entry to the Global Device Database. TPAC45 - STK~~~~~T9940B~~~~~~~~~~1.35 /dev/rmt/0cbn -1~-1~-1~-1 1 2 - - - 10 - - - 479000018541 - 3 2048 0 mastersrv - mediasrv 0 - - 4 TPAC45 - - - -1~-1~-1~-1 2 - - - - - - - - - - - 0 0 - - mastersrv 4 - - 0

Check the /usr/openv/volmgr/vm.conf file on the NetBackup client for the existence of a REQUIRED_INTERFACE option. If used, the REQUIRED_INTERFACE option must contain the valid hostname of the media server's network interface to route traffic over.
# cat /usr/openv/volmgr/vm.conf SERVER = <mastersrv> ... REQUIRED_INTERFACE = <hostname>

Master Server Log Files: n/a Media Server Log Files: The /usr/openv/volmgr/debug/tpcommand/log.<date> file will show a failure connect over the network.
<2> mm_getsockconnected: host=conbu12-bac service=vmd address=x.x.x.x protocol=tcp non-reserved port=13701 <2> get_long: (2) premature end of file (byte 1)

<16> getrequestack: unable to get request ack string: I/O error (5), stat=-9 <16> globdb_begin: unable to send request to server: network protocol error (39) <16> get_glob_list: unable to obtain globalDB handle: network protocol error (39) <4> GlobDBConsistencyCheck: get_glob_list() returned 39

Client Log Files: n/a Resolution: Verify the network connection is working between the master and media server. Be sure to test the network interface specified by the REQUIRED_INTERFACE in the media server's vm.conf file if one exists. The REQUIRED_INTERFACE can be added to the media server's vm.conf if the tpcommand log shows the network traffic is not using the expected interface. The address=x.x.x.x entry in the tpcommand log will show the IP address being used for the connection. Hostname lookup problems can also trigger this error. Verify the forward and reverse lookups are working properly for the master and media server and the hostname listed with REQUIRED_INTERFACE in the vm.conf file. For more information on the bpclntcmd reference TechNote 261393, found below in the Related Documents section.