5005 - IPFE Backend In Stasis

Alarm Group:

IPFE

Description:

The IPFE has received a heartbeat packet from the application server that indicates the application server is unwilling to accept new connections. However, the application server continues to process existing connections. The application server sends a stasis heartbeat message for the following reasons:

• The application server has reached its maximum number of active Diameter connections
• The application server is congested. The application server also raises 22200 - MP CPU Congested.

Severity:

Minor

Instance:

IP address of the application server in stasis

HA Score:

Normal

Auto Clear Seconds:

N/A

OID:

ipfeIpfeBackendInStasisNotify

Cause:

The application server has reached is maximum resource capacity.

When one or more of the DAMPs in the cluster reaches its capacity. The DAMP servers that reach their capacity sends Stasis messages to the IPFE servers.

When the IPFE servers received this stasis message, the IPFE will:

• Raise this 5005 alarm.
• Keep processing the existing connection to this stasis DAMP server.
• Route any NEW connection (TCP SYN, SCTP INIT) to other un-stasis servers in the cluster.

The IPFE clears this alarm when the IPFE server receives no more stasis message from the DAMP servers.

It usually tells that more back-end DAMP servers are required to extend the capacity when this alarm is present. Contact Oracle support team to help diagnose the issue.

Diagnostic Information:

Collect following data before contacting Oracle Support:

1. Export the alarm history.
2. iqt -pE IpfeOption>IpfeOption_$(hostname)
3. iqt -pE IpListTsa>IpListTsa_$(hostname)
4. ipfe.STK>ipfeStk_$(hostname)
5. Screenshot of Diameter->Maintenance->DA-MPs->DA-MP Connectivity.

Recovery:

1. When the IPFE receives heartbeats from the application server indicating that it is willing to accept new connections, this alarm clears.