No Failover works, Failover does not work

[Karen Pachla]

I believe this is happening because the servers, now running in
failover, need to sync their databases. As long as they are in recover
state, they will not provide service to DHCP clients. The recover state
will continue until the mclt has expired.

On Wed, 2006-05-17 at 21:29 +0300, Shlomo Dubrowin wrote:
> OK, so I switched the peer ports to 519 and 520.
> Now, when I try to get an address, these messages were recorded.  (Franklin
> is the primary DHCP Server, the MAC Address listed is my machine, and the IP
> 10.153.22.1 is the router IP for the VLAN that is configured as the relay
> agent.):*
> 
> *messages:May 17 21:18:37 franklin dhcpd: DHCPDISCOVER from
> 00:12:3f:1a:60:c3 via 10.153.22.1: not responding (recovering)
> messages:May 17 21:18:42 franklin dhcpd: DHCPDISCOVER from 00:12:3f:1a:60:c3
> via 10.153.22.1: not responding (recovering)
> messages:May 17 21:18:50 franklin dhcpd: DHCPDISCOVER from 00:12:3f:1a:60:c3
> via 10.153.22.1: not responding (recovering)
> messages:May 17 21:19:06 franklin dhcpd: DHCPDISCOVER from 00:12:3f:1a:60:c3
> via 10.153.22.1: not responding (recovering)
> 
> So which machine isn't responding?  the machine trying to get an address
> (the MAC Address) or the cisco router with the IP?
> 
>   Shlomo


-- 
K. Pachla
LSAIT
University of Michigan