EvMpCongestionEntered

Measurement Group: MP Performance

Measurement Type: Simple

Measurement Dimension: Single

Description: The number of times that the MP became congested (regardless of severity level).

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 to asserted with severity CL1.

Measurement Scope: Server Group

Recovery:

  1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining MPs in the server site. MP server status can be monitored from the Status & Manage > Server page.
  2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. 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 > 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. The alarm log should be examined using the Alarms & Events page.
  5. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Message Processor (MP) Performance measurements