19800 - Communication Agent Connection Down

Alarm Group:

CAF

Description:

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, and then Network, and then Routes.

Recovery:

1. Navigate to Alarms & Events, and then 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.

2. Check the event history logs by navigating to Alarms & Events, and then View History for additional Communication Agent events or alarms from this MP server.
3. Navigate to Communication Agent, and then Maintenance, and then Connection Status to determine which connections on the server have abnormal status.
4. If the connection is manually disabled, then no further action is necessary.
5. Verify the remote server is not under maintenance.
6. Verify IP network connectivity exists between the two connection end-points.
7. Verify the connection’s local IP address and port number are configured on remote node.
8. Verify the Application Process using Communication Agent plug-in is running on both ends.
9. Verify the connection’s remote IP address and port correctly identify remote’s listening port.
10. It is recommended to contact My Oracle Support for assistance.