22077 - Excessive Request Reroute Threshold Exceeded

Alarm Group:

DIAM

Description:

Request reroutes due to Answer response and/or Answer timeout having exceeded the configured onset threshold percentage on the DA-MP server.

Severity:

Major

Instance:

MpReroutePercent

HA Score:

Normal

Auto Clear Seconds:

N/A

Note:

The alarm clears when the percentage of Request reroutes due to Answer Result-code matching "Reroute on Answer" and Answer Timeout drops below the configured abatement threshold and remains there for the configured abatement time. The alarm also clears when the DSR process is stopped or restarted.

OID:

eagleXgDiameterMpExcessiveRequestRerouteNotify

Recovery:

1. This alarm is an indication of reroutes exceeding the configured threshold, due to responses from the Peer Node exceeding the Pending Answer timer in DSR or due to configured "Reroute on Answer" Result codes.
2. If rerouting is triggered due to Answer Result-code:
   1. Use measurement TxRerouteAnswerResponse to identify any peer (or set of peers) being identified as triggering reroute.
   2. If a peer (or set of peers) is identified, validate that Reroute-on-Answer is properly configured for that peer.
   3. Check for congestion being reported by the peer (Diameter > Maintenance > Peer Node).
3. If rerouting is triggered due to Answer Timeout:
   1. Use measurement TxRerouteAnswerTimeout to identify any peer (or set of peers) being identified as timing out.
   2. If a peer (or set of peers) is identified, verify that Pending Answer Timer and Transaction Lifetime are properly configured.
   3. Check for congestion being reported by the peer (Diameter > Maintenance > Peer Node).
4. If the problem persists, it is recommended to contact unresolvable-reference.htm#GUID-DD0927BD-FD0B-4CEB-86E9-98A33C12D4E0.