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

8.3.1 Opening network ports on managed systems
The network ports listed in Table 12 are used for communication between the managed systems
and the CMS. These ports must be open to network traffic.
If you used Insight Control for Linux to install an OS and you used a configuration derived from a
supported template, the firewall is enabled by default and Insight Control for Linux opens the ports
listed in
Table 12 automatically. If you do not use a supported template for the OS configuration,
the firewall is not opened automatically.
You must follow the instructions in the vendor-supplied documentation for your OS to open the
required ports that are not already open if you did not use Insight Control for Linux to install the
OS on a managed system.
Table 12 Open ports on managed systems
Inbound or outbond Protocol Service Port number
Inbound TCP ssh 22
Inbound TCP http 80
Inbound TCP/UDP SNMP 161
Outbound UDP SNMP trap listener 162
Inbound TCP Server location 427
Inbound UDP syslog-ng 514
Inbound TCP cpq-webm 2301
Inbound TCP compaq-https 2381
Inbound TCP mond 2709
Inbound TCP nrpe 5666
Both TCP WBEM 5989
Inbound TCP Default Insight Control for Linux repository web
server
1
60000
1
If you changed the default port during installation, you must open that port instead, and you must update the associated
configuration files.
The port designated for the repository web server must be opened on managed systems that run VMware ESX.
In addition to the standard ports, 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 differ.
8.3.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, Nagios does not send out syslog notifications for this managed system.
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:
8.3 Setting up managed systems for monitoring 79