TmMpDangerOfCongestion

Measurement Group: MP Performance

Measurement Type: Simple

Measurement Dimension: Single

Description: The total time (in milliseconds) the local DA-MP was in danger of CPU congestion. This will appear as an aggregate value retrieved from all DA-MPs for OAM Network Element.

Collection Interval: 5 min

Peg Condition:

The “time interval” starts when one of the following conditions occurs:
  • 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 “Info”.
  • Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is asserted with severity “Info” (onset of local DA-MP danger of CPU congestion).
The “time interval” stops when one of the following conditions occurs:
  • 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 “Info”.
  • Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is cleared (abatement of local DA-MP danger of CPU congestion).

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

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. Monitor the DA-MP server status from Main Menu > Status & Manage > Server Status.
  2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the MP. Monitor the ingress traffic rate of each DA-MP 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. Monitor the ingress traffic rate of each DA-MP 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. Examine the alarm log from Main Menu > Alarms & Events.
  5. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Message Processor (MP) Performance measurements