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 |
|
NNM iSPI Performance for Traffic Ports
The NNM iSPI Performance for Traffic ports fit into the following categories:
- Ports Used on the NNM iSPI Performance for Traffic Management Server (Traffic Master)
- Ports Used on the NNM iSPI Performance for Traffic Management Server (Traffic Leaf)
- Ports Used for Communication Between the NNM iSPI Performance for Traffic Management Server and Other Systems
Ports Used on the NNM iSPI Performance for Traffic Management Server (Traffic Master)
The following table shows the ports the NNM iSPI Performance for Traffic (Traffic Master component) uses on the management server. In case of port conflicts, almost all of these port numbers can be changed using the server.properties file located at: %NnmDataDir%/nmsas/traffic-master/server.properties.
|
Port |
Type |
Name |
Purpose |
Change Configuration |
|---|---|---|---|---|
|
5432 |
TCP |
com.hp.ov.nms.postgres.port |
This PostgreSQL port is the port the embedded database listens on for this NNMi management server. The port is expected to be the same as that configured for NNMi in the nms-local.properties file |
N/A |
|
12080 |
TCP |
nmsas.server.port.web.http |
Default HTTP port - used for Web UI. |
Modify the |
|
12043 |
TCP |
nmsas.server.port.web.https |
Default secure HTTPS port (SSL) - used for Web UI. |
Modify the |
|
12083 |
TCP |
nmsas.server.port.naming.rmi |
Default port for RMI naming service |
Modify the |
|
12084 |
TCP |
nmsas.server.port.jmx.jrmp |
Default RMI object port (JRMP invoker) |
Modify the |
|
12085 |
TCP |
nmsas.server.port.jmx.rmi |
Default RMI pooled invoker port |
Modify the |
|
12086 |
TCP |
nmsas.server.port.invoker.unified |
Default RMI remoting server connector port |
Modify the |
|
12087 |
TCP |
nmsas.server.port.hq |
Used for un-encrypted Global Network Management traffic. |
Modify the |
|
12089 |
TCP |
nmsas.server.port.remoting.ejb3 |
Default EJB3 |
Modify the |
|
12092 |
TCP |
nmsas.server.port.hq.ssl |
Used for encrypted Global Network Management traffic. |
Modify the |
|
12099 |
TCP |
nmsas.server.port.naming.port |
Default bootstrap JNP service port (JNDI provider) |
Modify the |
|
12712 |
TCP |
nmsas.server.port.ts.recovery |
Default recovery port used by the Transaction service. |
Modify the |
|
12713 |
TCP |
nmsas.server.port.ts.status |
Default status port used by the Transaction service. |
Modify the |
|
12714 |
TCP |
nmsas.server.port.ts.id |
Default port used by the Transaction service. |
Modify the |
Ports Used on the NNM iSPI Performance for Traffic Management Server (Traffic Leaf)
The following table shows the ports the NNM iSPI Performance for Traffic (Traffic Leaf component) uses on the management server. In case of port conflicts, almost all of these port numbers can be changed using the server.properties file located at: %NnmDataDir%/nmsas/traffic-leaf/server.properties.
|
Port |
Type |
Name |
Purpose |
Change Configuration |
|---|---|---|---|---|
|
5432 |
TCP |
com.hp.ov.nms.postgres.port |
This PostgreSQL port is the port the embedded database listens on for this NNMi management server. The port is expected to be the same as that configured for NNMi in the nms-local.properties file. |
N/A |
|
11080 |
TCP |
nmsas.server.port.web.http |
Default HTTP port - used for Web UI. |
Modify the |
|
11043 |
TCP |
nmsas.server.port.web.https |
Default secure HTTPS port (SSL) - used for Web UI. |
Modify the |
|
11083 |
TCP |
nmsas.server.port.naming.rmi |
Default port for RMI naming service |
Modify the |
|
11084 |
TCP |
nmsas.server.port.jmx.jrmp |
Default RMI object port (JRMP invoker) |
Modify the |
|
11085 |
TCP |
nmsas.server.port.jmx.rmi |
Default RMI pooled invoker port |
Modify the |
|
11086 |
TCP |
nmsas.server.port.invoker.unified |
Default RMI remoting server connector port |
Modify the |
|
11087 |
TCP |
nmsas.server.port.hq |
Used for un-encrypted Global Network Management traffic. |
Modify the |
|
11089 |
TCP |
nmsas.server.port.remoting.ejb3 |
Default EJB3 remoting connector port |
Modify the |
|
11092 |
TCP |
nmsas.server.port.hq.ssl |
Used for encrypted Global Network Management traffic. |
Modify the |
|
11099 |
TCP |
nmsas.server.port.naming.port |
Default bootstrap JNP service port (JNDI provider) |
Modify the |
|
11712 |
TCP |
nmsas.server.port.ts.recovery |
Default recovery port used by the Transaction service. |
Modify the |
|
11713 |
TCP |
nmsas.server.port.ts.status |
Default status port used by the Transaction service. |
Modify the |
|
11714 |
TCP |
nmsas.server.port.ts.id |
Default port used by the Transaction service. |
Modify the |
Ports Used for Communication Between the NNM iSPI Performance for Traffic Management Server and Other Systems
The following table shows some of the ports NNM iSPI Performance for Traffic uses to communicate with other systems. If a firewall separates the NNM iSPI Performance for Traffic 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 the NNM iSPI Performance for Traffic and how you configured those integrations. If column 4 indicates Client, the NNM iSPI Performance for Traffic connects or sends to this port; if column 4 indicates Server, the NNM iSPI Performance for Traffic listens on this port.
|
Port |
Type |
Purpose |
Client or Server |
|---|---|---|---|
|
Any Free Port |
TCP |
Avaya Streaming |
Server |
|
Any Free Port |
TCP |
RTCP Server |
Server |
|
22 |
TCP |
Cisco/Avaya SSH Communication |
Client |
|
22/23 |
TCP |
Cisco FTP/SFTP Communication |
Server |
|
23 |
TCP |
Avaya Survivable Communication |
Client |
|
8000 (Configurable) |
TCP |
.NET Proxy(IPT shipped) |
Client |
|
8443 |
TCP |
Cisco AXL Communication |
Client |
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: