RxConnMpCongestionAnswerRsp

Measurement Group: Diameter Exception

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: The number of ingress messages that were rejected with an error response because of local congestion.

Collection Interval: 5 min

Peg Condition: For each ingress Diameter message that was rejected because of local MP congestion and an Answer response was sent.

The connection measurement is associated with the connection from which the message was received.

Measurement Scope: Server Group

Recovery:

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.
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.
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.
The Diameter process may be experiencing problems. The alarm log should be examined using the Alarms & Events page.
If the problem persists, contact My Oracle Support (MOS).