22051 - Peer Unavailable
- Alarm Group:
- DIAM
- Description:
- Unable to access the Diameter Peer because all of
the transport connections are down. Peer node unavailability can happen in
these cases:
- All connections toward a peer are no longer candidates for routing Request messages.
- No available connections within the peer node support the Application ID. This is functionally equivalent to the peer node being unavailable.
- The Connection Priority Level (CPL) value for a resource is changed to 99, which means the operational status is Unavailable. The CPL value of a connection can be found in the active SO under .
- The number of established connections drops below the configured Minimum Connection Capacity.
- Severity:
- Critical
- Instance:
- <PeerName> (of the Peer which failed).
- HA Score:
- Normal
- Auto Clear Seconds:
- 0 (zero)
- OID:
- eagleXgDiameterPeerUnavailableNotify
- Cause
- The Alarm #22051 raises when the Diameter Peer is not accessible as all the transport connections are down.
- Diagnostic Information
-
Peer node is unavailable in the following cases:
Recovery:
-
Confirm a connection is provisioned for the peer
node.
- Peer status can be monitored from .
- Verify IP network connectivity exists between the MP server and the peer nodes using ping, traceroute, or other means.
- Examine the event history logs for additional DIAM events or alarms from the MP server.
- Verify the peer is not under maintenance.
- Verify there are connections provisioned for the peer node.
- Verify the status of all connections toward the
peer node.
From the active SO GUI, navigate to . View the Transaction Configuration Set of the peer node.
If the peer node has a corresponding Transaction Configuration Set setting, then navigate to and confirm the Application ID is supported.
- Confirm the peer node supports the Application ID in the request message.
- Resolve any congestion issues on the peer node.
- If the problem persists, it is recommended to contact My Oracle Support.
