--- title: "Performing upgrades using CMS CLI" slug: "performing-upgrades-using-cms-cli" updated: 2026-09-23T11:45:33Z published: 2026-09-23T11:45:33Z canonical: "docs.trellix.com/performing-upgrades-using-cms-cli" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Performing upgrades using CMS CLI The upgrade procedure depends on whether you are upgrading the system image, guest images, or both, and whether you are upgrading the cluster or an individual node. > [!WARNING] > Caution > > Do not upgrade a single node that is currently part of a cluster. Upgrade the entire cluster from the Central Management appliance instead. - [Upgrading the system image and Guest Images using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrading-the-system-image-and-guest-images-using-the-cli) - [Upgrading the system image using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrading-the-system-image-using-the-cli) - [Downloading and installing Guest Images using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#downloading-and-installing-guest-images-using-the-cli) - [Downloading Guest Images using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#downloading-guest-images-using-the-cli) - [Installing Guest Images using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#installing-guest-images-using-the-cli) - [Suspending, resuming, or cancelling an upgrade](/network-and-platform/docs/performing-upgrades-using-cms-cli#suspending-resuming-or-cancelling-an-upgrade) - [Deleting a Guest-Images download](/network-and-platform/docs/performing-upgrades-using-cms-cli#deleting-a-guestimages-download) - [Monitoring upgrade status using the CLI](/network-and-platform/docs/performing-upgrades-using-cms-cli#monitoring-upgrade-status-using-the-cli) #### Upgrading the system image and Guest Images using the CLI Use the commands in this section to upgrade both the system image and guest images on an IVX cluster or node using the Central Management CLI. ###### Upgrading a cluster The following procedure shows how to upgrade both the system image and guest images on all nodes in a cluster. ###### To upgrade both the system image and guest images on a cluster: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. Upgrade the cluster: ```plaintext cm-hostname (config) # fenet update cluster ``` where <cluster name> is the name of the cluster. 4. Monitor the status: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### To upgrade to a specific version of the system and upgrade guest images on a cluster: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. Upgrade the cluster: ```plaintext cm-hostname (config) # fenet update cluster version ``` 4. Monitor the status: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### Upgrading a node The following procedure shows how to upgrade both the system image and guest images on a specific node. ###### To upgrade both the system image and guest images on a node: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. Upgrade the node: ```plaintext cm-hostname (config) # fenet update appliance ``` where <`appliance name>` is the name of the Virtual Execution appliance. 4. Monitor the status: ```plaintext cm-hostname (config) # show fenet update status appliance ``` ###### Example The following example shows a full upgrade on Cluster-Acme. In the example, the system image upgrade is complete on both nodes, and guest images are being downloaded to vx-2. The guest images download task is Task (07/10). This task will start on vx-1 after it is completed on vx-2. ```plaintext cm-1 (config) # fenet update cluster Cluster-Acme cluster update for Cluster-Acme: success, update started    Run 'show fenet update status cluster Cluster-Acme' for status cm-1 (config) # show fenet update status cluster Cluster-Acme Cluster Update Status:    Cluster                 : Cluster-Acme    Status                  : in-progress    Current operation       : image-gi-update    Current task            : gi-download    Percent done            : 35.07 %    Start time              : 2019/07/15 20:23:23.480    End time                : ********    Node: vx-2        Status              : in-progress        Percent done        : 56.14 %        Task (01/10)        : image-check            Status          : complete            Percent done    : 100.00 %        Task (02/10)        : gi-check            Status          : complete            Percent done    : 100.00 %        Task (03/10)        : image-fetch            Status          : complete            Percent         : 100.00 %        Task (04/10)        : image-install            Status          : complete            Percent done    : 100.00 %        Task (05/10)        : image-rename            Status          : complete            Percent done    : 100.00 %        Task (06/10)        : image-boot-next            Status          : complete            Percent done    : 100.00 %        Task (07/10)        : gi-download            Status          : in-progress            Percent done    : 56.19 %    Node                    : vx-1        Status              : in-progress        Percent done        : 14.00 %        Task (01/10)        : image-check            Status          : complete            Percent done    : 100.00 %            Task (02/10)    : gi-check        Status              : complete            Percent done    : 100.00 %            Task (03/10)    : image-fetch        Status              : complete            Percent done    : 100.00 %            Task (04/10)    : image-install        Status              : complete            Percent done    : 100.00 %            Task (05/10)    : image-rename        Status              : complete            Percent done    : 100.00 %            Task (06/10)    : image-boot-next        Status              : complete            Percent done    : 100.00 % ``` #### Upgrading the system image using the CLI Use the commands in this section to upgrade the system image on an IVX cluster or an individual node using the Central Management CLI. > [!NOTE] > Note > > Use the show fenet metadata status command to see a list of the available versions of the system image. ###### Upgrading the system image on a cluster The following procedure shows how to upgrade the Intelligent Virtual Execution - Server system image on all nodes in a cluster. ###### Install the system image: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To upgrade to the latest version of the system image and then reboot the system: ```plaintext cm-hostname (config) # fenet update cluster system-image ``` or ```plaintext cm-hostname (config) # fenet update cluster system-image reboot ``` where <`cluster name>` is the name of the cluster. 4. To upgrade to the latest version of the system image without rebooting the system: ```plaintext cm-hostname (config) # fenet update cluster system-image no-reboot ``` 5. To upgrade to a specific version of the system image: ```plaintext cm-hostname (config) # fenet update cluster system-image version ``` where <`cluster name>` is the name of the cluster, and `<version>` is the system image version number. 6. Check the progress: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### Upgrading the system image on a node The following procedure shows how to upgrade the Virtual Execution system image on a specific node. ###### Install the system image: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To install the latest version of the system image and then reboot the system: ```plaintext cm-hostname (config) # fenet update appliance system image ``` or ```plaintext cm-hostname (config) # fenet update appliance system image reboot ``` where `<appliance name>` is the name of the Intelligent Virtual Execution - Server appliance. 4. To install the latest version of the system image without rebooting the system: ```plaintext cm-hostname (config) # fenet update appliance system- image no-reboot ``` 5. To install a specific version of the system image: ```plaintext cm-hostname (config) # fenet update appliance system- image version ``` or ```plaintext where is the name of the Virtual Execution appliance, and is the system image version number. ``` 6. To upgrade to a specific version of the system image and upgrade the guest images: ```plaintext cm-hostname (config) # fenet update appliance version ``` 7. Check the progress: ```plaintext cm-hostname (config) # show fenet update status appliance ``` ###### Example The following example shows a system image upgrade on Cluster-Acme. In the example, the image-check and image-fetch tasks are complete on both nodes, and the image-install task is in progress on vx-2. ```plaintext cm-1 (config) # fenet update cluster Cluster-Acme system-image cluster update for Cluster-Acme: update started: success    Run 'show fenet update status cluster Cluster-Acme' for status cm-1 (config) # show fenet update status cluster Cluster-Acme Cluster Update Status:    Cluster                     : Cluster-Acme        Status                  : in-progress        Current operation       : image-update        Current task            : image-install        Percent done            : 19.28 %        Start time              : 2019/07/18 18:58:33.168        End time                : ********        Node: vx-2            Status              : in-progress            Percent done        : 23.56 %            Task (01/07)        : image-check                Status          : complete                Percent done    : 100.00 %            Task (02/07)        : image-fetch                Status          : complete                Percent         : 100.00 %            Task (03/07)        : image-install                Status          : in-progress                Percent done    : 42.82 %        Node: vx-1            Status              : in-progress            Percent done        : 15.00 %            Task (01/07)        : image-check                Status          : complete                Percent done    : 100.00 %            Task (02/07)        : image-fetch            Status              : complete            Percent done        : 100.00 % ``` #### Downloading and installing Guest Images using the CLI Use the commands in this section to upgrade guest images on an IVX cluster or an individual node using the Central Management CLI. > [!NOTE] > Note > > You can cancel, suspend, and resume a guest-images download. For details, see [Suspending, resuming, or cancelling an upgrade](/network-and-platform/docs/performing-upgrades-using-cms-cli#suspending-resuming-or-cancelling-an-upgrade). ###### Downloading and installing Guest Images on a cluster The following procedure shows how to download and install guest images on all nodes in a cluster. ###### Download and install guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 2. Start the upgrade: ```plaintext cm-hostname (config) # fenet update cluster guest-image ``` 3. Check the progress: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### Downloading and installing Guest Images on a node The following procedure shows how to download and install guest images on a specific node. ###### Download and install guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 2. Start the upgrade: ```plaintext cm-hostname (config) # fenet update appliance guest- image ``` 3. Check the progress: ```plaintext cm-hostname (config) # show fenet update status appliance ``` ###### Example The following example downloads and installs guest images on the vx-1 node. ```plaintext cm-1 (config) # fenet update appliance vx-1 guest-image appliance update for vx-1 success, update started    Run 'show fenet update status appliance vx-1' for status cm-1 (config) # show fenet update status appliance vx-1 Appliance Update Status:    Appliance                       : vx-1        Status                      : complete        Current operation           : gi-update        Current task                : gi-install        Percent done                : 100.00 %        Start time                  : 2019/07/07 21:18:35.455        End time                    : 2019/07/07 22:18:49.335        Node: vx-1            Status                  : complete            Percent done            : 100.00 %            Task (01/03)            : gi-check                Status              : complete                Percent done        : 100.00 %            Task (02/03)            : gi-download                Status              : complete                Percent done        : 100.00 %            Task (03/03)            : gi-install                Status              : complete                Percent done        : 100.00 % ``` #### Downloading Guest Images using the CLI Use the commands in this section to download guest images to an IVX cluster or an individual node using the Central Management CLI. > [!NOTE] > Note > > You can cancel, suspend, and resume a guest-images download. For details, see [Suspending, resuming, or cancelling an upgrade](/network-and-platform/docs/performing-upgrades-using-cms-cli#suspending-resuming-or-cancelling-an-upgrade). ###### Downloading Guest Images on a cluster The following procedure shows how to download guest images to all nodes in a cluster. ###### Download the guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 2. Start the upgrade: ```plaintext cm-hostname (config) # fenet update cluster guest-image download ``` 3. Check the progress: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### Downloading Guest Images to a node The following procedure describes how to download guest images to a specific node. ###### Download the guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 2. Download the guest images: ```plaintext cm-hostname (config) # fenet update appliance guest- image download ``` 3. Check the progress: ```plaintext cm-hostname (config) # show fenet update status appliance ``` ###### Example The following example downloads guest images to all nodes of Cluster-Acme. ```plaintext cm-1 (config) # fenet update cluster Cluster-Acme guest-image download cluster update for Cluster-Acme success, update started Run 'show fenet update status cluster Cluster-Acme' for status ``` #### Installing Guest Images using the CLI Use the commands in this section to install downloaded guest images on an IVX cluster or an individual node using the Central Management CLI. ###### Installing Guest Images on a cluster The following procedure shows how to install guest images on all nodes in a cluster. ###### Install guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname # configure terminal ``` 2. Ensure that guest images were downloaded: ```plaintext cm-hostname (config) # show fenet update status cluster ``` 3. Install the guest images: ```plaintext cm-hostname (config) # fenet update cluster guest-image install ``` 4. Check the progress: ```plaintext cm-hostname (config) # show fenet update status cluster ``` ###### Installing Guest Images on a node The following procedure shows how to install guest images on a specific node. ###### Install guest images: 1. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 2. Ensure that guest images were downloaded: ```plaintext cm-hostname (config) # show fenet update status appliance ``` 3. Install the guest images: ```plaintext cm-hostname (config) # fenet update appliance guest- image install ``` 4. Check the progress: ```plaintext cm-hostname (config) # show fenet update status appliance ``` ###### Example The following example installs downloaded guest images on the vx-2 node. ```plaintext cm-1 (config) # fenet update appliance vx-2 guest-image install appliance update for vx-2 success, update started    Run 'show fenet update status appliance vx-2' for status ``` #### Suspending, resuming, or cancelling an upgrade This section describes operations you can perform during upgrades. ###### Suspending an upgrade The following procedure shows how to suspend an upgrade on a cluster or node. ###### To suspend an upgrade: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To suspend the upgrade on a cluster: ```plaintext cm-hostname (config) # fenet update cluster suspend ``` 4. To suspend the upgrade on a node: ```plaintext cm-hostname (config) # fenet update appliance suspend ``` ###### Resuming a suspended upgrade The following procedure shows how to resume an upgrade that was suspended. ###### To resume a upgrade: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To resume an upgrade on cluster: ```plaintext cm-hostname (config) # fenet update cluster resume ``` 4. To resume an upgrade on a node: ```plaintext cm-hostname (config) # fenet update appliance resume ``` ###### To resume a guest-images upgrade: 1. To resume a guest-images upgrade on a cluster: ```plaintext cm-hostname (config) # fenet update cluster guest-image resume ``` 2. To resume a guest-images upgrade on a node: ```plaintext cm-hostname (config) # fenet update appliance guest- image resume ``` ###### Canceling an upgrade The following procedure shows how to cancel an upgrade operation. ###### To cancel an upgrade: 1. Log into the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To cancel an upgrade on a cluster: ```plaintext cm-hostname (config) # fenet update cluster cancel ``` 4. To cancel an upgrade on a node: ```plaintext cm-hostname (config) # fenet update appliance cancel ``` ###### To cancel a guest-images upgrade: 1. To cancel a guest-images upgrade on a cluster: ```plaintext cm-hostname (config) # fenet update cluster guest-image cancel ``` 2. To cancel a guest-images upgrade on a node: ```plaintext cm-hostname (config) # fenet update appliance guest- image cancel ``` ###### Example The following example suspends the upgrade on the vx-2 node and then resumes it. In this example, the guest-images download operation was in progress. ```plaintext cm-1 (config) # fenet update appliance vx-2 suspend appliance suspend for vx-2: success, operation initiated    Run 'show fenet update status appliance vx-2' for status cm-1 (config) # show fenet update status appliance vx-2 Appliance Update Status:    Appliance                       : vx-2        Status                      : suspend        Current operation           : gi-download        Current task                : gi-download        Percent done                : 18.66 %        Start time                  : 2019/07/15 22:44:52.071        End time                    : ********        Node: vx-2            Status                  : in-progress            Percent done            : 18.66 %            Task (01/02)            : gi-check                Status              : complete                Percent done        : 100 %            Task (02/02)            : gi-download                Status              : in-progress                Percent done        : 14.38 % cm-1 (config) # fenet update appliance vx-2 resume appliance resume for vx-2: success, operation initiated    Run 'show fenet update status appliance vx-2' for status cm-1 (config) # show fenet update status appliance vx-2 Appliance Update Status:    Appliance: vx-2        Status                      : in-progress        Current operation           : gi-download        Current task                : gi-download        Percent done                : 19.58 %        Start time                  : 2019/07/15 22:44:52.071        End time                    : ********        Node: vx-2            Status                  : in-progress            Percent done            : 19.58 %            Task (01/02)            : gi-check                Status              : complete                Percent done        : 100 %            Task (02/02)            : gi-download                Status              : in-progress                Percent done        : 15.35 % ``` #### Deleting a Guest-Images download Use the commands in this section to delete downloaded guest images. For example, if an installation fails due to a bad download, you can delete the guest images to clean up the partial data. ###### To delete guest images: 1. Log in to the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable ``` 3. To delete guest images from all nodes in a cluster: ```plaintext cm-hostname (config) # fenet update cluster guest-image delete ``` 4. To delete guest images from a node: ```plaintext cm-hostname (config) # fenet update appliance guest- image delete ``` ###### Example The following example deletes the guest images from Cluster-Acme. ```plaintext cm-hostname (config) # fenet update cluster Cluster-Acme guest-image delete cluster update for Cluster-Acme: update started: success    Run 'show fenet update status cluster Cluster-Acme' for status The following example deletes the guest images from Cluster-mssp_01. cm-hostname (config) # fenet update cluster Cluster-mssp_01 guest-image delete cluster update for Cluster-mssp_01: update started: success    Run 'show fenet update status cluster Cluster-mssp_01' for status ``` #### Monitoring upgrade status using the CLI Use the commands in this section to monitor the status of an upgrade. ###### Monitoring cluster upgrades The following procedure shows how to monitor the status of a cluster upgrade. ###### To monitor a cluster upgrade: 1. Log in to the Central Management CLI. 2. To view standard status information: ```plaintext cm-hostname > show fenet update status cluster ``` where <`cluster name`> is the name of the cluster. 3. To view brief status information: ```plaintext cm-hostname > show fenet update status cluster brief ``` 4. To view detailed status information: ```plaintext cm-hostname > show fenet update status cluster detail ``` ###### Monitoring node upgrades The following procedure shows how to monitor the status of a node upgrade. ###### To monitor a node upgrade: 1. Log in to the Central Management CLI. 2. To view standard status information: ```plaintext cm-hostname > show fenet update status appliance ``` where <`appliance name`> is the name of the node (the name displayed in the show cmc appliances CLI command output). 3. To view brief status information: ```plaintext cm-hostname > show fenet update status appliance brief ``` 4. To view verbose status information: ```plaintext cm-hostname > show fenet update status appliance detail ``` ###### Examples The following example shows standard status information for the vx-1 node. ```plaintext cm-1 # show fenet update status appliance vx-1 Appliance Update Status:    Appliance               : vx-1        Status              : complete        Current operation   : gi-update        Current task        : gi-install        Percent done        : 100 %        Start time          : 2019/07/07 21:18:35:455        End time            : 2019/07/07 22:18:49.355    Node: vx-1        Status              : complete        Percent done        : 100 %    Task (01/03)            : gi-check        Status              : complete        Percent done        : 100 %    Task (02/03)            : gi-download        Status              : complete        Percent done        : 100 %    Task (03/03)            : gi-install        Status              : complete        Percent done        : 100 % The following example shows brief information for the Cluster-Acme cluster. cm-1 # show fenet update status cluster Cluster-Acme brief Cluster Update Status: Name         Operation         Percent     Status ----         ---------         -------     ------ Cluster-Acme image-gi-update   39.04       in-progress Node         Task ----         ---- vx-2         07/10             64.08       in-progress vx-1         07/10             14.00       in-progress ``` The following example shows detailed information for the Cluster-Acme cluster. > [!NOTE] > Note > > The following two fields report the status as a percentage: > > - **Percent Done**—The percentage of the update operation as a whole that was completed on the node or the cluster. > - **Percent Complete**—The percentage of the total number of tasks that were completed on the node or the cluster. ```plaintext cm-1 # show fenet update status cluster Cluster-Acme detail Cluster Update Status:    Cluster                 : Cluster-Acme        Status              : in-progress        Current operation   : image-gi-update        Current task        : gi-download        Percent done        : 39.28 %        Percent complete    : 60.00 %        Current num nodes   : 2        Total num nodes     : 2        Version:        Last updated at     : 2019/07/14 19:48:54:821        Last updated op     : image-gi-update        Start time          : 2019/07/15 20:23:23.480        End time            : ******** Node: vx-2    Status                  : in-progress    Percent done            : 64.57 %    Percent complete        : 60.00 %    Task (01/10)            : image-check        Status              : complete        Percent done        : 100 %        Retry count         : 0        Return code         : 0        Start time          : 2019/07/15 20:23:23.486        End time            : 2019/07/15 20:23:33:659        Return message: Operation initiated in the background.    Run 'show fenet image status' for status    Task (02/10)            : gi-check        Status              : complete        Percent done        : 100.00 %        Retry count         : 0        Return code         : 0        Start time          : 2019/07/15 20:23:33.661        End time            : 2019/07/15 20:23:35.732        Return message: Downloading server manifest.        Task (03/10)        : image-fetch        ... ``` ##### Configuring and viewing upgrade settings You can change the following settings for each task: - **Timeout**: Number of seconds before a task times out. - **Max Retry**: Number of times the system will retry a task that failed. - **Parallel Exec**: Whether the task starts on all nodes in the cluster at the same time (parallel execution), or starts on each node one at a time. You can also view the sequence of tasks that are performed in each update operation. #### Upgrade task settings The following table shows the default settings for each task. | **Task** | **Description** | **Timeout** **(Seconds)** | **Max Retry** | **Parallel Exec** | | --- | --- | --- | --- | --- | | gi-check | Check for newer version of guest images. | 60 | 2 | no | | gi- download | Download guest images. | 86400 | 2 | no | | gi-install | Install guest images. | 600 | 2 | no | | image-boot- next | Boot the system from the next partition when the node reboots. | 300 | 2 | no | | image-check | Check for newer version of system image. | 60 | 2 | yes | | image-fetch | Download the system image. | 600 | 2 | no | | image- install | Install the system image. | 600 | 2 | no | | image-prep- reboot | Prepare the system for reboot. | 600 | 2 | \| no \| \| --- \| | | no | | image- reboot | Reboot the node. | 900 | 2 | no | ###### Prerequisites - Monitor, Operator, or Admin access to view settings - Admin access to change settings ###### Viewing upgrade settings using the CLI Use the commands in this section to view upgrade settings. ###### To view the upgrade settings: 1. Log in to the Central Management CLI. 2. View the settings: ```plaintext cm-hostname > show fenet update config ``` ###### To view the update operations: 1. Log in to the Central Management CLI. 2. View the operations: ```plaintext cm-hostname > show fenet update operations ``` ###### Examples The following example shows the default upgrade settings. ```plaintext cm-1 > show fenet update config Update Config:    Task                 : gi-check        Timeout          : 60        Max retry        : 2        Parallel exec    : no    Task                 : gi-download        Timeout          : 86400        Max retry        : 2        Parallel exec    : no    Task                 : gi-install        Timeout          : 600        Max retry        : 2        Parallel exec    : no    Task                 : image-boot-next        Timeout          : 300        Max retry        : 2        Parallel exec    : no    Task                 : image-check        Timeout          : 60        Max retry        : 2        Parallel exec    : yes    Task                 : image-fetch        Timeout          : 600        Max retry        : 2        Parallel exec    : no    Task                 : image-install        Timeout          : 600        Max retry        : 2        Parallel exec    : no    Task                 : image-prep-reboot        Timeout          : 600        Max retry        : 2        Parallel exec    : no    Task                 : image-reboot        Timeout          : 900        Max retry        : 2        Parallel exec    : no The following example shows two upgrade operations and the tasks included in them. cm-hostname > show fenet update operations Update Operations:    Operation id    : 1    Operation name  : image-update    Operation cli   : fenet update cluster system-image        Task        : image-check        Task        : image-fetch        Task        : image-install        Task        : image-rename        Task        : image-boot-next        Task        : image-prep-reboot        Task        : image-reboot    Operation id    : 2    Operation name  : gi-check    Operation cli   : fenet update cluster guest-image        Task        : gi-check        Task        : gi-download        Task        : gi-install ... ``` ###### Configuring upgrade settings using the CLI Use the commands in this section to configure settings for upgrade operations. ###### To change the timeout setting: 1. Log into the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. Change the setting: ```plaintext cm-hostname (config) # fenet update config task timeout ``` where `<task>` is the name of the task shown in [Upgrade task settings](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrade-task-settings), and `<seconds>` is the number of seconds (1–86400) before the task times out. 4. Verify your change: ```plaintext cm-hostname (config) # show fenet update config ``` 5. Save your change: ```plaintext cm-hostname (config) # write memory ``` ###### To change the max retry setting: 1. Log into the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. Change the setting: ```plaintext cm-hostname (config) # fenet update config task retry ``` where `<task>` is the name of the task shown in [Upgrade task settings](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrade-task-settings), and `<number>` is the number of times (1–5) a failed task is tried again. 4. Verify your change: ```plaintext cm-hostname (config) # show fenet update config ``` 5. Save your change: ```plaintext cm-hostname (config) # write memory ``` ###### To change whether the task is executed on nodes in parallel: 1. Log into the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To enable parallel execution: ```plaintext cm-hostname (config) # fenet update config task parallel- execution ``` where `<task>` is the name of the task shown in [Upgrade task settings](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrade-task-settings). 4. To disable parallel execution: ```plaintext cm-hostname (config) # no fenet update config task parallel- execution ``` 5. Verify your change: ```plaintext cm-hostname (config) # show fenet update config ``` 6. Save your change: ```plaintext cm-hostname (config) # write memory ``` ###### To reset default settings: 1. Log into the Central Management CLI. 2. Enable the CLI configuration mode: ```plaintext cm-hostname > enable cm-hostname # configure terminal ``` 3. To reset the timeout setting: ```plaintext cm-hostname (config) # no fenet update config task timeout ``` where `<task>` is the task name (see [Upgrade task settings](/network-and-platform/docs/performing-upgrades-using-cms-cli#upgrade-task-settings)). 4. To reset the maximum retry setting: ```plaintext cm-hostname (config) # no fenet update config task retry ``` 5. To reset the parallel execution setting: ```plaintext cm-hostname (config) # no fenet update config task parallel- execution ``` 6. Verify your changes: ```plaintext cm-hostname (config) # show fenet update config ``` 7. Save your changes: ```plaintext cm-hostname (config) # write memory ``` ###### Examples The following example changes the image-check timeout to 45 seconds. ```plaintext cm-1 (config) # fenet update config task image-check timeout 45 cm-1 (config) # show fenet update config Update Config:  ...    Task: image-check        Timeout              : 45        Max retry            : 2        Parallel exec        : yes ... The following example changes the number of retries for the gi-install task to 3. cm-1 (config) # fenet update config task gi-install retry 3 cm-1 (config) # show fenet update config Update Config:  ...    Task: gi-check        Timeout              : 600        Max retry            : 3        Parallel exec        : no ... The following example enables parallel execution for the image-boot-next task. cm-1 (config) # fenet update config task image-boot-next parallel-execution cm-1 (config) # show fenet update config Update Config:  ...    Task: image-boot-next        Timeout              : 300        Max retry            : 2        Parallel exec        : yes ... The following example restores the default setting for the image-fetch task. cm-1 (config) # no fenet update config task image-fetch retry ```