HP Servicecontrol Manager 3.0 Troubleshooting Guide

Operating System and Networking Issues
Incorrect Network Configuration
Chapter 2
15
Incorrect Network Configuration
If nslookup(1) fails, Servicecontrol Manager cannot resolve hostnames and the mxnode
command will fail.
Symptom The command mxnode -a
hostname fails with the error:
Unknown host: ‘node_name’. Node ignored.
Verification Verify that this command works: nslookup $(
hostname )
The output must have a line beginning with Name: as well as one that follows that starts
with either Address: or Addresses:. If the command fails:
•Check /etc/nsswitch.conf:
— Does it exist?
— Is the file readable by all?
— What order is it specifying for IP address resolution?
•If /etc/nsswitch.conf specifies use of a file for IP address resolution (such as
/etc/hosts):
— Does this file exist?
— Is it readable by all?
—Is the
hostname resolvable by its entry in this file?
— Does this file have the CMS entry defined correctly?
•If /etc/nsswitch.conf specifies use of DNS:
— Can any user use nslookup(1) to resolve the IP address of the
hostname ?
—Do nslookup
short_hostname and
nslookup
fully_qualified_hostname work for both root and non-root users?
—Does /etc/resolve.conf exist, and is it readable by all?
—Does /etc/resolve.conf specify the correct
search domain_name for DNS to resolve the IP address of
hostname ?
— On HP-UX, run nslookup -swdebug
hostname to see how the IP address is
being resolved. On Linux, run the nslookup -debug
hostname command.
Fix • Try using a fully qualified name with mxnode -a when adding the managed node.
•If required by nslookup(1), make sure that /etc/nsswitch.conf, /etc/hosts and
/etc/resolve.conf are readable by all, and have the correct and appropriate
information for nslookup(1).