TxReqMsgPerConnPtrMax

Measurement Group: Diameter Exception

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: The number of times message routing bypassed the connection because the maximum allowed pending transactions was exceeded.

Collection Interval: 5 min

Peg Condition: Each time the DSR bypasses a transport connection during route selection because the maximum number of pending transactions allowed for the connection was exceeded.

The connection measurement is pegged against the egress connection with the maximum number of pending transactions condition which prevented message routing.

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.
If no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing it from processing messages from its Request Message Queue. The alarm log should be examined from the Alarms & Events page.
If the problem persists, contact My Oracle Support (MOS).