1. Alarms and KPIs Guide
  2. Alarms and Events
  3. Generic Application Alarms and Events (22500-22599)
  4. 22502 - Peer CNDRA Application Request Message Queue Utilization

22502 - Peer CNDRA Application Request Message Queue Utilization

Alarm Group:
APPL
Description:
The Peer CNDRA Application Request Message Queue Utilization is approaching its maximum capacity.
Severity:
Minor, Major, Critical
Instance:
<Metric ID>, <Peer CNDRA Application Name>

Note:

The value for Metric ID for this alarm varies (such as RxRbarRequestMsgQueue) depending on which Peer CNDRA application generates the alarm (such as RBAR). Use the ID that corresponds to the specific Peer CNDRA application in use.

Note:

The value for Peer CNDRA Application Name will vary depending on the Peer CNDRA application generating the alarm (such as RBAR). Use the name that corresponds to the specific Peer CNDRA application in use.
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterCndraApplicationRequestQueueUtilNotify
Cause:

Alarm #22502 is raises:

  • When Peer CNDRA Application Request Message Queue Utilization is approaching its maximum capacity.
  • If this problem persists and the queue reaches 100% utilization all new ingress Request messages will be discarded.
Diagnostic Information:
To get further information regarding this issue:
  1. Examine the alarm log on the active Overseer server.
  2. This alarm should not normally occur when no other congestion alarms are asserted.

Recovery:

  1. Display and monitor the Peer CNDRA application status. Verify the Admin State is set as expected.
    The Peer CNDRA application's Request Message Queue Utilization is approaching its maximum capacity. This alarm should not normally occur when no other congestion alarms are asserted.
  2. Application Routing might be mis-configured and is sending too much traffic to the Peer CNDRA Application. Verify the configuration.
  3. If no additional congestion alarms are asserted, the Peer CNDRA application task might be experiencing a problem that is preventing it from processing messages from its Request Message Queue. Examine the Alarm log on the active Overseer server.
  4. If the problem persists, it is recommended to contact My Oracle Support.