Applies To:

Show Versions Show Versions

Manual Chapter: Upgrade the Logging Nodes in Your Cluster with Minimal Downtime
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

What you need to do before you upgrade the logging node from version 5.1 to 5.3

Before upgrading the F5® BIG-IQ® Centralized Management logging node, perform these tasks.

Tasks Additional information
Re-activate the BIG-IQ system license. You must do this for each logging node in the cluster. For specific instructions about how to reactivate a license, refer to the F5® BIG-IQ® Central Management: Licensing and Initial Setup guide.
Decide which disk volume you want to install the upgrade on. You must have at least two volumes to upgrade BIG-IQ. If the machine you are upgrading does not have two volumes, you must create one using a sequence of tmsh commands. The upgrade task provides options for either case.

Upgrade the logging nodes to version 5.3

After you prepare the logging node cluster for upgrade, use these procedures to upgrade the logging nodes in your cluster. Perform the following tasks for each logging node in the cluster.

  1. Upload the BIG-IQ version 5.3 software image.
  2. From the BIG-IP device(s), take the logging node out of the alert-traffic flow.
  3. Deactivate data collection services.
  4. Upgrade the logging node to version 5.3.
  5. Confirm that the logging node is back in service
  6. Reactivate data collection services.
  7. From the BIG-IP device(s), bring the logging node back online.
Important: To successfully upgrade your logging node cluster with minimal downtime, it is critical that you perform this sequence of tasks to each logging node in the cluster serially, not in parallel.

Upload the BIG-IQ version 5.3 software image

Before you can upload the software image to your logging node, you must have first downloaded it from the F5 Downloads site.

You upload the BIG-IQ® version 5.3 software image to your logging node to make it available for this upgrade.

  1. At the top of the screen, click System Management.
  2. At the top of the screen, click Inventory.
  3. Click the Upload Image button.
  4. Click the Choose File button and go to the location to which you downloaded the image, and click the Open button to upload it to BIG-IQ.
  5. Click the Upload button.
    The screen refreshes to display the progress of the upload.
When the image is done uploading, it shows in the Available Images list.

Stop sending alerts to the logging node

To upgrade your logging node cluster with minimum downtime, before you begin the process of updating your logging nodes, you must complete the upgrade preparation described in Prepare for Logging Node Upgrade With Minimal Downtime.

This is the first task you must perform on each logging node in the cluster to make sure that you do not lose any data during the upgrade. When you take the logging node that you are about to upgrade offline, the BIG-IP® device routes the data to another logging node in the cluster.

Log in to each BIG-IP device that sends data to your logging node cluster, and revise the configuration so that the data it sends to the cluster does not include the particular logging node that you are preparing to upgrade.
Note: The process for stopping data collection for one logging node in the cluster depends on the kind of data that you collect.
Option Description
If you collect FPS alerts or IPsec events:
  1. On the BIG-IP device, select Local Traffic > Pools > Pool List .
  2. Select the pool that sends alerts and events to the logging node.
  3. Click Members.
  4. Select the pool member that sends alerts to the target logging node, and disable it.
If you collect ASM® events:
  1. On the BIG-IP device, select Local Traffic > Pools > Pool List .
  2. Select the pool that contains the members that send events to the logging node.
  3. Click Members.
  4. Select the pool member that sends alerts to the target logging node, and disable it.
If you collect APM® events: You don't need to disable the logging node from the BIG-IP device. All you need to do is deactivate the service.

Deactivate data collection services for version 5.1

You must perform this task for each logging node in the cluster to make sure that you minimize data loss during the upgrade. When you take the logging node that you are about to upgrade off line, the BIG-IP® device routes the data to another logging node in the cluster.

  1. Log in to the BIG-IQ primary to deactivate services.
  2. At the top of the screen, click System Management.
  3. At the top of the screen, click Inventory.
  4. On the left, expand BIG-IQ LOGGING and then select Logging Configuration.
    The Logging Configuration screen opens to display the current state of the logging node cluster defined for this device.
  5. Select the device name of the first logging node in your cluster.
    The Properties screen for the selected logging node opens.
  6. On the left, select Services.
  7. For each active service, click Deactivate.
    Important: Before you exit this screen, make a note of the Listener Address for this logging node. You will need it later in the upgrade process.
  8. Click Cancel.
    The screen closes and BIG-IQ deactivates your services.

Upgrade the logging nodes from version 5.1 to 5.3

Note: If the machine you are upgrading does not have two volumes, you must create one using a sequence of tmsh commands. The following steps provide options for either case.
Before upgrading the logging node, you must have downloaded the BIG-IQ® version 5.3 .iso image from the F5 downloads site.

The upgrade process installs the new version of the software on each logging node in your cluster.

  1. Log in to the logging node with your admin user name and password.
  2. At the top of the screen, click System Management.
  3. At the top of the screen, click Inventory.
  4. On the left, click BIG-IQ DEVICES > BIG-IQ HA .
  5. On the left, click Software Version.
  6. Click the Update button.
  7. From the Software Image list, select the image you want to install.
  8. From the Target Volume list, select the volume you want to install the image on.
    Note: If the Target Volume list is empty, the machine you are upgrading does not have a second volume available for you to install the upgrade. You must create one to proceed.
    • If you selected a target volume, complete the remaining steps to finish the upgrade.
    • If you do not have a second volume, use the following sequence of tmsh comments to install the upgrade for this machine:
      • Use SSH to log in to the machine you want to upgrade. You must log in as root to perform this procedure.
      • Navigate to the folder where you install software using the command: cd /shared/images
      • Install the upgrade to a new volume using one of the following commands:
        • If you are upgrading a virtual machine: tmsh install sys software image <full name of the iso file> volume hd1.2 create-volume reboot
        • If you are upgrading a BIG-IQ 7000 series platform: tmsh install sys software image <full name of the iso file> volume md1.2 create-volume reboot
      • While the system installs the upgrade to the new volume, you can check on the status of the upgrade using the command: tmsh show sys soft.
      • When the upgrade finishes installing, the machine reboots. Proceed to the next to the last (login) step in this task.
  9. To prompt the logging node to reboot into the new software installation volume, select the Reboot into Target Volume check box.
  10. Click the Apply button.
    A popup screen opens, prompting you to confirm the installation.
  11. Click the Continue button.
  12. Wait while the logging node loads the new software and reboots.
    Depending on your configuration and the number of devices you are managing, this could take up to 15 minutes. During this time, it is important that you do not interrupt the installation process by restarting services or the server.
  13. Log back in to the logging node to confirm that the upgrade succeeded.
  14. Complete the setup wizard.
    Note: To complete the setup task, you must supply a master key pass phrase that all devices in the logging node cluster must share. Make note of the phrase you use. Each logging node, as well as the primary and secondary BIG-IQ systems must use this phrase before they can join the cluster.
  15. If needed, extend the /var partition.
    The default size of the /var file system in a newly installed node is 10 GB. This volume size might be insufficient to store your data. You can see how to extend this file system to a larger size in knowledge article K16103. refer to: K16103: Extending disk space on BIG-IQ Virtual Edition at support.f5.com/csp/article/K16103. Because upgrading a node requires at least two volumes, you must ensure that both volumes can have their /var file system extended to the same size, or upgrades might fail.
Important: In the unlikely event that you are unable to log in to a BIG-IQ® 7000 series platform after you upgraded it, refer to SOL40338232: The BIG-IQ system interface might be inaccessible after the BIG-IQ system is upgraded from BIG-IQ Centralized Management version to 5.2.0 at support.f5.com/kb/en-us/solutions/public/k/40/sol40338232.html for more information.

Confirm that the upgraded logging node is back in service

After you upgrade a logging node as part of the minimum downtime workflow, you need to confirm that the logging node is back in service before you proceed with upgrading the next logging node in the cluster.

Note: In the 5.3 user interface, logging nodes are referred to as a data collection devices (DCDs).
  1. Log in to the BIG-IQ® system primary with your admin user name and password.
  2. At the top of the screen, click System Management.
  3. On the left, expand BIG-IQ LOGGING and then select Logging Nodes.
  4. Note the status icon color for the DCD that you just upgraded. 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 system and the DCD are communicating.
  5. Use SSH to log in to the DCD you just upgraded.
    You must log in as root to perform this procedure.
    Important: It is critical that you log in to the correct device. Log in to the DCD, not the primary BIG-IQ.
  6. Determine whether the DCD cluster service restarted, using the following command:
    bigstart status elasticsearch
    In this example, the DCD cluster has been up and running for less than an hour.
    elasticsearch run (pid 5110) .5 hours
    
  7. Determine whether this DCD has rejoined the DCD cluster, using the following command:
    curl localhost:9200/_cat/nodes?v
    In the following example, the recently upgraded DCD (10.11.0.96) has rejoined the cluster (three other DCDs, the primary BIG-IQ, and the secondary BIG-IQ).
    curl localhost:9200/_cat/nodes?v
    host          ip            heap.percent ram.percent load node.role master name                                                                                                                                                              
    10.11.0.96    10.11.0.96               2          63 0.01 d         m      d6211
    10.11.0.97    10.11.0.97               2          63 0.01 d         m      d6212
    10.11.0.98    10.11.0.98               2          63 0.01 d         m      d6213
    10.11.0.99    10.11.0.99               2          63 0.01 d         m      d6214
    10.144.73.126 10.144.73.126           22          45 0.04 -         *      09020 b0c-7021-458f-89f4-5e89faf64670
    10.144.73.127 10.144.73.127           22          45 0.05 -         m      09020 c0c-2235-234a-54b2-2f45fab3233b
    
  8. If the DCD did not rejoin the cluster, restart the cluster service using this command:
    bigstart restart elasticsearch
    The cluster service restarts, and the DCD rejoins the cluster. Repeat step 7 to confirm.
  9. Log in to the BIG-IQ system primary again with your admin user name and password.
  10. At the top of the screen, click System Management.
  11. On the left, expand BIG-IQ LOGGING and then select Logging Nodes.
  12. Click Settings.
    The Properties screen for the logging node cluster opens.
  13. Note the Data Cluster Status icon color. If it is not green yet, wait until it turns to green before proceeding.
    When the icon turns green, it indicates that data is again distributed to all members of the DCD cluster.
The DCD cluster is now fully restored to service.
Now that the cluster is functioning again, you need the upgraded DCD to start collection data again.

Reactivate data collection services from 5.1 upgrade

After you upgrade a data collection device (DCD) and it is again a fully functioning member of the DCD cluster, you need it to start collecting data again.

  1. Log in to the BIG-IQ® system primary with your admin user name and password.
  2. At the top of the screen, click System Management.
  3. At the top of the screen, click Inventory.
  4. On the left, expand BIG-IQ LOGGING and then select Logging Nodes.
  5. On the left, expand BIG-IQ DATA COLLECTION and then select BIG-IQ Data Collection Devices.
    The BIG-IQ Data Collection Devices screen opens to list the data collection devices in the cluster.
  6. Click the device name of the DCD you just upgraded.
    The Properties screen for the selected DCD opens.
  7. On the left, click Services.
  8. For each service that you deactivated previously, click Activate.
    Important: Use the Listener Address that you noted when you deactivated services for this DCD.
  9. Click Cancel.
    The screen closes and BIG-IQ activates your services.

Bring the logging node back online

After you upgrade a logging node to a data collection device (DCD), and reactivate data collection services, you need to start sending data to the DCD again.

Log in to each BIG-IP® device that sends data to your logging node cluster, and revise the configuration so that the data it sends to the cluster includes the logging node you just upgraded.
Note: The process for starting data collection for one logging node in the cluster depends on the kind of data you collect.
Option Description
If you collect FPS alerts:
  1. On the BIG-IP device, select Local Traffic > Pools > Pool List > .
  2. Select the pool that sends alerts and events to the logging node.
  3. Click Members.
  4. Select the pool member that sends alerts to the target logging node, and enable it.
If you collect ASM® events:
  1. On the BIG-IP device, select Local Traffic > Pools > Pool List .
  2. Select the pool that contains the members that send events to the logging node.
  3. Click Members.
  4. Select the pool member that sends alerts to the target logging node, and enable it.
If you collect APM® events: You don't need to enable the logging node from the BIG-IP device. All you need to do is activate the service.
Now that the upgraded logging node has rejoined the cluster, the services are reactivated, and the BIG-IP devices are sending data again, you can upgrade the next logging node in the cluster.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)