EvMpCongestionLevel1Entered
- Measurement ID
- 10285
- Measurement Group
- MP Performance
- Measurement Type
- Simple
- Measurement Dimension
- Single
- Description
- The number of times that the local DA-MP entered CPU congestion level 1.
- 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" to asserted with severity "Minor".
- Measurement Scope
- Server Group
Recovery
- 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 .
- 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 . Each DA-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 DA-MP can be monitored from . 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. The alarm log be examined from .
- If the problem persists, it is recommended to contact My Oracle Support.