Go to primary content
Oracle® Communications Alarms and KPIs
Release 8.3
E93200
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

22328 - Connection is processing a higher than normal ingress messaging rate

Alarm Group:
DIAM
Description:
The diameter connection specified in the alarm instance is processing a higher than normal ingress messaging rate.
Severity:
  • Minor (if all of the following are true):
    • The average ingress MPS rate the connection is processing has reached the percentage of the connection's maximum ingress MPS rate configured for the connection minor alarm threshold.
    • The average ingress MPS rate the connection is processing has not yet reached the percentage of the connection's maximum ingress MPS rate configured for the connection major alarm threshold.
  • Major (if the following are true):
    • The average ingress MPS rate the connection is processing has reached the percentage of the connection's maximum ingress MPS rate configured for the connection major alarm threshold.
Instance:
The name of the diameter connection as defined by the TransportConnection table
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterIngressMpsRateNotify
Cause:
Alarm # 22328 raises the severity,
Minor (if all of the following are true):
  • The average ingress MPS rate that the connection is processing has reached the percentage of the connection's maximum ingress MPS rate configured for the connection minor alarm threshold.
  • The average ingress MPS rate that the connection is processing has not yet reached the percentage of the connection's maximum ingress MPS rate configured for the connection major alarm threshold.
Major (if all of the following are true):
  • The average ingress MPS rate that the connection is processing has reached the percentage of the connection's maximum ingress MPS rate configured for the connection major alarm threshold.
Diagnostic Information:
To get further information regarding this issue:
  1. Examine the alarm log from Main Menu > Alarms & Events on Active SOAM Server.

  2. Get the Connection ID IcRate[Connection_Id] from Alarm Details and the corresponding Connection Name from TransportConnectionTable on active SOAM server.
  3. Investigate the connection's remote Diameter peer (the source of the ingress messaging) to determine why they are sending the abnormally high traffic rate.

Recovery:

  1. The Diameter connection specified in the Alarm Instance field is processing a higher than expected average ingress Diameter message rate. The alarm thresholds for minor and major alarms are configured in the Capacity Configuration Set used by the Diameter connection.
  2. The message rate used for this alarm is an exponentially smoothed 30 second average. This smoothing limits false alarms due to short duration spikes in the ingress message rate.
  3. If the alarm severity is minor, the alarm means the average ingress message rate has exceeded the minor alarm threshold percentage of the maximum ingress MPS configured for the connection.
  4. If the alarm severity is major, the alarm means the average ingress message rate has exceeded the major alarm threshold percentage of the maximum ingress MPS configured for the connection.
  5. This alarm is cleared when the average ingress message rate falls 5% below the minor alarm threshold, or the connection becomes disabled or disconnected. This alarm is downgraded from major to minor if the average ingress message rate falls 5% below the major alarm threshold.
  6. If the average ingress message rate is determined to be unusually high, investigate the connection's remote Diameter peer (the source of the ingress messaging) to determine why they are sending the abnormally high traffic rate; otherwise, consider increasing either the connection's maximum ingress MPS rate or the connection's alarm thresholds.
  7. If the problem persists, it is recommended to contact My Oracle Support.