The average transaction hold time has exceeded its configured limits.
This alarm is generated when KPI #10098 (TmAvgRspTime) exceeds DSR-wide engineering attributes associated with average hold time, defined in the DA-MP profile assigned to the DA- MP server. KPI #10098 is defined as the average time (in milliseconds) from when the routing layer (DRL) receives a request message from a downstream peer to the time that an answer response is sent to that downstream peer. The source measurement of KPI #10098 is the TmResponseTimeDownstreamMp (10093) measurement.
Alarm 22224 is generated when KPI #10098 (TmAvgRspTime) exceeds DSR-wide engineering attributes associated with average hold time, defined in the DA-MP profile assigned to the DA-MP server. KPI #10098 is defined as the average time (in milliseconds) from when the routing layer (DRL) receives a request message from a downstream peer to the time that an answer response is sent to that downstream peer. The source measurement of KPI #10098 is the TmResponseTimeDownstreamMp (10093) measurement.
The alarm thresholds are configurable on Diameter Common > MPs > Profiles.
The severity of the alarm (Minor, Major, or Critical) is according to onset threshold/abatement threshold of each severity level. When the average hold time initially exceeds the average hold time for an alarm onset threshold, a minor, major, or critical alarm is triggered. When the average hold time subsequently exceeds a higher onset threshold, or drops below an abatement threshold, but is still above the minor alarm abatement threshold, the alarm severity changes based on the highest onset threshold crossed by the current average hold time.
If Alarm #22224 is raised, then it indicates the average response time (TmAvgRspTime) for messages forwarded by the Relay Agent is larger than the defined for a deployment as per DA-MP profile assignment. One of the following problems could exist:
One or more MPs is experiencing traffic overload.
Recovery: