Why do DHCP failover servers (primary and secondary) land into potential-conflict state?

Solution In Progress - Updated -

Issue

DHCP servers (primary and secondary) with failover configuration keep staying on POTENTIAL-CONFLICT.
While the dhcpd is in POTENTIAL-CONFLICT, it cannot deal with any request from DHCP clients. So, it doesn't work as a DHCP server at all.

 dhcpd failover peer dhcp: I move from resolution-interrupted to potential-conflict
 dhcpd failover peer dhcp: peer moves from partner-down to potential-conflict

Environment

  • Red Hat Enterprise Linux 6.4
  • dhcp-4.1.1-34.P1.el6.x86_64 and dhcp-common-4.1.1-34.P1.el6.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content