CARP - How to promove Slave to Master
-
Hi guys, first of all sorry for my english…
I need some help...I have 2 pfsense servers running CARP but they were in 2.1.5 version and I needed run a update version into this servers.
I installed the pfsense 2.2.6 on my Slave (he are running on ESXI), I did all the configurations and through the Master sync all the configurations to the new Slave Server, up to this point everything was perfect.
Now I have problems, I would like to do the same with the Master Server, I wanna sync the Slave (or promove this Slave to a Master Server) with this new server...
I tryed to disable CARP on Slave, and changed the Skew to 0 on VIP, after re-enabled CARP the servers flopping to BACKUP and then back to MASTER...and the CARP doesn't work...
I would like to know how is the best way to sync my Slave carp with this new server, or promove this Slave to a Master to sync all the configurations with this new server?
-
If you just want to push the backup to take over the master role for the update, on master go to Status > CARP and press "Enter persistent CARP maintenance mode" and run the update.
When the update has finished, come back to this tab and press "Leave maintenance CARP mode". -
I will try this, but If I can change the Slave to Master I think this is a better solution…because I made some new configurations on the Slave Server who is running now as Master (CARP)
My "old" Master Server is off now, just the Slave is running. Do you now how I can change this is Slave to a Master now?
-
That's generally what I do.
1. Update the secondary (backup)
2. Reboot it and let CARP/pfSync stabilize
3. Enter persistent maintenance mode on primary (master) - traffic swings to secondary (new master)
4. Run it a while to be sure everything's working.
5. Update the primary
6. Reboot let everything stabilize (Give it time for states to sync, etc)
7. Leave persistent maintenance mode on primary. Traffic swings back. -
I understood, but in my case I formated the Master. I didn't do the update, I installed the 2.2.6 version…
What can I do in this case?
-
There is a good section in the book about bringing up a new HA member. That's what I use. It's for 2.1.5 but I've used it on 2.2.X.
A key issue is to add interfaces in the same order. There is a lot to be done "just so" esp if the active unit is in production.
If you have a third, identical unit you might restore a backup to it and get the new HA member configured on the work bench.
