EvMpCongestionLevel3Entered

Measurement ID

10289

Measurement Group

MP Performance

Measurement Type

Simple

Measurement Dimension

Single

Description

The number of times that the local DA-MP entered CPU congestion level 3.

Collection Interval

5 min

Peg Condition

Each time Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) transitions from "cleared" or asserted with severity "Info", "Minor", or "Major" to asserted with severity "Critical".

Measurement Scope

Server Group

Recovery

1. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining MPs in the server site. DA-MP server status can be monitored from Main Menu > Status & Manage > Server Status.
2. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP. The ingress traffic rate of each DA-MP can be monitored from Main Menu > Status & Manage > KPIs. Each DA-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 DA-MP can be monitored from Main Menu > Status & Manage > KPIs. 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. The alarm log be examined from Main Menu > Status & Manage > Alarms & Events.
5. If the problem persists, it is recommended to contact My Oracle Support.