F5 Logo MyF5
Search
  1. MyF5 Home
  2. Knowledge Centers
  3. BIG-IQ Centralized Management
  4. F5 BIG-IQ Centralized Management: Upgrading a 5.1 Logging Node Cluster to the Latest Version with Minimal Downtime
  5. Completing Post-Upgrade Processes
Manual Chapter : Completing Post-Upgrade Processes

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 5.4.0
Manual Chapter
Table of Contents | << Previous Chapter | Next Chapter >>

Recheck data collection device health

You can use the Summary Status screen to review the overall health and status of the data collection devices you've configured. You can use the data displayed on this screen both before and after an upgrade to verify that your data collection device cluster configuration is as you expect.
  1. At the top of the screen, click System.
  2. At the top of the screen, click System, and then, on the left, click BIG-IQ DATA COLLECTION and select BIG-IQ Data Collection Cluster.
    • Under Summary, you can view information detailing how much data is stored, as well as how the data is stored.
    • Under Configuration, you can access the screens that control DCD cluster performance.
  3. Note the status icon color for the cluster. If it is not green yet, wait until it turns to green before proceeding. When the icon turns green it indicates that the primary BIG-IQ DCD cluster is functioning again.
  4. Analyze the data collection device cluster details listed in the Summary area, and make sure that the values after upgrade match the values from the health check you did before the upgrade. At a minimum, you should confirm that the following values are correct:
    • Data Node Count

Reestablish the HA configuration after upgrading to BIG-IQ version 5.4

After you upgrade both F5® BIG-IQ® Centralized Management systems in a HA configuration, you can re-associate the secondary system with the primary BIG-IQ system.
  1. Log in to primary BIG-IQ system with your administrator user name and password.
  2. At the top of the screen, click System.
  3. On the left, click BIG-IQ HA.
  4. Click the Add Secondary button.
  5. In the IP Address field, type the discovery address you specified on the BIG-IQ system during setup.
    This is the same IP address the peers in a high availability confirmation use to communicate.
  6. In the User name and Password fields, type the administrative user name and password for the system.
  7. In the Root Password field, type the root password for the system.
  8. Click the Add button to add this device to this high availability configuration.

Even though you can log in to the secondary BIG-IQ after the you reestablish the HA configuration, the system continues some database re-indexing processes in the background. For larger configurations, that can take up to an hour. If you perform any searches on objects before it's done re-indexing, BIG-IQ might not return the expected results. During this time, you can use the primary BIG-IQ.

Next, you should verify that both BIG-IQ systems have the same configuration.

Restart snapshot creation

Because of the mixed software version environment that occurs during the upgrade process, if you had configured snapshot schedules in 5.1, you stopped creating snapshots before the upgrade. Now that the upgrade is complete, you need to restart the snapshots to protect your data.
  1. Use SSH to log in to the primary BIG-IQ system for this cluster.
    You must log in as root to perform this procedure.
  2. Retrieve the list of scheduled snapshots using the following command: restcurl cm/shared/esmgmt/es-snapshot-task | grep task-scheduler 
    config # restcurl cm/shared/esmgmt/es-snapshot-task | grep task-scheduler 
"link": "https://localhost/mgmt/shared/task-scheduler/scheduler/0fdf50ec-8a17-3da9-b717-c63637ccc68a"
"link": "https://localhost/mgmt/shared/task-scheduler/scheduler/0af33352-2f33-32b3-85cb-1281bb88c249"
"link": "https://localhost/mgmt/shared/task-scheduler/scheduler/2ad770a8-bdb0-3383-99a9-300846eb0972"
    In the example here, there are 3 snapshots scheduled.
  3. Stop each of the schedules using the following command: restcurl -X PATCH -d '{"status":"ENABLED"}' shared/task-scheduler/scheduler/<SNAPSHOT ID> 
    #restcurl -X PATCH -d '{"status":"ENABLED"
shared/task-scheduler/scheduler/0af33352-2f33-32b3-85cb-1281bb88c249
    After you run the command for each scheduled snapshot, snapshots will again be created following the snapshot schedule.

Upgrade the BIG-IP framework

To properly communicate, BIG-IQ® Centralized Management and managed BIG-IP® devices must be running a compatible version of its framework. If the frameworks are incompatible, BIG-IQ displays a yellow triangle next to the device in the BIG-IP Device inventory.

When you upgrade a BIG-IP device running version 11.5.x to another 11.5.x version, or to an 11.6.x version (for example, from version 11.5.3 to 11.5.4, or from version 11.5.3 to version 11.6.1), you must upgrade the REST framework so BIG-IQ can manage the device.

When you upgrade BIG-IQ from version 5.x to the latest version, you must also upgrade the REST framework for all BIG-IP devices (currently in the BIG-IP Device inventory) running a version prior to 12.0.0.

  1. At the top of the screen, click Devices.
  2. Select the check box next to a device, click the More button, and select Upgrade Framework.
    A popup screen opens.
  3. Into the fields, type the required credentials, and click the Continue button.
    A REST Framework upgrade in progress message displays.
After the framework is updated, you can successfully manage this device.
Repeat these steps for each device.

Re-discover devices and re-import services

After you upgrade F5® BIG-IQ Centralized Management, you must rediscover your managed devices and reimport their services for AFM, ASM, DNS, and LTM so you can start managing those devices with the new features introduced in this release.
  1. At the top of the screen, click Devices.
  2. Select the check box next to the devices you want to rediscover and reimport services for.
  3. Click the More button and select Re-discover and Re-import.
  4. In the Name and Description fields, type a name and an optional description to identify this task.
  5. For the Conflict Resolution Policy setting, select an option for how you want to handle any differences found between the configuration on BIG-IQ and the BIG-IP device during the re-discover and re-import task.
    • Use BIG-IQ to use the configuration setting stored on BIG-IQ if any differences are found.
    • Use BIG-IP to override the configuration settings stored on BIG-IQ with the settings from the BIG-IP device.
    Important:

    Some new features are introduced with each BIG-IQ release so it's a good idea to use the BIG-IP device's configuration after you upgrade BIG-IQ. This ensures you don't inadvertently overwrite a configuration that wasn't previously supported. BIG-IP devices are re-imported in the order listed, from top to bottom. You can use the arrow keys to change the processing order.

    When you select Use BIG-IP to resolve conflicts, the BIG-IP device used to resolve those conflicts should appear last in the re-import list. If two or more BIG-IP devices contain the same object with different values, only the value in the last imported BIG-IP is used to resolve the conflict for all the BIG-IP devices.

  6. If you want to save a snapshot of the BIG-IP device's configuration before importing their services, select the Create a snapshot of the current configuration before importing check box.
  7. Click the Create button at the bottom of the screen.
Table of Contents | << Previous Chapter | Next Chapter >>
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5 Networks, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information