05-25-2018 01:37 PM - edited 02-21-2020 07:49 AM
Hi,
Currently my ASA pair(active/standby) running 9.1(2) version. I want to update them to 9.9 with no downtime.
My question is: can i update directly from 9.1(2) to 9.9 with no downtime ? If no, can you explain me how properly should i update.
Solved! Go to Solution.
05-25-2018 06:51 PM
Hi
First regarding asa path upgrade, you can go from your version directly to 9.9.
Take a look for validation:
https://www.cisco.com/c/en/us/td/docs/security/asa/asa99/release/notes/asarn99.html#ID-2152-0000000a
Here an official upgrade guide:
To summarize, upgrade for failover asa is straight forward:
- copy new image to active and standby devices.
- change the boot config to boot using new image.
- reload standby with the new image.
- when reloaded, force a failover from active to new reloaded standby.
- reload old active with new software.
- force back active role if you want.
05-25-2018 06:51 PM
Hi
First regarding asa path upgrade, you can go from your version directly to 9.9.
Take a look for validation:
https://www.cisco.com/c/en/us/td/docs/security/asa/asa99/release/notes/asarn99.html#ID-2152-0000000a
Here an official upgrade guide:
To summarize, upgrade for failover asa is straight forward:
- copy new image to active and standby devices.
- change the boot config to boot using new image.
- reload standby with the new image.
- when reloaded, force a failover from active to new reloaded standby.
- reload old active with new software.
- force back active role if you want.
05-28-2018 01:53 AM
Hi Francesco,
Thank you. Yesterday i successfully updated to 9.9(2) version.
However, after update our branch office lost connectivity to internet through s2s.
The branch still access to HQ internal network but not to internet.
Please help me to solve the problem.
05-28-2018 04:44 AM
05-28-2018 06:13 AM
Francesco,
I found the problem.
I had NAT rule like this:
nat (NETWORK1,outside) source static any any destination static NETWORK_OBJ_172.16.48.0_27 NETWORK_OBJ_172.16.48.0_27
subnet 172.16.48.0 255.255.255.0
nat(outside,outside) dynamic interface
And its had been working before update. After some debugging i found that ASA trying to NAT traffic from 172.16.48.0 to NETWORK1 interface.
I changed "source static any any" to "source static NTW_1 NTW_1" and now its working.
Anyway thanks for support.
05-28-2018 04:00 PM
01-07-2019 06:24 AM
01-07-2019 09:08 AM
Hi,
I dont remember about stateful connections whether they failed over or not but i didnt have any system disruption.
01-07-2019 09:32 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide