interface Ethernet0/1 nameif inside security-level 100 ip address 10.1.26.111 255.255.255.0 !
interface Ethernet0/2 nameif VMWARE security-level 75 ip address 10.1.110.100 255.255.255.0 !
hostname atest1 enable password someencryptedpassword encrypted passwd somepasswordalsoencrypted encrypted names !
interface Ethernet0/0 nameif outside security-level 0 ip address 188.8.131.52 255.255.255.0 !
In order to show you the upgrade of the failover pair, I need to go back to 8.2 version on this appliance and make a failover cluster with the other one, also running the 8.2 code. Please make a note that the “downgrade” process can have an optional argument “activation-key”.
This has to be considered if some features needs to be turned off, that are not supported in the old code.
My configuration has some ACLs and some NAT statements, among other things.
Or should I say This can be tricky and I strongly recommend consulting the documentation on your specific versions to select a proper upgrade path.Please also refer to the ASA 8.3 migration guide for a complete explanation of the automated migration process.INFO: MIGRATION – Saving the startup configuration to file INFO: MIGRATION – Startup configuration saved to file ‘flash:8_2_5_0_startup_cfg.sav’ *** Output from config line 4, “ASA Version 8.2(5) ” NAT migration logs: nat (inside) 1 192.168.0.0 255.255.255.0 INFO: NAT migration completed.More on this some other time, I just want you to know about this.Now both appliances have the same code and we make them a failover cluster, according to this blog post. And it won’t break any existing sessions, as the previous upgrade example would, because of the reboot.