2.2.2 fails to start after 2.1.5 config restore
-
Installed a fresh 2.2.2 x64 server in my lab. Boots up fine, i can log in fine in web console and run "wizard". Everything fine with a clean install.
After restoring configuration (All without RRD) from 2.1.5 x86 the new 2.2.2 firewall doesn't boot anymore.It will just stay in the state in the attachement…forever. Host is not pingable or anything. But it reacts if I disconnect a NIC, setting state to "DOWN" instead of "UP".
I would rather not see this happen when i do the switch in the live environment. Any idea?
-
That's where it switches to serial console. Your restored config must enable the serial console. It's booting all the way to an interface assignment prompt, you just can't see it as you're not on the serial console.
Set the primary console to VGA in your config backup by setting:
<primaryconsole>video</primaryconsole>Replacing "serial" with "video" there.
-
Ah, thanks!
I did not have a entry like that in the backup. But after som try-and-errors (thank god for snapshots!!!) i figured out to go to "System->Advanced->Serial Communications->Change to VGA" on the 2.1.5 system, save the configuration and take a backup again adds the following to the XML:<system><serialspeed>9600</serialspeed> <primaryconsole>video</primaryconsole></system>Now it boots fine after restoring config :)