Update procedure

David Coulthart davec at columbia.edu
Thu Mar 26 20:18:36 UTC 2009


On Mar 24, 2009, at 7:05 PM, David W. Hankins wrote:
> On Tue, Mar 24, 2009 at 02:39:00PM +1100, Glenn Satchell wrote:
>> It is probably only necessary to wait a few minutes until the  
>> secondary
>> server has synchronised with the primary before updating the primary.
>> The reason for this is that different versions are not guaranteed to
>> inter-operate as far as failover goes.
>
> The only failover incompatibility is between 3.0.x and 3.1.x.

What would the update procedure look like if you need to do an upgrade  
from 3.0.x to 4.1.x?  If I upgrade one server to 4.1.x without taking  
down the second one still running 3.0.x (so I don't cause an outage  
for my users) will dhcpd recognize that they're trying to speak  
incompatible versions of the failover protocol and just refuse to talk  
to one another?  Or could this result in some form of lease file  
corruption so I have to take both servers down before bringing them up  
on 4.1.x (causing a brief outage for users)?

Thanks,
Dave Coulthart



More information about the dhcp-users mailing list