RxDOCRejectMp

Measurement Group: Diameter Exception

Measurement Type: Simple

Measurement Dimension: Single

Description: The number of ingress Diameter messages that were rejected with error answer due to local DA_MP danger of CPU congestion.

Collection Interval: 5 min

Peg Condition: Pegged for each message discarded with a DIAMETER (Error) Answer due to DA-MP danger of CPU congestion.

Measurement Scope: Server Group

Recovery:

  1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may need to be changed.
  2. 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.
  3. 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.
  4. 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.
  5. The Diameter process may be experiencing problems. The alarm log should be examined using the Alarms & Events page.
  6. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Diameter Exception measurements