F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Doran_Lum_13484's avatar
Doran_Lum_13484
Icon for Nimbostratus rankNimbostratus
Oct 02, 2013

Upgrading of BIG-IP 3900 systems

Hi all, we would like to upgrade the software of both our new BIG-IP 3900 Series for the 1st time. We have a concern if the service would be working after the update.   Are we able to update the s...
askf5
deployment
f5
JRahm's avatar
JRahm
Icon for Admin rankAdmin
Oct 02, 2013

Operationally, I am a fan of this process:

 

  1. Sync both systems, create archives, and ftp them offbox somewhere, then freeze all configuration changes for the duration of the upgrade window
  2. Take snapshots of current system and application performance and availability
  3. Upgrade the standby unit and fail over to it
  4. Take new snapshots of current system and application performance and availability and compare to the ones taken before the upgrade, failing back if there are issues that can't immediately be addressed. If all is well, then proceed.
  5. Upgrade the now standby unit and fail back over to it
  6. Take another set of snapshots and compare to previous to make sure both units in the pair took the upgrade well.
  7. Watch for anomalies over the course of several days, then unfreeze the configuration changes.

The benefit of a config freeze during the upgrade process is it is super simple to fall back, just boot back into the previous version bootslot on the standby and then fail over.