HP Insight control for Linux 6.2 Installation Guide

3.4.2.5 Open inbound and outbound ports on the CMS
The network ports listed in Table 3-7 are used for communication between the managed systems
and the CMS. These ports must be open to inbound traffic, so follow the instructions in the
vendor-supplied OS documentation to open the required network ports that are not already
open.
All outbound ports are assumed to be open by default.
In addition to the standard ports, Insight Control for Linux binds to ports dynamically for
outgoing traffic. Because the outbound ports are chosen when the Insight Control for Linux
agents are started, the port numbers will vary between instances, and therefore, the exact port
numbers are different.
If you do not open the required ports inbound, you must disable the firewall on the CMS.
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 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.
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
3.4 Preparing a server or a Xen or KVM virtual guest to become the CMS 25