HP Insight Control Software for Linux - Manual (Page 49)

Table 4-1 Open ports on managed systems (continued)
Inbound or outbond Protocol Service Port number
Inbound TCP compaq-https 2381
Inbound TCP mond 2709
Inbound TCP nrpe 5666
Both TCP WBEM 5989
Inbound TCP Insight Control for Linux repository web
server
1
60000
1 This must port must be opened for managed systems running VMware ESX only. If you changed the default port
during installation, you need to open this port instead.
NOTE: In addition to the standard ports, HP Insight Control for Linux also opens a few more
ports dynamically for outgoing traffic. Because the outbound ports are chosen at the start of the
agents, the ports might vary between instances, and thus the exact port numbers will differ.
4.4.2 Resolving host names on the CMS
To ensure proper Nagios notification of syslog reported problems, the syslog-ng service
running on the CMS must be able to recognize the managed systems that posted the syslog
event.
The syslog or syslog-ng services on each managed system uses the /bin/hostname
command output to identify itself in the syslog entry. If the CMS cannot resolve the
host name
in the syslog entry, syslog-ng cannot identify which managed system generated the syslog
event.
As a result of not being able to resolve the host name, syslog-ng logs the event in the
consolidated log as belonging to localhost/localhost. Because localhost does not match
the host name known by HP SIM, syslog notifications for this managed system are not sent
out by Nagios.
To ensure that the CMS can resolve the host name that is appended to all syslog events that
originate from managed systems, follow these steps:
1. Determine the managed system's name by running the hostname command on the system:
# /bin/hostname
If the node does not report a host name, set one or configure DHCP to assign one. DHCP
configuration information is located in the HP Insight Control for Linux Installation Guide.
2. On the CMS, run the mxgethostname command with the host name obtained in the previous
step. For this example, the host name is venus:
# mxgethostname -n venus
If the CMS recognizes the host name, command output is similar to the following:
Host name: venus.example.com
DNS Name: venus.example.com
If the mxgethostname command does not return any results, do the following:
• Verify that the managed system has a valid IP address.
• Verify that the IP address is registered in a DNS server.
• Add the IP address and host name to the /etc/hosts file on the CMS.
• Verify that network is configured correctly and the managed system is able to access
it.
4.4 Setting up managed systems for monitoring 49