IP Conflict Displayed When a Passive Server is Restarted

Follow

Summary

This knowledgebase article provides information about a patch to resolve an IP conflict displayed when a passive server is restarted.


More Information

Note: Please contact Neverfail Support before installing this patch.

Symptoms

The passive server is rebooted and an IP conflict is reported. The System Event log contains the message "Could not find Neverfail Heartbeat configuration in registry."

Cause

When a Heartbeat server starts, the packet filter gets a value from the registry which identifies whether the server is in the active or passive state (Passthru or Filter). In situations where the filter fails to obtain the appropriate value from registry, the default is set to 'Passthru'. If this occurs on the passive server, then both the active and passive servers are simultaneously connected to the network. An IP Conflict will occur briefly until the configuration can be read.

Resolution

To resolve this issue, follow the steps below:

  1. Shutdown Neverfail Heartbeat on both servers.
  2. Add the following Value to the registry of the Primary server.

    HKLM\System\CurrentControlSet\Services\NfPktFltr\Parameters\DefaultToFilterOnStart (This should be a string, and should be set to "TRUE")
  3. Repeat the process on the Secondary server.
  4. Restart Neverfail Heartbeat on both servers.


Applies To

All Versions


Related Information

None

KBID-336

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.