HP Insight Control for Linux 7.0 Installation Guide

Table 9 Network ports on the CMS that must be open to inbound traffic (continued)
ProtocolServicePort number
TCPSystems Insight Manager web server280
TCP/UDPhttps443
UDPsyslog-ng514
TCPrsync873
TCPHP System Management Homepage2301 and 2381
TCPmond2709
TCPsupermon2710
TCPnrpe5666
TCPnsca5667
2
TCPcmfd6500
TCPSystems Insight Manager secure web server50000
TCPSystems Insight Manager SOAP50001
TCPDatabase communication with management hubs50002
2
TCPInsight Control for Linux repository web server60000
3
TCPBooting virtual media60002
4
1
Although NTP is not required for Insight Control for Linux, HP recommends that you run NTP or similar utility to synchronize
time among the CMS and managed systems.
2
Open this port only if you are configuring management hubs.
3
Port 60000 is the default port used for network installations. If you need to specify another port during the Insight Control
for Linux installation process, open that port instead. If you change the default port, you must update the associated
configuration files as noted in the HP Insight Control for Linux User Guide.
4
Open this port only if you are using virtual media.
3.4.2.6 Open ports for NFS on the CMS (optional)
Insight Control for Linux can manage and monitor as many as a thousand servers through the use
of management hubs, which are servers that are responsible for monitoring a subset of managed
systems. By defining multiple servers to acts as hubs, the monitoring load is distributed across
multiple servers.
The /hptc_cluster file system stores the monitoring data collected by the management hubs.
During the Insight Control for Linux installation procedure you can elect to export this file system
to the management hubs. Doing so enables you to access all monitoring data from any management
hub.
Insight Control for Linux uses NFS to export the /hptc_cluster file system on the CMS to the
management hubs. This means that you will have to configure the CMS to allow it, which requires
opening ports in the firewall.
Because NFS uses random ports by default, you must identify and lock specific ports for NFS so
the firewall can be configured. The procedure differs for RHEL and SLES operating systems.
NOTE: The port numbers used in the procedure are intended as examples; you can elect to use
different values than are used in the procedures.
NOTE: See Table 11 (page 38) if you want to learn more about exporting the /hptc_cluster
file system and management hubs.
3.4 Preparing a server or a Xen or KVM virtual guest to become the CMS 23