You have to upgrade to 8.3 and then to 8.4 version. Start from 8.3 version you have lots of changes in the sysntax. Especially in NAT and few more things. I have pasted the change in commands with specifi to NAT/PAT which was posted in our forumn by an SME. Before going to 8.4 pls go through the doc for 8.4 and understand. Do read the release notes of 8.4 and go for an upgrade.
When you upgrade it should take the configs converted.
I'd like to upgrade to 8.2.5 and even thou there are already some discussions regarding upgrading ASA from 7.2 to 8.2 in failover pair, I'm still not sure I have to:
first reboot primary then secondary
first reboot secondary then primary
in Cisco document the how to perform Zero Downtime Upgrades for Failover Pairs choose the second one, however cause in my case I'm upgrading from 7.2 to 8.2 Zero Downtime Upgrades won't work or at least it is not supported.
Any advice or Cisco documents specific to Upgrading Failover Pairs without Zero Downtime ?
Yes. 1st thing you have to make the standby fw to take charge as the active. reload primary fw and once that comes back and says its okay and waiting as the standby then you can make the other firewall which is active to be forced to go as the standby to make the actual primary as active and reload the secondary. So that there won't be much outage or interupption.... Eventhough we have the interupption that will not be much visible for the endusers.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...