1. Alarms and KPIs
  2. Alarms and Events
  3. Diameter Alarms and Events (8000-8299, 22000-22350, 22900-22999, 25600-25899)
  4. 22200 - MP CPU Congested

3.9.85 22200 - MP CPU Congested

Alarm Group:
ExgStack
Description:
DA-MP CPU utilization threshold has been exceeded. Potential causes are:
  • One or more peers are generating more traffic than is normally expected
  • Configuration requires more CPUs for message processing than is normally expected
  • One or more peers are answering slowly, causing a backlog of pending transactions
  • A DA-MP has failed, causing the redistribution of traffic to the remaining DA-MPs
Severity:
Minor, Major, Critical, Warning
Instance
NA
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterMpCpuCongestedNotify
Cause:

Potential causes are:

  • One or more peers are generating more traffic than is normally expected.
  • Configuration requires more CPUs for message processing than is normally expected.
  • One or more peers are answering slowly, causing a backlog of pending transactions.
  • A DA-MP has failed, causing the redistribution of traffic to the remaining DA-MPs.
Diagnostic Information:
  1. Monitor the ingress traffic rate of each MP from Status & Manage > KPIs.
    1. The misconfiguration 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.
    2. 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.
  2. Examine the alarm log from Main Menu > Alarms & Events.
  3. Examine the DA-MP status from Status & Manage > Server.

Recovery:

  1. If one or more MPs in a server site has failed, the traffic is distributed between the remaining MPs in the server site. Monitor the MP server status from Status & Manage, and then Server.
  2. The mis-configuration of DIAMETER peers may result in too much traffic being distributed to the MP. Monitor the ingress traffic rate of each MP from Status & Manage, and then KPIs. Each MP in the server site should be receiving approximately the same ingress transaction per second.
  3. There may be an insufficient number of MPs configured to handle the network traffic load. The ingress traffic rate of each MP can be monitored from the Status & Manage, and then KPIs page. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
  4. The Diameter Process may be experiencing problems. Examine the alarm log from Alarms & Events.
  5. If the problem persists, it is recommended to contact My Oracle Support.