HP Insight Control for Linux 6.0 Installation Guide

Table 3-7 Network ports on the CMS that must be open to inbound traffic
ProtocolServicePort number
TCP
ssh
22
UDP
tftp
69
TCP/UDPSNMP161
UDPSNMP trap listener162
TCP
syslog-ng
214
TCPSystems Insight Manager web server280
TCP/UDP
https
443
UDP
syslog-ng
514
TCP
rsync
873
TCPHP System Management home page2301 and 2381
TCP
mond
2709
TCP
supermon
2710
TCP
nrpe
5666
TCP
nsca
5667
1
TCP
cmfd
6500
TCPSystems Insight Manager secure web server50000
TCPSystems Insight Manager SOAP50001
TCPDatabase communication with management hubs50002
1
TCPInsight Control for Linux repository web server60000
2
TCPBooting virtual media60002
3
1 Open this port only if you are configuring management hubs.
2 Port 60000 is the default port used for network installations. If you override the default 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.
3 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 OSs.
3.4 Preparing a server or Xen virtual guest to become the CMS 25