Forum Discussion
Procedure of upgrading from BIG IP v11.4.1 (Build 635.0) to 11.6.3.1
- Can you please mention the procedure in details ?
- I read in some article that forced offline is not really needed in 11.6 version while upgrading. We can directly install the image, re-active the license and reboot from new volume, then stand-by device will come up as standby.
- And then we can make Active as "Force to standby" and reboot post installation of the image.
Please reply.
- Samir_Jha_52506
Noctilucent
Steps are correct but do on different order.
1) Take the backup of both unit.
2) Activate license on standby device.
3) Upgrade standby device(image n hotfix)
4) Validate the behavior of device(memory, CPU, interface packet in n out, etc)
5) Failover device from standby to active
6) Do the same steps on other node(repeat steps 2 to 4)
7) sync both unit.
Cheers...
- RaghavendraSY_7
Cumulonimbus
Yes. You are right but still, suggest you go with offline configuration.
- Open proactive request with the f5 vendor
- Verify console connectivity
- Backup existing configuration
- On activity day, start upgrade process with standby
- Relicense standby device
- Upgrade the device to a new version
- Boot with new volume/version
- Failover the traffic from active to newly upgraded device
- Verify the connectivity and compare pre and post-upgrade configuration
- Do similar steps (5 to 9) for another device
- Sabya_361427
Nimbostratus
I had a doubt on step 8 - Let me drop my queries in very clear way. Please reply question wise.
- Do I need to perform Force Offline before following steps - 5 to 7 ?
- Do I need to do Release Offline before upgrade or post upgrade ?
- Will it come as Standby as it was earlier before the upgrade ?
After I ensure the traffic flow and in-out packets, I should follows the below steps -
- Do I need to Force Standby the Active ?
- Do I need to make Active as Force Offline ?
- Do I need to follow the same upgrade steps like what I did for Standby ?
- Now Active comes up as Active ?
- Do I need to do sync ?
- RaghavendraSY
Altostratus
Yes. You are right but still, suggest you go with offline configuration.
- Open proactive request with the f5 vendor
- Verify console connectivity
- Backup existing configuration
- On activity day, start upgrade process with standby
- Relicense standby device
- Upgrade the device to a new version
- Boot with new volume/version
- Failover the traffic from active to newly upgraded device
- Verify the connectivity and compare pre and post-upgrade configuration
- Do similar steps (5 to 9) for another device
- Sabya_361427
Nimbostratus
I had a doubt on step 8 - Let me drop my queries in very clear way. Please reply question wise.
- Do I need to perform Force Offline before following steps - 5 to 7 ?
- Do I need to do Release Offline before upgrade or post upgrade ?
- Will it come as Standby as it was earlier before the upgrade ?
After I ensure the traffic flow and in-out packets, I should follows the below steps -
- Do I need to Force Standby the Active ?
- Do I need to make Active as Force Offline ?
- Do I need to follow the same upgrade steps like what I did for Standby ?
- Now Active comes up as Active ?
- Do I need to do sync ?
- Anoop
Nimbostratus
Hello Sabya,
Here is the steps to be followed.
Ensure service check date is not earlier than license check date , if it is then perform step 4(optional). Refer https://support.f5.com/csp/article/K7727 for more details
- Take backup from both the device(Qkview and UCS)
- Upload image and hotfix file either via GUI or CLI
- Make the device force offline(Standby unit)
- *****Reactivate license *****
- Install software
- Install hotfix
- Release offline
-
Force to standby and validate below
a) Network map b) Compare configuration c) Test service Once successful proceed with other unit.
- RaghavendraSY
Altostratus
Here are my steps.
Do I need to perform Force Offline before following steps - 5 to 7 ? You can perform at step6 Do I need to do Release Offline before upgrade or post upgrade ? after upgrade and before traffic failover Will it come as Standby as it was earlier before the upgrade? yes After I ensure the traffic flow and in-out packets, I should follow the below steps -
Do I need to Force Standby the Active? always bring an active device to standby state Do I need to make Active as Force Offline? please do only when a device is in standby and traffic is passing through active firewalls Do I need to follow the same upgrade steps like what I did for Standby? yes Now Active comes up as Active? standby because already you did a failover and traffic is passing through another device which you upgraded Do I need to do sync ? yes, before upgrade sync the configurations and take a print screen of network map of both the devices
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com