Troubleshooting guide

Chapter 2, Troubleshooting Procedures 25

General Test and Troubleshooting Procedures

2. Verify basic network connectivity between client and server by trying to ping the

client from the server.

ping clientname

Where clientname is the name of the client as configured in the NetBackup class

configuration, /etc/hosts, and also in NIS and DNS (if applicable).

For example, to ping a client named ant:

ping ant

ant.nul.nul.com: 64 byte packets

64 bytes from 199.199.199.24: icmp_seq=0. time=1. ms

----ant.nul.nul.com PING Statistics----

2 packets transmitted, 2 packets received, 0% packet loss

round-trip (ms) min/avg/max = 1/1/1

Also, try ping from the client to the server.

If ping succeeds in both instances, it verifies basic connectivity between the server

and client. If ping fails, you have a network problem outside of NetBackup that must

be resolved before proceeding.

Note that some forms of the ping command let you ping the bpcd port on the client

as in:

ping ant 13782

ping ant bpcd

3. Check that the client is listening on the correct port for connections 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 is a Solaris system and you execute:

netstat -a | grep 13782

If there is no problem with the port, the results are be similar to:

tcp 0 0 *.13782 *.* LISTEN

The LISTEN indicates that the client is listening for connections on this port.

If there is a problem, this line does not appear and one of the following three

conditions exists: