Applies To:Show Versions
BIG-IQ Centralized Management
What you need to do before you upgrade to BIG-IQ version 5.0
We want your upgrade to go smoothly, so it's important to note a couple things. First, before you start the upgrade process, there are a few tasks you need to do. Once you finish those tasks and are ready to start the upgrade, be sure to follow the process in the order specified.
Required tasks you must complete before you upgrade to BIG-IQ version 5.0
Before you start the process to upgrade the BIG-IQ® system, you must complete each of the following tasks.
|Reactivate the BIG-IQ license on both the active and standby systems.||For specific instructions about how to reactivate a license, refer to the BIG-IQ® Central Management: Licensing and Initial Setup guide.|
|Create a UCS backup of the BIG-IQ system's current configuration and send it to a remote server for storage.||
You can restore this saved backup only to BIG-IQ running version 4.5 or 4.6. You cannot restore a backup file for BIG-IQ version 4.5 or 4.6 onto BIG-IQ running version 5.0.
For specific instructions about how to create a UCS backup, refer to the BIG-IQ® Central Management: Licensing and Initial Setup guide.
|Decide which disk volume you want to install the upgrade on.||If you are running BIG-IQ Virtual Edition and you don't have at least two volumes, follow these instructions: SOL17406: Using the tmsh utility to create a new software volume for installing a new image or hotfix on the BIG-IQ system at https://support.f5.com/kb/en-us/solutions/public/17000/400/sol17406.html.|
|Upgrade all your managed BIG-IP devices to a version compatible with BIG-IQ version 5.0.||See SOL14592: Compatibility between BIG-IQ and BIG-IP releases at https://support.f5.com/kb/en-us/solutions/public/14000/500/sol14592.html for details about what BIG-IP versions are compatible with BIG-IQ version 5.0.|
|To make sure you've deployed all pending changes you want to keep after the
upgrade, for each functional area:
||For more information about this process, review the documentation associated with the functionality you're deploying changes for.|