My boss wants me to pull the 515 failover from production to test the upgrade to the latest release.
I had thought I'd run across something somewhere saying something about whether it's ok or not ok but I cannot find that information again.
Anyone know if there would be a problem running the latest OS using a FO license? (If the FO has no issue we will upgrade the UR and place the FO back to replicate from the UR to continue normal operation.)
Wouldn't it be possible to run the FO upgrade scenerio and then if all is good with our current config with the new IOS, upgrade the primary, clear the FO and pair it with the primary to replicate the config?
I guess I could pull the primary and leave the FO device up. From what I understand the only issue with FO as stand-alone is that it will restart every 24 hours However, if the primary has a UR license and a failover was detected then the FO device will work normally unless it's manually rebooted.
I can power down and upgrade the IOS on the primary and be sure the config is error free then move on from there I guess.
We are running 6.3(3) all 6 interfaces used.
Failover cable only, no stateful or lan based failover.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...