RxMessageLooping

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 message looping was detected (FQDN of the Local Node associated with the ingress transport connection matched a FQDN in the messages' Route-Record AVPs).

Collection Interval: 5 min

Peg Condition: Request message from a downstream peer is rejected by a Local Node with Result-Code 3005 (DIAMETER_LOOP_DETECTED).

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

Measurement Scope: Server Group

Recovery:

  1. An excessive amount of Request message rerouting may have been triggered by either connection failures or Answer timeouts. The status of connections should be examined from the Diameter > Maintenance > Connections page.
  2. 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 using the Alarms & Events page.
  3. If the problem persists, contact My Oracle Support (MOS).
Parent topic: Diameter Ingress Transaction Exception measurements