RxDOCRejectConn

Measurement ID

#####

Measurement Group

Diameter Exception

Measurement Type

Simple

Measurement Dimension

Arrayed (by Connection ID)

Description

The number of ingress Diameter messages that were rejected with an error response because of local DA-MP danger of CPU congestion.

Collection Interval

5 min

Peg Condition

For each message discarded on a connection with a DIAMETER (Error) Answer due to DA-MP danger of CPU congestion.

Measurement Scope

Server Group

Recovery

1. The DA-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. DA-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 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.
4. 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.
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.