RxNoRulesFailure

Measurement Group: Diameter Ingress Transaction Exception

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: The number of Request messages from a downstream peer rejected by a Local Node because no Peer Routing Rule was found.

Collection Interval: 5 min

Peg Condition: Request message from a downstream peer is rejected by a Local Node because no Peer Routing Rules were found in the peer routing table and the message was not addressed to a peer (either Destination-Host AVP was absent or Destination-Host AVP was present but was not a peer's FQDN).

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

Measurement Scope: Server Group

Recovery:

  1. 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.
  2. 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.
  3. 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.
  4. If no additional congestion alarms are asserted, the Routing Answer Task may be experiencing a problem preventing it from processing messages from its Answer Message Queue. The alarm log should be examined from the Alarms & Events page.
  5. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Diameter Ingress Transaction Exception measurements