how to upgrade the failover pair?

Bob Harold rharolde at umich.edu
Thu May 31 16:06:45 UTC 2018


On Thu, May 31, 2018 at 11:26 AM Bill Shirley <
bill at c3po.polymerindustries.biz> wrote:

> I am running a fail-over pair:
> primary = dhcp-server-4.3.6-9.fc27.x86_64
> secondary = dhcp-4.2.5-23.fc19.x86_64
>
> So yes, I think 4.1.1 and 4.3.5 would speak the same language.
>
> Bill
>
>
> On 5/31/2018 6:40 AM, Алексей Перов wrote:
> > You mean 4.1.1 and 4.3.5 use the same failover protocol and can talk to
> each other without any issue?
>

You could try it, and if it fails to sync it should give some error in the
logs.

-- 
Bob Harold


> >
> > 31.05.2018 12:41, Simon Hobson пишет:
> >> Aleksey Perov <a.perov at sura.ru> wrote:
> >>
> >>> The draft plan is as follows:
> >>>
> >>> - stop the secondary;
> >>> - turn the primary into partner-down;
> >>> - reinstall the secondary;
> >>> - wait until the primary reclaims all addresses in all pools;
> >>> - stop the primary;
> >>> - copy leases file from primary to secondary;
> >>> - start the secondary in partner-down mode;
> >>> - reinstall the primary;
> >>> - turn the secondary into normal mode;
> >>> - start the primary.
> >>>
> >>> Is anything wrong here?
> >>
> >> Isn't the simplest - provided they are using the same level of failover
> protocol - to simply start up a clean upgraded
> >> secondary and allow it to transfer leases from the primary ? So :
> >>
> >> Stop one partner, put the remaining one into partner down state.
> >> Create new upgraded clean partner.
> >> Start up new partner and allow the pair to synchronise.
> >>
> >> Repeat for the other partner.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20180531/14e49988/attachment.html>


More information about the dhcp-users mailing list