This alarm indicates that a Communication Agent is
unable to establish transport connections with one or more other server, and
this may indicate applications on the local server are unable to communicate
with all of their peers. Generally this alarm is generated when a server or the
IP network is undergoing maintenance or when a connection has been manually
disabled.
Severity:
Major
Instance:
N/A
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
cAFConnectionDownNotify
Cause:
A connection becomes
down. If a connection was already down, when another connection becomes down,
then the count of connections is updated, and the alarm is re-asserted.
A connection exits
the down state, and there are other down connections. Update the connection
count and re-assert the alarm.
Diagnostic Information:
This alarm indicates a Communication Agent is unable to
establish transport connections with one or more other servers, and this may
indicate applications on the local server are unable to communicate with all of
their peers. Generally this alarm is asserted when a server or the IP network
is undergoing maintenance or when a connection has been manually disabled.
Following problems could exist:
The IP network may
be experiencing problems due to which the heartbeat exchange between the peers
are not successful.
There are missing
route information or incorrectly configured routes in
NOAM
Configuration > Network > Routes.
Recovery:
Navigate to
Alarms &
Events > View
History to find additional information about the
alarm.
The information can be found by locating the row
with a sequence number that matches the active alarm sequence number and
viewing the Additional Info column.
Check the event history logs by navigating to
Alarms &
Events > View
History for additional Communication Agent events or
alarms from this MP server.
Navigate to
Communication
Agent > Maintenance > Connection Status to determine which
connections on the server have abnormal status.
If the connection is manually disabled, then no
further action is necessary.
Verify the remote server is not under maintenance.
Verify IP network connectivity exists between the
two connection end-points.
Verify the connection’s local IP address and port
number are configured on remote node.
Verify the Application Process using Communication
Agent plug-in is running on both ends.
Verify the connection’s remote IP address and port
correctly identify remote’s listening port.
