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:
-
- Monitor the ingress
traffic rate of each MP from
Status & Manage > KPIs.
- 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.
- 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 DA-MP
status from
Status & Manage > Server.
Recovery:
-
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
.
-
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
. Each
MP in the
server
site should be receiving approximately the same ingress transaction per second.
-
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
page.
If all MPs are in a congestion state then the offered load to the
server
site is exceeding its capacity.
-
The Diameter Process may be experiencing problems.
Examine the alarm log from
Alarms & Events.
-
If the problem persists, it is recommended to
contact
My Oracle Support.