22005 - No peer routing rule found
- Event Type:
- DIAM
- Description:
- A message not addressed to a peer (either Destination-Host AVP was absent or Destination-Host AVP was present but was not a peer's FQDN) could not be routed because no Peer Routing Rules matched the message.
- Severity:
- Info
- Instance:
- <MPName>
- HA Score:
- Normal
- Throttle Seconds:
- 10
- OID:
- eagleXgDiameterNoPrtRuleNotify
- Cause:
-
Ingress-request message from a downstream peer is rejected by a Local Node when no peer-routing rules are found in the Peer Routing Table (PRT) and one of the following is true:
- The ingress-request message did not contain a Destination-Host AVP or
- The ingress-request message contained a Destination-Host AVP but did not match with any configured peer node's FQDN or
- Destination-Realm AVP value and the Application-ID in the request message header did not match with configured Realm/Application-Id in Realm Route Table
The Realm Route Table (table RealmRoute) managed object is used to perform message routing based upon the Destination-Realm and Application-ID in a request message. The Realm Route Table is dynamically configured on the active Overseer via Diameter > Configuration > Peer Discovery > Realms.
- Diagnostic Information:
-
Analyze the event history and event #22005 which will have following information regarding the failure diameter message:
- <TransConnName> (Receiving connection)
- <PeerName> (Name of the receiving peer )
- <DestRealm> (Value found in Request message Destination-Realm AVP)
- <ApplicationID> (Application ID in the Request message)
- <DestHostFQDN> (FQDN found in request message Destination-Host AVP, if present)
- <OriginHostFQDN> (FQDN found in request message Origin-Host AVP)
The Diameter Ingress Transaction Exception group measurement report contains the RxNoRulesFailure (10034) measurement, which is also pegged in the same scenario.
Recovery:
- Either the message was incorrectly routed to this node or additional Peer Routing Rules need to be added. View and update the Peer Routing Rules by navigating to Diameter > Configuration > Peer Routing Rules.
- If multiple peer routing tables are used, ensure the correct table is applied for the message in question.
- If the problem persists, it is recommended to contact My Oracle Support.
