Alarms and KPIs

22223 - DraWorker Memory Utilization Threshold Crossed

Alarm Group:

DIAM

Description:

DraWorker memory utilization threshold crossed.

Severity:

Minor, Major, Critical

Instance:

System.RAM_UtilPct, DSR

HA Score:

Normal

Auto Clear Seconds:

0 (zero, no auto clear)

OID:

eagleXgDiameterMpMemCongestedNotify

Cause:

Following are the potential causes:

One or more peers are generating more traffic than expected.
Configuration requires more Physical Memory for message processing than expected.
One or more peers are answering slowly, causing a backlog of pending transactions.
A DraWorker failed, causing the redistribution of traffic to the remaining DraWorkers.

Diagnostic Information:

To diagnose the cause:

Monitor the ingress traffic rate of each MP from Status & Message > KPIs.
- The mis-configuration of server/client routing may result in too much traffic being distributed to the MP. Each MP in the server site should be receiving approximately the same ingress transactions per second.
- There may be an insufficient number of MPs configured to handle the network traffic load. If all MPs are in congestion, then the traffic load to the server site is exceeding its capacity.
Examine the alarm log from Main Menu > Alarms & Events.
Examine the DraWorker status from Status & Manage > Server.

Recovery:

Analyze and correct routing so the traffic load is balanced between MPs.
If all MPs are approaching or exceeding their engineered traffic handling capacity, add more MPs to the system and configure connections and routes to distribute traffic to new DraWorkers.
If the problem persists, it is recommended to contact My Oracle Support.