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
Recovery:
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 > Configuration > 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.
Ping the local IMI IP address.
Reboot the IPFE servers, if you have permission to
do so.
If the alarm is still there, it is recommended to
contact My Oracle Support (MOS) for assistance. Collect this data first:
Screenshots for the
Configuration > Network > Devices All IPFE Server tab and
IPFE > Configuration > Options.
