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.
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
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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalUpgrade the cluster:
cm-hostname (config) # fenet update cluster <cluster name>where <cluster name> is the name of the cluster.
Monitor the status:
cm-hostname (config) # show fenet update status cluster <cluster name>
To upgrade to a specific version of the system and upgrade guest images on a cluster:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalUpgrade the cluster:
cm-hostname (config) # fenet update cluster <cluster name> version<version>
Monitor the status:
cm-hostname (config) # show fenet update status cluster <cluster name>
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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalUpgrade the node:
cm-hostname (config) # fenet update appliance <appliance name>where <
appliance name>is the name of the Virtual Execution appliance.Monitor the status:
cm-hostname (config) # show fenet update status appliance <appliance name>
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.
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
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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo upgrade to the latest version of the system image and then reboot the system:
cm-hostname (config) # fenet update cluster <cluster name> system-imageor
cm-hostname (config) # fenet update cluster <cluster name> system-image rebootwhere <
cluster name>is the name of the cluster.To upgrade to the latest version of the system image without rebooting the system:
cm-hostname (config) # fenet update cluster <cluster name> system-image no-rebootTo upgrade to a specific version of the system image:
cm-hostname (config) # fenet update cluster <cluster name> system-image version <version>where <
cluster name>is the name of the cluster, and<version>is the system image version number.Check the progress:
cm-hostname (config) # show fenet update status cluster <cluster name>
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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo install the latest version of the system image and then reboot the system:
cm-hostname (config) # fenet update appliance <appliance name> system imageor
cm-hostname (config) # fenet update appliance <appliance name> system image rebootwhere
<appliance name>is the name of the Intelligent Virtual Execution - Server appliance.To install the latest version of the system image without rebooting the system:
cm-hostname (config) # fenet update appliance <appliance name> system- image no-rebootTo install a specific version of the system image:
cm-hostname (config) # fenet update appliance <appliance name> system- image version <version>or
where <appliance name> is the name of the Virtual Execution appliance, and <version> is the system image version number.To upgrade to a specific version of the system image and upgrade the guest images:
cm-hostname (config) # fenet update appliance <appliance name> version<version>Check the progress:
cm-hostname (config) # show fenet update status appliance <appliance name>
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.
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
You can cancel, suspend, and resume a guest-images download. For details, see 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:
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalStart the upgrade:
cm-hostname (config) # fenet update cluster <cluster name> guest-imageCheck the progress:
cm-hostname (config) # show fenet update status cluster <cluster name>
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:
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalStart the upgrade:
cm-hostname (config) # fenet update appliance <appliance name> guest- imageCheck the progress:
cm-hostname (config) # show fenet update status appliance <appliance name>
Example
The following example downloads and installs guest images on the vx-1 node.
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
You can cancel, suspend, and resume a guest-images download. For details, see 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:
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalStart the upgrade:
cm-hostname (config) # fenet update cluster <cluster name> guest-image downloadCheck the progress:
cm-hostname (config) # show fenet update status cluster <cluster name>
Downloading Guest Images to a node
The following procedure describes how to download guest images to a specific node.
Download the guest images:
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalDownload the guest images:
cm-hostname (config) # fenet update appliance <appliance name> guest- image downloadCheck the progress:
cm-hostname (config) # show fenet update status appliance <appliance name>
Example
The following example downloads guest images to all nodes of Cluster-Acme.
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 statusInstalling 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:
Enable the CLI configuration mode:
cm-hostname # configure terminalEnsure that guest images were downloaded:
cm-hostname (config) # show fenet update status cluster <cluster name>Install the guest images:
cm-hostname (config) # fenet update cluster <cluster name> guest-image installCheck the progress:
cm-hostname (config) # show fenet update status cluster <cluster name>
Installing Guest Images on a node
The following procedure shows how to install guest images on a specific node.
Install guest images:
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalEnsure that guest images were downloaded:
cm-hostname (config) # show fenet update status appliance <appliance name>Install the guest images:
cm-hostname (config) # fenet update appliance <appliance name> guest- image installCheck the progress:
cm-hostname (config) # show fenet update status appliance <appliance name>
Example
The following example installs downloaded guest images on the vx-2 node.
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 statusSuspending, 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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo suspend the upgrade on a cluster:
cm-hostname (config) # fenet update cluster <cluster name> suspendTo suspend the upgrade on a node:
cm-hostname (config) # fenet update appliance <appliance name> suspend
Resuming a suspended upgrade
The following procedure shows how to resume an upgrade that was suspended.
To resume a upgrade:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo resume an upgrade on cluster:
cm-hostname (config) # fenet update cluster <cluster name> resumeTo resume an upgrade on a node:
cm-hostname (config) # fenet update appliance <appliance name> resume
To resume a guest-images upgrade:
To resume a guest-images upgrade on a cluster:
cm-hostname (config) # fenet update cluster <cluster name> guest-image resumeTo resume a guest-images upgrade on a node:
cm-hostname (config) # fenet update appliance <appliance name> guest- image resume
Canceling an upgrade
The following procedure shows how to cancel an upgrade operation.
To cancel an upgrade:
Log into the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo cancel an upgrade on a cluster:
cm-hostname (config) # fenet update cluster <cluster name> cancelTo cancel an upgrade on a node:
cm-hostname (config) # fenet update appliance <appliance name> cancel
To cancel a guest-images upgrade:
To cancel a guest-images upgrade on a cluster:
cm-hostname (config) # fenet update cluster <cluster name> guest-image cancelTo cancel a guest-images upgrade on a node:
cm-hostname (config) # fenet update appliance <appliance name> 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.
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:
Log in to the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enableTo delete guest images from all nodes in a cluster:
cm-hostname (config) # fenet update cluster <cluster name> guest-image deleteTo delete guest images from a node:
cm-hostname (config) # fenet update appliance <appliance name> guest- image delete
Example
The following example deletes the guest images from Cluster-Acme.
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 statusMonitoring 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:
Log in to the Central Management CLI.
To view standard status information:
cm-hostname > show fenet update status cluster <cluster name>where <
cluster name> is the name of the cluster.To view brief status information:
cm-hostname > show fenet update status cluster <cluster name> briefTo view detailed status information:
cm-hostname > show fenet update status cluster <cluster name> detail
Monitoring node upgrades
The following procedure shows how to monitor the status of a node upgrade.
To monitor a node upgrade:
Log in to the Central Management CLI.
To view standard status information:
cm-hostname > show fenet update status appliance <appliance name>where <
appliance name> is the name of the node (the name displayed in the show cmc appliances CLI command output).To view brief status information:
cm-hostname > show fenet update status appliance <appliance name> briefTo view verbose status information:
cm-hostname > show fenet update status appliance <appliance name> detail
Examples
The following example shows standard status information for the vx-1 node.
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
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.
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 |
| |
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:
Log in to the Central Management CLI.
View the settings:
cm-hostname > show fenet update config
To view the update operations:
Log in to the Central Management CLI.
View the operations:
cm-hostname > show fenet update operations
Examples
The following example shows the default upgrade settings.
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 <name> 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 <name> 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:
Log into the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalChange the setting:
cm-hostname (config) # fenet update config task <task> timeout <seconds>where
<task>is the name of the task shown in Upgrade task settings, and<seconds>is the number of seconds (1–86400) before the task times out.Verify your change:
cm-hostname (config) # show fenet update configSave your change:
cm-hostname (config) # write memory
To change the max retry setting:
Log into the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalChange the setting:
cm-hostname (config) # fenet update config task <task> retry <number>where
<task>is the name of the task shown in Upgrade task settings, and<number>is the number of times (1–5) a failed task is tried again.Verify your change:
cm-hostname (config) # show fenet update configSave your change:
cm-hostname (config) # write memory
To change whether the task is executed on nodes in parallel:
Log into the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo enable parallel execution:
cm-hostname (config) # fenet update config task <task> parallel- executionwhere
<task>is the name of the task shown in Upgrade task settings.To disable parallel execution:
cm-hostname (config) # no fenet update config task <task> parallel- executionVerify your change:
cm-hostname (config) # show fenet update configSave your change:
cm-hostname (config) # write memory
To reset default settings:
Log into the Central Management CLI.
Enable the CLI configuration mode:
cm-hostname > enable cm-hostname # configure terminalTo reset the timeout setting:
cm-hostname (config) # no fenet update config task <task> timeoutwhere
<task>is the task name (see Upgrade task settings).To reset the maximum retry setting:
cm-hostname (config) # no fenet update config task <task> retryTo reset the parallel execution setting:
cm-hostname (config) # no fenet update config task <task> parallel- executionVerify your changes:
cm-hostname (config) # show fenet update configSave your changes:
cm-hostname (config) # write memory
Examples
The following example changes the image-check timeout to 45 seconds.
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