3.9.101 22225 - Average Message Size Limit Exceeded

Alarm Group:

DIAM

Description:

The size of the average message processed by DSR has exceeded its configured limits.

The alarm is generated when the measurement RxAvgMsgSize reaches the DSR-wide engineering attributes, defined in the DaMpProfileParameters corresponding to the MP profile being used. RxAvgMsgSize is defined as the size of the average message processed by DSR.

This alarm indicates DSR has encountered a message it can accept for processing, but might not continue processing if the message size increases more than the maximum supported message size. This increase can be due to standard diameter processing (for example, Route Record additions to requests) or due to custom processing (for example, Mediation modifying AVPs).

Severity:

Minor, Major, Critical

Instance:

N/A

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

eagleXgDiameterAvgMsgSizeLimitExceededNotify

Cause:

Alarm 22225 raises when the measurement RxAvgMsgSize reaches the DSR-wide engineering attributes, defined in the DaMpProfileParameters corresponding to the MP profile being used.

RxAvgMsgSize is defined as the size of the average message processed by DSR. The alarm thresholds are configurable from Diameter Common > MPs > Profiles

• Average message size minor alarm onset threshold
• Average message size minor alarm abatement threshold
• Average message size major alarm onset threshold
• Average message size major alarm abatement threshold
• Average message size critical alarm onset threshold
• Average message size critical alarm abatement threshold

The severity of alarm (Minor, Major, or Critical) is according to onset/abatement threshold of each severity level. When the average message size reaches the value of the respective alarm onset/abatement threshold, within 3 seconds the alarm is raised with severity Minor, Major, or Critical, based on the value reached by the average message size.

Diagnostic Information:

This event indicates that DSR has encountered a message that it can accept for processing, but might not continue processing if the message size increases more than the maximum supported message size. This increase can be due to standard diameter processing (for example, RouteRecord additions to requests) or due to custom processing (for example, Mediation modifying AVPs).

Recovery:

1. Examine the traffic coming from connected peers to see if any of them are sending abnormally large messages, and look for any special processing rules being applied by DSR to that message.
2. The alarm thresholds are configurable on Diameter Common, and then MPs, and then Profiles:
   • Average hold time minor alarm onset threshold
   • Average hold time minor alarm abatement threshold
   • Average hold time major alarm onset threshold
   • Average hold time major alarm abatement threshold
   • Average hold time critical alarm onset threshold
   • Average hold time critical alarm abatement threshold
   The severity of the alarm (Minor, Major, or Critical) is according to the 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.
3. If the problem persists, it is recommended to contact My Oracle Support.