I upgraded a 5520 using this information a few months ago but the upgrade failed. The device booted and I was able to log in via console but I could not reach the interfaces and passive would not pass through the device. I ended up restoring the previous software and config and have since upgraded to new 5500x series devices. I am concerned I will run into this issue again even after following the path recommendation, 8.2(x) to 8.4.6 to 8.4.7. I will be doing this remotely with someone on the remote end setting up console access via an oob network and rdp or webex so a failure to boot situation really is not an option. Any ideas on what happened and how I could avoid it this time around? The boot logs showed no indication as to why this happened.
The "no cfg structure..." issue generally hits you before you ever do the actual upgrade - it prevents successful transfer of the new image onto the target ASA's flash (disk0:).
I've upgraded dozens of firewalls and never had one fail to boot and/or become inaccessible. Where I've encountered issues has generally been around fine tuning some NAT rules or access-lists after the parser translates the pre-8.3 commands.
If you have Cisco Smartnet support you can always open a proactive TAC case to request assistance.
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...