TmMpCongestionLevel2

Measurement Group: MP Performance

Measurement Type: Simple

Measurement Dimension: Single

Description: The total time (in seconds) the local DA-MP was in CPU congestion level 2. This value will appear as an aggregate value retrieved from all DA-MPs in a Network Element.

Collection Interval: 5 min

Peg Condition:

The "time interval" starts when one of the following conditions occur:
  • A new "collection interval" for the measurement begins and Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is already asserted with severity "Major".
  • Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is asserted with severity "Major" (onset of local DA-MP CPU congestion level 2 or abatement of local DA-MP CPU congestion levels 3).
The "time interval" stops when one of the following conditions occur:
  • The "collection interval" for the measurement ends and Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is already asserted with severity "Major".
  • Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is no longer asserted with severity "Major" (abatement of local DA-MP CPU congestion level 2 or onset of local DA-MP CPU congestion levels 3).

When the "time interval" completes, the time measured is added to the measurement value.

  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, contact My Oracle Support (MOS).
Parent topic: Message Processor (MP) Performance measurements