C. List of Ports Used by NNMi
Table C-1 lists the ports NNMi uses on the management server. NNMi listens on these ports. If port conflicts occur, you can change most of these port numbers as shown in the Change configuration column.
- Important note
-
For application failover to work successfully, use the following configurations:
-
Open TCP ports 7800 to 7810.
-
The active and standby NNMi management servers must have unrestricted network access to each other.
-
To run NNMi in a cluster system in an HA configuration, the port number configurations used on the primary and secondary cluster nodes must be the same. When you change a port in the nms-local.properties file, you must configure each node (the port change is not copied by file replication of the HA configuration).
Port |
Type |
Name |
Purpose |
Change configuration |
---|---|---|---|---|
80 |
TCP |
nmsas.server.port.web.http |
Default HTTP port
|
Modify the nms-local.properties file. You can also change this during installation.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
162 |
UDP |
trapPort |
SNMP trap port |
Modify using the nnmtrapconfig.ovpl Perl script. |
443 |
TCP |
nmsas.server.port.web.https |
Default secure HTTPS port (SSL)
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
1098 |
TCP |
nmsas.server.port.naming.rmi |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
1099 |
TCP |
nmsas.server.port.naming.port |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
3873 |
TCP |
nmsas.server.port.remoting.ejb3 |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4444 |
TCP |
nmsas.server.port.jmx.jrmp |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4445 |
TCP |
nmsas.server.port.jmx.rmi |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4446 |
TCP |
nmsas.server.port.invoker.unified |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4457 |
TCP |
nmsas.server.port.hq |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4459 |
TCP |
nmsas.server.port.hq.ssl |
|
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4712 |
TCP |
nmsas.server.port.ts.recovery |
Internal transaction service port |
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4713 |
TCP |
nmsas.server.port.ts.status |
Internal transaction service port |
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
4714 |
TCP |
nmsas.server.port.ts.id |
Internal transaction service port |
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
5432 |
TCP |
com.hp.ov.nms.postgres.port |
This PostgreSQL port is the port the embedded database listens on for this NNMi management server. |
Modify the nms-local.properties file.
%NNM_CONF%\nnm\props\nms-local.properties
$NNM_CONF/nnm/props/nms-local.properties |
7500 |
UDP |
nnmcluster |
Port used by nnmcluster. |
Configuration cannot be modified. |
7800 to 7810 |
TCP |
-- |
|
Modify the nms-cluster.properties file.
%NNM_CONF%\nnm\props\nms-cluster.properties
$NNM_CONF/nnm/props/nms-cluster.properties |
8886 |
TCP |
OVsPMD_MGMT |
NNMi ovspmd (process manager) management port |
1. Run the ovstop command to stop the NNMi service. 2. Open the services file:
%Windir%\system32\drivers\etc\services
/etc/services 3. Add the following line to the file: ovspmd_mgmt port-number/tcp 4. Run the ovstart command to start the NNMi service. |
8887 |
TCP |
OVsPMD_REQ |
NNMi ovsmpd (process manager) request port |
1. Run the ovstop command to stop the NNMi service. 2. Open the services file:
%Windir%\system32\drivers\etc\services
/etc/services 3. Add the following line to the file: ovspmd_req port-number/tcp 4. Run the ovstart command to start the NNMi service. |
- Legend:
-
--: No name
Table C-2 lists some of the ports NNMi uses to communicate with other systems. If a firewall separates NNMi from these systems, open many of these ports in the firewall. The actual set of ports to open depends on the system to be linked to NNMi and how that system is configured.
Purpose |
Port No. (Port/Type) |
Firewall pass-through direction |
---|---|---|
NNMi console |
80/tcp |
|
SNMP request |
161/udp |
NNMi |
SNMP response |
ANY/udp |
NNMi |
SNMP trap/SNMP inform request |
162/udp |
NNMi |
Response to SNMP inform request |
ANY/udp |
NNMi |
SNMP trap transfer |
162/udp |
NNMi NNMi |
LDAP |
389/tcp |
NNMi |
NNMi console using SSL connection |
443/tcp |
|
LDAP using SSL connection |
636/tcp |
NNMi |
Messaging bisocket connector |
4457/tcp |
NNMi (global manager) |
Messaging bisocket connector using SSL connection |
4459/tcp |
NNMi (global manager) |
Application failover |
7800 to 7810/tcp |
NNMi (active) |
- Legend:
-
:
For TCP, the arrow indicates the direction in which a connection is made.
For UDP, the arrow indicates the direction in which a packet is sent.
#1: An SNMP response is made from the SNMP request receiving port to the SNMP request sending port.
#2: A response to an SNMP inform request is made from the SNMP inform request receiving port to the SNMP inform request sending port.
Notes:
1. You must configure the firewall to pass ICMP between NNMi and the monitored node.
2. The port numbers are set to the default settings.
3. For details about configuring application failover, see Chapter 16. Configuring NNMi for Application Failover.
If you configure NNMi to use ICMP fault polling or ping sweep for node discovery, configure the firewall to pass ICMP packets through the firewall.
If you plan to use the global network management feature, Table C-3 shows the ports that need to be accessible to a regional NNMi management server from a global NNMi management server. The global network management feature requires these ports to be open for TCP access from the global NNMi management server to the regional NNMi management server. The regional NNMi management server will not open sockets back to the global NNMi management server.
Security |
Parameter |
TCP port |
---|---|---|
Non-SSL |
nmsas.server.port.web.http |
80 |
nmsas.server.port.hq |
4457 |
|
SSL |
nmsas.server.port.web.https |
443 |
nmsas.server.port.hq.ssl |
4459 |