3.9.11 8010 - MpIngressDrop

Alarm Group:

DIAM

Description:

An ingress message is discarded or rejected.

Severity:

Major

Instance:

<DraWorker 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).
• DraWorker maximum message rate exceeded (ingress control).
• DraWorker CPU congestion (overload control).
• Diameter message pool congested (routing ingress).
• Signaling event pool congested (routing ingress).
• Destination DraWorker unknown (routing ingress).
• Destination DraWorker 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.
• Peer CNDRA logs of all MPs.

Recovery:

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