Standalone Firewall Upgrade from 9.1 to 10.2.5
HA Firewall Upgrade from 9.1 to 10.2.x
HA Firewall Upgrade from 9.1.0 to 10.2.x
FW-A has priority 50, preemptive is Enabled, status is Active; FW-B has priority 100, preemptive is Enabled, status is Passive.
- Backup configuration.
- Install latest content release on both units. Verify HA status and configuration is in sync.
- ======Patch to 9.1.x=========
- FW-A, disable preemptive, submit the change.
- FW-A, download 9.1.x (synch to peer)
- Suspect FW-A, check HA status: FW-A is Suspended / FW-B is Active
- FW-A install 9.1.x then reboot.
- When FW-A is back up, verify version is 9.1.x, HA status: FW-A is Passive/ FW-B is Active.
- Suspend FW-B, check HA status: FW-A is Active / FW-B is Suspended.
- FW-B install 9.1.x then reboot.
- When FW-B is back up, verify version is 9.1.x, HA status: FW-A is Active / FW-B is Passive.
- ======Upgrade to 10.0.x=========
- FW-A, download 10.0 (synch to peer), No install, download 10.0.x (synch to peer)
- Suspend FW-A, check HA status: FW-A is Suspended / FW-B is Active
- FW-A install 10.0.x then reboot.
- When FW-A is back up, verify version is 10.0.x, HA status: FW-A is Passive / FW-B is Active.
- Suspend FW-B, check HA status: FW-A is Active/ FW-B is Suspended.
- FW-B install 10.0.x then reboot
- When FW-B is back up, verify version is 10.0.x, HA status: FW-A is Active / FW-B is Passive.
- ======Upgrade to 10.1.x=========
- FW-A, download 10.1 (synch to peer), No install, download 10.1.x (synch to peer).
- Suspect FW-A, check HA status: FW-A is Suspended / FW-B is Active.
- FW-A install 10.1.x then reboot.
- When FW-A is back up, verify version is 10.1.x, HA status: FW-A is Active/ FW-B is Non-functional (version mismatch).
- FW-B install 10.1.x then reboot
- When FW-B is back up, verify version is 10.1.x, HA status: FW-A is Active / FW-B is Passive.
- ======Upgrade to 10.2.0===============
for some reason, download 10.2.0 then download 10.2.x cause both downloaded images disappear. - FW-A download 10.2.0 (synch to peer)
- Suspect FW-A, check HA status: FW-A is Suspended / FW-B is Active.
- FW-A install 10.2.0 then reboot.
- When FW-A is back up, verify version is 10.2.0, HA status: FW-A is Passive / FW-B is Active.
- Suspend FW-B, check HA status: FW-A is Active/ FW-B is Suspended.
- FW-B, install 10.2.0 then reboot.
- When FW-B is back up, verify version is 10.2.0, HA status: FW-A is Active / FW-B is Passive
- ======Upgrade to 10.2.x===============
- FW-A download 10.2.x (synch to peer)
- Suspect FW-A, check HA status: FW-A is Suspended / FW-B is Active.
- FW-A install 10.2.x then reboot.
- When FW-A is back up, verify version is 10.2.x, HA status: FW-A is Passive / FW-B is Active.
- Suspend FW-B, check HA status: FW-A is Active/ FW-B is Suspended.
- FW-B, install 10.2.x then reboot.
- When FW-B is back up, verify version is 10.2.x, HA status: FW-A is Active / FW-B is Passive
- FW-A, enable preemptive, submit the change.
Upgrade from CLI
1. Current is 9.1.6, download 9.1.11 image:
IMPORTANT NOTE:
When upgrading a HA Active/Passive firewall pair across multiple feature releases, for example from 9.0.14 to 10.0.7, it has to be made sure that both Firewalls in HA are upgraded to the same Feature release every time before moving on the next feature release.
If Firewall-A has been upgrade to 9.1.x as the intermediate step, then Firewall-B also has to be upgraded to 9.1.x before Firewall-A can be upgraded to 10.0.7
If there is more than 1 version of difference between the HA pairs, "Peer version too old" issue will happen.
1. Disable Preempt
Lower Preempt number has higher priority
Traffic failover test must have been conducted before the start of upgrade process to make sure both Firewalls are capable of passing traffic without issues. Disable Preemption if enabled.
- Disable Preemption on High Availability settings to avoid unexpected failover.
- Disabling preempt configuration change must be committed on both peers.
- Once upgrade is completed, re-enabling must be committed on both peers.
Comments
Post a Comment