3.1.1 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:
- From the SO GUI,
navigate to
If yes, go to step 2.
; and at least one DAMP
server XSI IP should be present.
- Log into the IPFE
server.
- Ping <the DAMP server XSI IP>
- Telnet
<the DAMP server XSI IP>
<monitoring port, default 9675>
If steps a or b fail, go to step 3.
- ssh admusr@<DAMP server
XMI>.
- 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.
- 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.
- From the SO GUI,
navigate to
Recovery:
- Check the status of the application servers by navigating to the page.
- Consult the application server's documentation for recovery steps.
- If the application server is functioning, check for network connectivity issues between the IPFE and the application server.
- It is recommended to contact My Oracle Support if further assistance is needed.