NetBackup Troubleshooting Guide - Zedat

General Test and Troubleshooting Procedures
d. Check the client names, server names, and service entries in your NetBackup
configuration as explained in “Verifying Host Names and Services Entries” on
page 34.
Two other checks that you can make on host names are:
◆ Use the hostname command on the client to determine the host name that
the client sends with requests to the server.
◆ Check the bprd debug log (verbose) on the server to determine what
occurred when the server received the request.
e. Pay special attention to NIS or DNS updates that are required. Failing to properly
update these services is a common source of network problems with NetBackup.
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 policy
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
or
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
28 NetBackup Troubleshooting Guide