RxNoRoutesFound

Measurement ID

10035

Measurement Group

Diameter Ingress Transaction Exception

Measurement Type

Simple

Measurement Dimension

Arrayed (by Connection ID)

Description

Number of Request messages from a downstream peer rejected by a Local Node because no routes were available for routing the message.

Collection Interval

5 min

Peg Condition

Request message from a downstream peer is rejected by a Local Node because no routes were available for routing the message. A No Routes Available condition occurs when:

• A Route List was selected via a Peer Routing Rule or implicit routing but its Operational Status was Unavailable
• Implicit routing was invoked and the peer's Operational Status was not Available and an alternate implicit route was not provisioned for the peer

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

Measurement Scope

Server Group

Recovery

1. If the message matched a Peer Routing Rule but none of the peers in the Route List were eligible for routing the message because either their operation state was Unavailable, the Application ID in the Request message did not match an application ID supported by the peer, or the peer had previously processed the message as defined by the Route-Record AVPs in the message:
   1. Verify that IP network connectivity exists between the MP server and the peers.
   2. Check the event history logs for additional DIAM events or alarms from this MP server.
   3. Verify that the peers in the Route List are not under maintenance. It is recommended to contact My Oracle Support for assistance if needed.
2. If the message was addressed to a peer directly connected to the Local Node via the Destination-Host AVP but the peer's operational status was Unavailable or the alternate path to the peer, designated by the peer's alternate implicit route was either not provisioned or was Unavailable:
   1. Verify that IP network connectivity exists between the MP server and the adjacent servers.
   2. Check the event history logs for additional DIAM events or alarms from this MP server.
   3. Verify that the peer is not under maintenance.
3. If the message was addressed to a peer directly connected to the Local Node via the Destination-Host AVP but the application ID in the Request message did not match an Application ID supported by the peer:
   1. 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.
   2. 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.
   3. A software defect may exist resulting in PTR 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 from the Alarms & Events page.
4. It is recommended to contact My Oracle Support for assistance if needed.