Applies To:

Show Versions Show Versions

Manual Chapter: Installing a hotfix
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Installing a hotfix

About installing a hotfix

We provide an F5® iWorkflow™ hotfix to meet a need or resolve an issue unique to your environment. F5 recommends that you run iWorkflow in a cluster. When applying a hotfix to an iWorkflow cluster, you must first evict the peers from the cluster (breaking the cluster) and then apply the hotfix to each instance before recreating the cluster.

To install a hotfix, make sure that you have:

  • Adequate disk space available to complete the installation.
  • Administrator rights on the iWorkflow system.
  • A recent user configuration set (UCS) backup of the iWorkflow system copied to a remote secure server for storage.
  • An iWorkflow release ISO file copied to the /shared/images directory.
  • A target iWorkflow base ISO available under the /shared/images directory.

Breaking a cluster

Before you start, make sure that you are running an iWorkflow™ cluster.
You break the cluster in order for removed peers to return to a default state.
Important: If you are running a standalone system (your environment contains a single iWorkflow server), skip all the steps for Breaking a cluster. Proceed to Installing a hotfix on a standalone system.
Note: When you break a cluster, the data stored on the peer that is evicted from the cluster will be lost.
  1. Log in to the iWorkflow administrative user interface with your administrator user name and password.
  2. At the top of the screen, click System settings.
  3. From the iWorkflow Cluster panel, double-click the peer you want to remove.
  4. In the Properties panel, click Remove to remove the peer you want to evict from the cluster ("break" the cluster) .
  5. Repeat this task for each peer you want to evict from (break) the cluster.
    Note: From the time you remove the first peer, until the leader is a standalone instance, iWorkflow will report the cluster size as unsupported.

Installing a hotfix on a standalone system

Before you start, make sure you are running a standalone system. That is, your environment is running a single iWorkflow™ server.
Important: If you are installing a hotfix on an iWorkflow cluster, you must first break the cluster before installing the hotfix on each iWorkflow instance. If you have an iWorkflow cluster, first perform the Breaking the a cluster procedure before you start this procedure.
You can install a hotfix to meet a need or resolve an issue unique to your environment.
Note: While you are updating the iWorkflow server, it is not available for administrative access. You cannot make changes, updates, or additions to any of the managed BIG-IP® systems. However, traffic on BIG-IP systems is not impacted.
  1. Run the command tmsh to access the tmsh utility.
  2. Run the command show /sys software to check the status of the currently installed iWorkflow software.

    The output displays something similar to this example.

                               
    
    ------------------------------------------------------------------------
    Sys::Software Status      
    Volume     Product            Version      Build     Active  Status    
                                                                
    ------------------------------------------------------------------------
    HD1.1      iWorkflow          2.0.0        0.0.9631  yes      complete   
    HD1.2           none          none         none      no       complete
    
    
                            
    
  3. Run the command install /sys software hotfix <iworkflow-hotfix.iso> volume <inactive volume> to install an iWorkflow hotfix onto an existing inactive volume.
    <iworkflow-hotfix.iso> is the name of the hotfix file.

    <inactive volume> is the name of the inactive volume.

    Example: install /sys software hotfix Hotfix-iWorkflow-bigiq-mgmt-2.0.0.9999.9999-ENG.iso volume HD1.2.
  4. Optional: Run the command install /sys software image <iworkflow-hotfix.iso> create-volume volume <new volume> reboot to automatically reboot after creating a new volume and installing iWorkflow into a new location.
    <iworkflow-hotfix.iso> is the name of the hotfix file. For example, install sys software hotfix Hotfix-iWorkflow-bigiq-mgmt-2.0.0.9999.9999-ENG.iso create-volume volume HD1.3.
  5. Run the command quit to exit the tmsh utility.
    Note: You can monitor the installation process by running the command: watch tmsh show /sys software. By default, the watch command automatically refreshes every two seconds. If tmsh appears to stall and a waiting for product image message displays, confirm that you have the base ISO image available in the /shared/images directory.

    The command output displays something similar to this example.

                               
    
    ------------------------------------------------------------------------
    Sys::Software Status      
    Volume     Product      Version  Build     Active                 Status    
                                                                
    ------------------------------------------------------------------------
    HD1.1      iWorkflow    2.0.0    0.0.9631  yes                   complete   
    HD1.2      iWorkflow    2.0.1    0.0.9631  no       installing  0.000 pct
    
    
                            
    

Recreating a cluster

Before you start, make sure that the peers joining the cluster are clean builds.
You can recreate a cluster from any iWorkflow™ instance.
Important: The cluster creation process does not support importing existing configurations from an existing iWorkflow system.
  1. Log in to the iWorkflow administrative user interface with your administrator user name and password.
  2. At the top of the screen, click System settings.
  3. From the iWorkflow Cluster panel, in the iWorkflow Cluster header, click the plus (+) icon.
  4. In the New iWorkflow Cluster Member panel, type the IP address, Admin Username, and Password.
  5. Click OK to acknowledge the data on the peer will be overwritten warning.
  6. Repeat this procedure for the third iWorkflow member 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)