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

Previous
Previous
Next
Next

5001 - IPFE Backend Unavailable

Alarm Group:
IPFE
Description:
The IPFE has not received any heartbeats from an application server within the heartbeat timeout interval.
Severity:
Minor
Instance:
IP address of the application server.

Note:

If a heartbeat is received from the application server, this alarm clears.
HA Score:
Normal
Auto Clear Seconds:
N/A
OID:
ipfeIpfeBackendUnavailableNotify
Cause:
A DA-MP is not sending heartbeats to the IPFE.
Diagnostic Information:

Wireshark is the tool to monitor if the DAMP is sending a heartbeat to IPFE.

Follow these steps to diagnose the issues:

  1. From the SO GUI, navigate to IPFE > Configuration > Target Sets > TSA# > + at least one DAMP server XSI IP should be present.

    If yes, go to step 2.

  2. Log into the IPFE server.
    1. Ping <the DAMP server XSI IP>
    2. Telnet <the DAMP server XSI IP> <monitoring port, default 9675>

      If steps a or b fail, go to step 3.

  3. ssh admusr@<DAMP server XMI>.
    1. Run the sudo netstat -anop | grep <monitoring port, default 9675> command to see if there is a TCP listen socket on that DAMP XSI IP.

      If yes, check the DAMP XSI network (hardware and software).

      If no, check the configuration of the DAMP.

Recovery:

  1. Check the status of the application servers by navigating to the Status & Manage > Server page.
  2. Consult the application server's documentation for recovery steps.
  3. If the application server is functioning, check for network connectivity issues between the IPFE and the application server.
  4. It is recommended to contact My Oracle Support for assistance.