RxRuleDuplicatePriority

Measurement Group: Peer Routing Rules

Measurement Type: Simple

Measurement Dimension: Arrayed (by Peer Routing Rule ID)

Description: The number of times that the Peer Routing Rule was selected for routing a message but another Peer Routing Rule had the same priority and was ignored.

Collection Interval: 5 min

Peg Condition: When the DSR searches the Peer Routing Rules and finds more than one highest priority Peer Routing Rule with the same priority that matches the search criteria.

The measurement is associated with the Peer Routing Rule that is selected for 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.
A software defect may exist resulting in PDU buffers not being deallocated to the pool. This alarm should not normally occur when no other congestion alarms are asserted. The alarm log should be examined using the Alarms & Events page.
If the problem persists, contact My Oracle Support (MOS).