22502 - DSR Application Request Message Queue Utilization

Alarm Group:

APPL

Description:

The DSR Application Request Message Queue Utilization is approaching its maximum capacity.

Severity:

Minor, Major, Critical

Instance:

<Metric ID>, <DSR Application Name>

Note:

The value for Metric ID for this alarm varies (RxPdraRequestMsgQueue, RxCpaRequestMsgQueue, or RxDcaRequestMsgQueue[<DcaDalId.dalId>], for example) depending on which DSR application generates the alarm (CPA, DCA, FABR, Policy DRA, RBAR, etc.). Use the ID that corresponds to the specific DSR application in use.

Note:

The value for DSR Application Name will vary depending on the DSR application generating the alarm (CPA, DCA, FABR, PCA, Policy DRA, RBAR, etc.). Use the name that corresponds to the specific DSR application in use.

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

eagleXgDiameterDsrApplicationRequestQueueUtilNotify

Cause:

Alarm #22502 is raises:

• When DSR 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 from Main Menu > Alarms & Events on the active SOAM server.
   
   
2. This alarm should not normally occur when no other congestion alarms are asserted.

Recovery:

1. Display and monitor the DSR application status by selecting Diameter > Maintenance > Applications in the SO GUI. Verify the Admin State is set as expected.
   The DSR 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 DSR Application. Verify the configuration by selecting Diameter > Configuration > Application Route Tables in the SO GUI.
3. If no additional congestion alarms are asserted, the DSR application task might be experiencing a problem that is preventing it from processing messages from its Request Message Queue. Examine the Alarm log in Alarms & Events on the active SOAM server.
4. If the problem persists, it is recommended to contact My Oracle Support.