I have an upgrade planned on our ASA5520's running an active/standby failover scenario, moving from 7.2(4) 8.2(5)
Reading the release notes and a few other documents online I can see that there are no major syntax changes so should be good to go in that respect. I do however have some concerns over failover with the upgrade.
My plan of attack would be to upgrade the standby to the new code, failover to the upgraded unit and monitor for stability, then do the primary. During this process and when the standby device returns will it automatically join the failover group OK?
From the release notes I can see:
In a failover configuration, the two units must have the same hardware configuration, must be the same model, must have the same number and types of interfaces, must have the same feature licenses, and must have the same amount of DRAM. You do not have to have the same amount of flash memory"
I can confirm all of the above requirements are met but cannot see any reference to different code versions - I presume that failover pair should be OK in this scenario?
Any information provided would be appreciated or any other gotcha's you may envisage me facing
My plan of attack would be to upgrade the standby to the new code, failover to the upgraded unit and monitor for stability, then do the primary'
-The units will not be in Active/Stadby mode anymore when you have different code (major release). The failover will not work. Also, there may be routing issues for the outgoing traffic thru firewalls. The best way is to check the release notes for 8.2(5) code for any open caveats.
Once you've expanded Cisco Secure Endpoint connector deployment to about 50% of your licensed count (check out this article that shows you how to do that), it's time to put those connectors to action i.e. convert them to Protect from Audit mode for vari...
Hello! I’m Betsy, UX Researcher, on the Cisco+ Secure Connect Now team. Nice to meet you all .We have a short survey to learn about your Zero Trust Network Access (ZTNA) journey. Whether you have, plan to, or have not implemented a ...
A set of interface access rules can cause the Cisco Adaptive Security Appliance to permit or deny a designated host to access another particular host with a specific network application (service). When there is only one client, one host and one se...
How To: Cisco ISE Captive Portals with Aruba Wireless
Authors: Adam Hollifield, Brad Johnson
IntroductionPrerequisitesMinimum RequirementsComponents UsedConfigurationAruba Wireless ControllerWLAN CreationAuthentication ConfigurationRole & Policy Confi...
Ready to learn more about SecureX? Our Cisco security expert @Juan Ponce Dominguez reviews the features and benefits of SecureX, as well as a product demo covering:
Customising SecureX dashboards to create a single pane, unified visibility