TmMpCongestion

Measurement Group: MP Performance

Measurement Type: Simple

Measurement Dimension: Single

Description: Total time (in millisecondsseconds) spent in local MP congestion state.

Collection Interval: 5 min

Peg Condition:The time duration interval starts when one of the following conditions occurs:
  1. 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 asserted (regardless of severity level).
  2. Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is asserted with severity Minor (local MP congestion level CL0 to CL1 transition).
The time duration interval stops when one of the following conditions occurs:
  1. 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 asserted (regardless of severity level).
  2. Alarm 22200 - Local MP Congestion (refer to the DSR Alarms and KPIs Reference for details about this alarm) is cleared (local MP congestion level CL1 to CL0 transition).
When a time duration interval completes, the time measured is added to the total measurement value.

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