Monitoring Prognosis Connections

The PROGNOSIS Connections Display is accessed from the Prognosis Status Display by clicking on the Connections link at the top of the screen. 

This is online data and it is used on an 'as needed' basis. It is usually used as a tool to provide a different view on how systems connect to each other. It is also very useful in detecting any connection problems, as illustrated in the example screen below, where a connection cannot be established.

This Display provides Connection Summary information for the selected node. The Connection Summary window at the top of the screen shows:

  • The total number of inter-server network connections
  • The number of servers that cannot be connected to
  • The number of connected systems that are managing the current server
  • The total number of physical connections

By clicking on the numeric indicators in the Connections Summary window, the lower window of the Display will be populated with the selected connection data.

All inter-cluster server connections are listed in the table. Any connections that are not in a 'Connected' state will be highlighted in red indicating that there is a network connection problem.

Remote Node

This is the name for the remote end of the connection.

Remote Address

This can be the IP address plus port number for TCPIP connections, a TCPIP process name for HPE NonStop TCPIP listeners or a Node Name for HPE NonStop IPC connections.

Remote PID

Symbolic process ID for the remote end of the connection. This ID uniquely identifies the process


The current connection state. This can be one of the following:


The connection has just been established and the listener is listening for incoming connections.


The connector is trying to connect to the other end.


This end of the connection has been established successfully.


The connection is disconnecting. Disconnecting connections will try to connect again.


The connection is disconnected and will be terminated.


The listener has requested the other end to re-initiate the connection.


If the Connection Status is 'Connected' then this is the time that the connection occurred. If the status is not connected then this is the disconnection time.


This refers to the direction of the connection. This relates to MANAGED-NODES () and MANAGING-NODES () statements in NETWORK Configuration on the involved server. MANAGED means that this server manages the remote server. MANAGING means that this server is managed by the remote server.

Connection (Connection Type) field value

A connection type can either be physical or virtual. 'Physical' indicates that the connection to the remote server is established on a physical link, e.g. server A is directly connected to server B. ''Virtual' indicates that there is no physical link to the remote server and the connection is established over one or more routing server, e.g. server A is connected to server C via one or more intermediate server that routes the data from server C to server A.

See Multi-Domain Management for more information on the purpose of ROUTE-TO statement in the NETWORK Configuration.

The second part of the Connection field shows 'Connector' if the connection is initiated by the Network Router process on this machine, 'Listener' if the connection has been initiated by a remote process or the process primary listener, or 'Multicast' if it is a multicast connection listening on this nodes multicast group address (defined as MULT-GROUP-ADDR in the NETWORK Configuration).


Clicking on a numeric indicator in the Connections Summary window will populate the lower half of the Display with data relating specifically to the selected connection type.

Clicking on a node name in the Remote Node column of the data window will open the Prognosis Connection Details Display that provides further detailed information about the selected connection.

Provide feedback on this article