19804 - Communication Agent configured connection waiting for remote client to establish connection

Alarm Group: CAF

Description: Communication Agent configured connection waiting for remote client to establish connection. This alarm indicates that a Communication Agent is waiting for one or more far-end client MPs to initiate transport connections. Generally this alarm is asserted when a client MP or the IP network is undergoing maintenance or when a connection has been manually disabled at a client MP.
Note: It is normal to have this auto-clearing connection alarm for the remote server connections that configured manually in "Client" mode, but are not yet available for processing traffic.

Severity: Minor

Instance: N/A

HA Score: Normal

Auto Clear Seconds: 300 (5 min)

OID: cAFClientConnWaitNotify

Recovery:

The alarm is cleared when a "server" connection exits the "forming" state and no other connection having "server" connect mode is in the "forming" state or the auto-clear time-out occurs.
  • The MP Server/Connection is deleted
  • When connection is moved to TotallyBlocked/RemotelyBlocked/InService state from Aligning
  • Auto Clear
  • Connection is disabled
The alarm is cleared only for remote server connections that are configured manually in “Client” mode. This mode is used to listen for connection requests from configured remote clients.
  • The MP Server/Connection is deleted
  • When connection is moved to TotallyBlocked/RemotelyBlocked/InService state from Aligning
  • Auto Clear
  • Connection is disabled
  1. Find additional information for the alarm in Main Menu > Alarms & Events > View History 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 at Main Menu > Alarms & Events > View History for additional Communication Agent events or alarms from this MP server.
  3. Check Main Menu > Communication Agent > Maintenance > Connection Status to determine which connections on the server have abnormal status.
  4. Verify that the remote server is not under maintenance.
  5. If the connection is manually disabled at the client MP, and it is expected to be disabled, then no further action is necessary.
  6. If the connection has been manually disabled at the client MP, but it is not supposed to be disabled, then enable the connection by clicking on the 'Enable' action button on the Connection Status screen.
  7. Verify that IP network connectivity exists between the two connection end-points.
  8. Verify that the connection's local IP address and port number are configured on remote client MP.
  9. Verify that the Application Process using Communication Agent plug-in is running on both ends.
  10. Verify that the connection's remote IP address and port correctly identify remote's listening port.
  11. Contact My Oracle Support (MOS) for assistance.
Parent topic: Communication Agent, ComAgent (19800-19909)