1. Alarms and KPIs
  2. Alarms and Events
  3. IP Front End, IPFE (5000-5999)
  4. 5002 - IPFE Address Configuration Error

3.1.2 5002 - IPFE Address Configuration Error

Alarm Group:
IPFE
Description:
This alarm indicates misconfiguration due to manual changes to the configuration database, configuration data importing errors, or software installation errors. In general, this error is caused by IPFE IP addresses being incorrectly configured.
Severity:
Critical
Instance:
Description of the field or fields that are incorrect.

Note:

If the IPFE is able to successfully synchronize data with its peer, this alarm clears.
HA Score:
Normal
Auto Clear Seconds:
N/A
OID:
ipfeIpfeStateSyncConfigErrorNotify
Cause:
The alarm raises if IPFE IP addresses is configured incorrectly. img/5002.png

The IPFE mates state synchronization is through the connection (IPFE-A1/A2 or B1/B2 IP Address, 19041, TCP). This alarm raises when the connection is not able to be established. Following are few reasons:

  • IPFE-A/B: Addresses both identical - one of the addresses is incorrect
  • IPFE-A/B: Cannot open IPFE device, /dev/recent - xt_recent module in TPD is either missing or incorrect
  • IPFE-A/B: First address bad - invalid address format
  • IPFE-A/B: Second address bad - invalid address format
  • IPFE-A/B: Bind error - cannot bind a socket to this interface address
  • IPFE-A/B: Both addresses empty - it is not possible to leave both addresses empty when configuring from the GUI, but it is possible if data is manually entered from GCLI command
  • IPFE-A/B: Only one sync address may be local - two addresses that both correspond to an interface on the same blade have been entered
  • IPFE-A/B: Peer software version incompatible - the peer IPFE is on a different version
Diagnostic Information:

Collect the following data before contacting My Oracle Support for assistance:

  • iqt -pE Network>Network_$(hostname)
  • iqt -pE L3Interface>L3Interface_$(hostname)
  • Screenshot of Configuration, and then Network, and then Devices, and then <All IPFE Server Tab>.
  • iqt -pE IpfeOption>IpfeOption_$(hostname)
  • iqt -pE IpfeOption>IpListTsa_$(hostname)
  • Screenshot of IPFE, and then Configuration, and then Options.
  • tr.cat ipfe.STK>ipfeSTK_$(hostname)
  • ifconfig>ifconfig_$(hostname)

Recovery:

  1. To correct configuration errors:
    • Read and understand the alarm text. This should have sufficient information to diagnose the configuration error. As a last resort.
    • Navigate to IPFE, and then Configuration, and then Options.
    • Check the IPFE-A1 and IPFE-A2 IP address. You also need to check IPFE-B1 and IPFE-B2 IP addresses, if you have full 4 IPFE servers. You should select INTERNALIMI IP address here. All servers have to be the same IP type.
    • Check the State Sync TCP Port. We suggest you always use the default 19041, if possible.
  2. Ping the local IMI IP address.
  3. Reboot the IPFE servers, if you have permission to do so.
  4. If the alarm is still there, it is recommended to contact My Oracle Support for assistance. Collect this data first:
    • Screenshots for Configuration, and then Network, and then Devices All IPFE Server tab and IPFE, and then Configuration, and then Options.
    • ifconfig>ifconfig_$(hostname)