Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Network Node Manager i Software Ports
The NNMi ports fit into the following categories:
- Ports Used on the NNMi Management Server
- Ports Used for Communication Between the NNMi Management Server and Other Systems
- Required Accessible Sockets for Global Network Management
Ports Used on the NNMi Management Server
The following table shows 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. See the nnm.ports reference page, or the Linux manpage, for more information.
Note For application failover to work successfully, open TCP ports 7800-7810. For the application failover feature to function correctly, the active and standby NNMi management servers must have unrestricted network access to each other.
|
Port |
Type |
Name |
Purpose |
Change Configuration |
|---|---|---|---|---|
|
80 |
TCP |
nmsas.server.port.web.http |
Default HTTP port - used for Web UI & Web Services - In GNM configurations NNMi uses this port to establish communication from the global manager to the regional manager - Once this port is open, it becomes bi-directional |
Modify the You can also change this during installation. |
|
162 |
UDP |
trapPort |
SNMP trap port |
Modify using the |
|
443 |
TCP |
nmsas.server.port.web.https |
Default secure HTTPS port (SSL) - used for Web UI & Web Services |
Modify the |
|
1098 |
TCP |
nmsas.server.port.naming.rmi |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
1099 |
TCP |
nmsas.server.port.naming.port |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
3873 |
TCP |
nmsas.server.port.remoting.ejb3 |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
4444 |
TCP |
nmsas.server.port.jmx.jrmp |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
4445 |
TCP |
nmsas.server.port.jmx.rmi |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
4446 |
TCP |
nmsas.server.port.invoker.unified |
- Used by NNMi command line tools to communicate with a variety of services used by NNMi - recommends configuring the system firewall to restrict access to these ports to localhost only |
Modify the |
|
4457 |
TCP |
nmsas.server.port.hq |
- Used for un-encrypted Global Network Management traffic. - Messaging travels from the global manager to the regional manager - Once this port is open, it becomes bi-directional |
Modify the |
|
4459 |
TCP |
nmsas.server.port.hq.ssl |
- Used for encrypted Global Network Management traffic. - Messaging travels from the global manager to the regional manager - Once this port is open, it becomes bi-directional |
Modify the |
|
4712 |
TCP |
nmsas.server.port.ts.recovery |
Internal transaction service port |
Modify the |
|
4713 |
TCP |
nmsas.server.port.ts.status |
Internal transaction service port |
Modify the |
|
4714 |
TCP |
nmsas.server.port.ts.id |
Internal transaction service port |
Modify the |
|
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 |
|
7800-7810 |
TCP |
|
- JGroups ports for application failover - If application failover is not used, recommends configuring the system firewall to restrict access to these ports |
Modify the |
|
8886 |
TCP |
OVsPMD_MGMT |
NNMi |
Modify the |
|
8887 |
TCP |
OVsPMD_REQ |
NNMi |
Modify the |
|
8989 |
TCP | com.hp.ov.nms.events.action.server.port | Action server port |
Modify the |
Ports Used for Communication Between the NNMi Management Server and Other Systems
The following table shows some of the ports NNMi uses to communicate with other systems. If a firewall separates NNMi from these systems, you must open many of these ports in the firewall. The actual set of ports depends on the set of integrations you configured to use with NNMi and how you configured those integrations. If column 4 indicates Client, NNMi connects or sends to this port; if column 4 indicates Server, NNMi listens on this port.
|
Port |
Type |
Purpose |
Client, Server |
|---|---|---|---|
|
80 |
TCP |
Default HTTP port for NNMi; used for Web UI and Web Services |
Server |
|
80 |
TCP |
Default HTTP port for NNMi connecting to other applications. The actual port depends on NNMi configuration. |
Client |
|
161 |
UDP |
SNMP request port |
Client |
|
162 |
UDP |
SNMP trap port - traps received by NNMi |
Server |
|
162 |
UDP |
SNMP trap port; Trap Forwarding, Northbound Interface, or NetCool integrations |
Client |
|
389 |
TCP |
Default LDAP port |
Client |
|
395 |
UDP |
nGenius Probe SNMP trap port |
Client |
|
443 |
TCP |
Default secure HTTPS port for NNMi connecting to other applications; the actual port depends onNNMi configuration. Default HTTPS port for HPOM on Windows |
Client |
|
443 |
TCP |
Default secure HTTPS port; used for Web UI and Web Services |
Server |
|
636 |
TCP |
Default secure LDAP port (SSL) |
Client |
|
1741 |
TCP |
Default CiscoWorks LMS web services port |
Client |
|
4457 |
TCP |
Used for un-encrypted Global Network Management traffic. The connection is from the global manager to the regional manager. |
Client, Server |
|
4459 |
TCP |
Used for encrypted Global Network Management traffic. The connection is from the global manager to the regional manager. |
Client, Server |
|
7800-7810 |
TCP |
JGroups ports for application failover |
Client and Server |
|
8004 |
TCP |
Default HTTP port for NNMi if another web server already has port 80. Used for Web UI and Web Services. Verify the actual HTTP port for your NNMi management server. |
Server |
|
8080 |
TCP |
Default HTTP port for connecting to NA if installed on the same system as NNMi. Default HTTPS port for UCMDB web services |
Client |
|
8443 or 8444 |
TCP |
Default HTTP port for connecting to HPOM for UNIX |
Client |
|
9300 |
TCP |
Default HTTP port for connecting to NNM iSPI Performance for Metrics |
Client |
|
50000 |
TCP |
Default HTTPS port for connecting to SIM |
Client |
Note If you configure NNMi to use ICMP fault polling or ping sweep for discovery, configure the firewall to pass ICMP packets through the firewall.
Note The Web Services approach for the NNMi-HPOM integration does not work through a firewall, however the NNMi-HPOM integration using the Northbound Interface does work through a firewall.
Required Accessible Sockets for Global Network Management
The following table shows the well-known ports that need to be accessible from a global NNMi management server to a regional 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 |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: