STATUS CODE: 160, encountered after enabling Vopie authentication for the NetBackup server and clients.

Article:TECH47600  |  Created: 2006-01-24  |  Updated: 2008-01-25  |  Article URL http://www.symantec.com/docs/TECH47600
Article Type
Technical Solution


Environment

Issue



STATUS CODE: 160, encountered after enabling Vopie authentication for the NetBackup server and clients.

Error



<32> bpdbm: authentication failed: 15
<2> bpdbm: request complete: exit status 160 authentication failed

Solution



Overview:
A Status code 160 is encountered after enabling Vopie (Veritas One-time Passwords In Everything) authentication for the Veritas NetBackup (tm) server and clients.  This error is seen when starting the Windows Remote Administration Console and attempting to connect to the master server.  The connection will report a Status 160 and state that the bprd daemon is not running.  This can occur if the public and secret keys have not been configured properly for the servers and clients.

Vopie uses two types of keys.  The first type of keys are public (hashed) keys.  These store the authentication challenges that a local system presents to remote systems.   The second type of keys are secret (unhashed) keys.  These contain the secret key that NetBackup uses when it responds to challenges from remote systems.

Troubleshooting:
Enable the admin, bpdbm and bpcd logs and look for any errors that appear when trying to connect via the Windows Remote Admin console.

Log Files:
The /usr/openv/netbackup/logs/admin/log.<date> file on the master will show:
<2> bpauthsync.c.298: function update_files failed: 160

The /usr/openv/netbackup/logs/bpdbm/log.<date> file on the master will show:
<2> logconnections: BPDBM ACCEPT FROM x.x.x.x.34858 TO x.x.x.x.13721
<2> connected_peer: Connection from host <hostname>, <ip>, on non-reserved port 34858
<2> vauth_acceptor: vauth_comm.c.364: Function failed: 15 0x0000000f
<32> bpdbm: authentication failed: 15
<2> bpdbm: request complete: exit status 160 authentication failed

The /usr/openv/netbackup/logs/bpcd/log.<date> file on the client will show:
<2> logconnections: BPCD ACCEPT FROM 192.168.81.11.834 TO 192.168.81.10.13782
<2> bpcd main: setup_sockopts complete
<2> vauth_acceptor: vauth_comm.c.364: Function failed: 15 0x0000000f
<16> bpcd main: authentication failed: 15

Resolution:
It will be necessary to properly configure the hashed and unhashed keys prior to running the bpauthsync command.  This can be done by doing the following on the NetBackup systems that will be configured for vopie authentication.  The following examples use a master server (client_a) and the system running the Windows Remote Administration console (client_b).

1. Remove the directories 'hashed' and 'unhashed' (including their contents) from /usr/openv/var/auth/vopie.

2.  On the master run the following commands:
# cd /usr/openv/bin
# ./vopie_util -local_name client_a -unhashed client_b client_a

This will display the host name and the key information:
client_a <seq> <seed> <hash>

3.  On the system running the Windows Administration console, run the following commands:
# cd /usr/openv/bin
# ./vopie_util -local_name client_b -hashed client_a <seq> <seed> <hash>
# ./vopie_util -local_name client_b -unhashed client_a
This will display the host name and the key information.
client_b <seq> <seed> <hash>

3.  On the master server:
# cd /usr/openv/bin
# ./vopie_util -local_name client_a -hashed client_b <seq> <seed> <hash>

4. Run the bpauthsync command from the master to update the files:
# cd /usr/openv/netbackup/bin/admincmd
# ./bpauthsync -vopie -servers -clients client_a client_b

Once the hashed and unhashed keys have been configured for the systems, connect to the master server with the Windows Remote Administration console again.

Supplemental Materials

SourceError Code
Value160
DescriptionNetBackup Error 160: authentication failed

Legacy ID



283146


Article URL http://www.symantec.com/docs/TECH47600


Terms of use for this information are found in Legal Notices