Upgrading Dual-WAN + CARP?
-
Any suggestions on how to go about upgrading a dual-wan + CARP setup from 1.2.3 to 2.0 (either now, as RC3, or when final)? Do I upgrade the master or slave first?
-
For any cluster, the suggestion is the same:
- Upgrade the secondary, make sure it boots and runs OK
- Fail over to the secondary as a test, make sure things still work like they should
- If that test failed, reinstall back to the old version on the slave. If it passed, upgrade the master.
- After both are upgraded, repeat any necessary failover tests.
-
Ok, thanks.
-
I would add one step going from 1.2.3 to 2.0, disable the config sync otherwise 1.2.3 will overwrite the config in the wrong format on the 2.0 box (2.0 has a check that prevents config sync to different config versions but 1.2.3 does not)
-
@cmb:
I would add one step going from 1.2.3 to 2.0, disable the config sync otherwise 1.2.3 will overwrite the config in the wrong format on the 2.0 box (2.0 has a check that prevents config sync to different config versions but 1.2.3 does not)
Oh, good one. If I disable the carp sync, will the CARP IPs still fail over to the second box? If not, how exactly do I test the secondary system after the update?
-
Disabling the configuration sync won't disable CARP failover.
