Sure, it will be master anyway as long as the master is down. In case you want to make it the new "real master" just change the adverising frequency of your VIPs to 0 and add the new node you are about to setup as sync IP at carp settings with the appropriate sync options. This way you can sync over to the new system you are about to setup after making only the basic IP settings and adding firewallrules so the new master can sync over.
Holger > -----Original Message----- > From: Derrick MacPherson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 05, 2006 12:11 AM > To: [email protected] > Subject: Re: [pfSense Support] boot problems after update > > > Can I do this, move the slave to a CARP master? > > On Tue, 2006-04-04 at 11:37 -0700, Derrick MacPherson wrote: > > # /etc/rc.firmware pfSenseupgrade /tmp/pfSense-Full-Update- > > RELENG_1_SNAPSHOT_04-03-2006.tgz > > tar: Error opening archive: Failed to open '-C': No such file or > > directory > > Shutdown NOW! > > shutdown: [pid 12380] > > > > > > The system does now not see the hdd, I'll grab the iso and > try a fresh > > install, but now that my CARP slave is master, should I make it the > > permanent master so the configuration will be copied over? > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ____________ Virus checked by G DATA AntiVirusKit --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
