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

Previous
Previous
Next
Next

8010 - MpIngressDrop

Alarm Group:
DIAM
Description:
An ingress message is discarded or rejected.
Severity:
Major
Instance:
<DA-MP Name>
HA Score:
Normal
Auto Clear Seconds:
30
OID:
eagleXgDiameterMpIngressDrop
Cause:
An ingress message is discarded or rejected in the following congestion scenarios:
  • Connection maximum message rate exceeded (ingress control).
  • DA-MP maximum message rate exceeded (ingress control).
  • DA-MP CPU congestion (overload control).
  • Diameter message pool congested (routing ingress).
  • Signaling event pool congested (routing ingress).
  • Destination DA-MP unknown (routing ingress).
  • Destination DA-MP congested (routing ingress).
  • DRL request message queue congested (routing ingress).
  • DRL answer message queue congested (routing ingress).
Diagnostic Information:
Collect the following information to diagnose the cause before contacting Oracle Support:
  • Event History on active SO server.
  • Savelogs of all MPs.
  • DSR logs of all MPs.

Recovery:

  1. Potential causes of this alarm are:
    • One or more DA-MPs are unavailable and traffic has been distributed to the remaining DA-MPs.
    • One or more peers are generating more traffic than is nominally expected.
    • There are an insufficient number of DA-MPs provisioned.
    • One or more peers are answering slowly, causing a backlog of pending transactions.