22022 - Forwarding Loop Detected

Alarm Group:

DIAM

Description:

Ingress Request message received was previously processed by the local node as determined from the Route-Record AVPs received in the message.

Severity:

Major

Instance:

<Peer Name>

HA Score:

Normal

Auto Clear Seconds:

30

OID:

eagleXgDiameterForwardingLoopDetectedNotify

Recovery:

1. An ingress request message was rejected because message looping was detected. In general, the forwarding node should not send a message to a peer that has already processed the message (it should examine the Route-Record AVPs before message forwarding). If this type of error is occurring frequently, then the forwarding node is most likely mis-routing the message. This should not be related to a configuration error because the identity of the local node is sent to the peer during the Diameter Capabilities Exchange procedure when the Connection comes into service.
2. If Path Topology Hiding is activated and Protected Network Node's Route-Records are obscured with PseudoNodeFQDN, then inter-network ingress message loop detection could reject the message if same Request message is routed back to DEA. If this type of error is occurring then the forwarding node is most likely mis-routing the message back to DEA.
3. If the problem persists, it is recommended to contact My Oracle Support (MOS).