5002 - IPFE address configuration error

Alarm Group: IPFE

Description: The IPFE is unable to synchronize state data with its peer. This alarm can be issued for multiple reasons, including missing or invalid configurations, inability to bind a socket to the given IP address, or incompatible versions of software. The instance column provides more details when this alarm is raised. This alarm is present when the IPFE is activated but not yet configured.

Severity: Critical

Instance: One of the following strings:

"ipfe1 and ipfe2 address both empty" - incomplete configuration
"ipfe1 and ipfe2 address identical" - one of the addresses is incorrect
"IPs are both local" - the two addresses correspond to the same interface on the blade
"ipfe1 bad address" - invalid address format
"ipfe2 bad address" - invalid address format
"bind error" - cannot bind a socket to this interface address
"cannot open ipfe device /dev/recent" - xt_recent module in TPD is either missing or incorrect
"peer software version incompatible" - peer IPFE is on a different version

HA Score: Normal

Auto Clear Seconds: N/A

OID: ipfeIpfeStateSyncConfigErrorNotify

Recovery: If the IPFE is able to successfully synchronize data with its peer, this alarm will clear.

To correct configuration errors, select IPFE > Configuration > Options from the left-hand menu.

The Configuration Options pane appears.
Ensure that IPFE1 IP Address and IPFE2 IP Address are configured correctly.
For issues with modules or versions, contact My Oracle Support (MOS) for assistance.