https://doc.pfsense.org/index.php/Upgrade_Guide#Upgrading_High_Availability_Deployments
"Generally the recommended path for upgrading a High Availability cluster is to first upgrade the secondary node." -- Steve Yates ITS, Inc. -----Original Message----- From: List [mailto:[email protected]] On Behalf Of Mike Montgomery Sent: Tuesday, May 10, 2016 3:55 PM To: pfsense mail list <[email protected]> Subject: [pfSense] 2.2.6 HA to 2.3 Upgrade Advice I have two servers, setup in high availability that are currently running 2.2.6. I have been running 2.3 at home and my test servers and am ready to upgrade the office to 2.3 as well. I have been reading several upgrade guides, as to which one to upgrade first, but would like to see if anyone has upgraded a HA setup yet successfully? What I am looking at doing, is disable carp, and upgrade the master after I make backups, and take a snapshot of the machines to roll back to if needed (they are vm's). Then once everything is upgraded on master, allow carp to switch back, then upgrade secondary. Should this work? Going from 2.2.6 to 2.3, if I do the master first, do I need to disable the sync from master until the secondary is upgraded as well? Have not seen much specified for 2.3, only 2.1 to 2.2 upgrades. Thanks _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
