Go to primary content
User Data Repository Alarms, KPIs, and Measurements
Release 12.4
E82598-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

RxDOCDiscardMp

Measurement ID
10252
Measurement Group
Diameter Ingress Transaction Exception
Measurement Type
Simple
Measurement Dimension
Single
Description
The number of ingress messages that were discarded due to local DA-MP danger of CPU congestion.
Collection Interval
5 min
Peg Condition
Pegged for each message discarded due to DA-MP danger of CPU congestion.
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. DA-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 DA-MP can be monitored from the Status & Manage > KPIs page. 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 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, it is recommended to contact My Oracle Support.