Troubleshooting guide

Chapter 2, Troubleshooting Procedures 27
General Test and Troubleshooting Procedures
In this example, telnet can establish a connection to the client ant.
◆ If the telnet succeeds, then inetd on the client is configured correctly and is
able to pass its connection to bpcd and NetBackup should also be able to establish
a connection.
◆ If telnet doesn’t work, ensure that the inetd.conf file and /etc/services
files on both the server and client have correct and matching entries. By default,
these are:
In /etc/services:
bpcd 13782/tcp bpcd
In /etc/inetd.conf:
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
Then, execute kill -HUP to reread the /etc/inetd.conf file as explained in
step 3.
Also, update the applicable NIS or DNS files.
If all these files are correct and you still cannot successfully connect to the client,
suspect network routing problems or a problem with the port assignment (see
next step).
5. Check that the client is listening on the correct port for the telnet connection to
bpcd by running one of the following commands (depending on platform and
operating system).
netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)
For example, assume the client in step 4 is a SunOS system named ant and the
telnet is from a NetBackup server named whale:
netstat -a | grep 13782
◆ If there is no problem with the port, you see:
tcp 0 0 ant.nul.nul.com.13782 whale.nul.nul.com.1516 ESTABLISHED
tcp 0 0 *.13782 *.* LISTEN
In the first line of the result, ESTABLISHED indicates that the telnet connection
was established to bpcd through port 13782 on the client.
The LISTEN in the second line indicates that the client is listening for further
connections on this port.