Users Guide

For the non-vSAN cluster, for more information about running firmware update for the non-vSAN cluster, see Running firmware
update wizard for non-vSAN clusters on page 94.
Running firmware update wizard for non-vSAN
host
NOTE: During the firmware update process, ensure that you do not delete the following:
The host from vCenter for which the firmware update job is in progress.
The connection profile of the host for which the firmware update job is in progress.
To perform the firmware update for a non-vSAN host, perform the following steps:
1. To access the firmware update wizard, in OpenManage Integration, click Hosts and perform either of the following actions:
Right-click a host, select All OpenManage Integration Actions > Firmware Update.
On the Hosts page, click a host, and then select All OpenManage Integration Actions > Firmware Update.
In the Navigator pane, select a host, and then click Summary > OMIVV Host Information > Run Firmware Wizard.
In the Navigator pane, select a host, and then click Monitor > OMIVV Host Information > Firmware > Run Firmware
Wizard.
OMIVV checks compliance of the host and whether any other firmware update job is in progress in any host within the same cluster.
After the verification, the Firmware Update wizard is displayed.
NOTE: If you upgrade from an earlier version of OMIVV to the available version and there is already a firmware
update job scheduled, you can launch the firmware update wizard on the same host after you back up the OMIVV
database and restore it to the available version.
2. On the Welcome page, read the instructions, click Next.
The Select Update Source page is displayed.
3. On the Select Update Source page, select either of the following:
a. The Current repository location is displayed and selects the firmware update bundle from the Select an Update Bundle drop-
down list.
NOTE: 64-bit bundles are not supported for 12th generation hosts with iDRAC version 1.51 and earlier.
NOTE: 64-bit bundles are not supported for 11th generation hosts on all iDRAC versions.
NOTE: OMIVV supports 32–bit and 64–bit bundles for firmware update. Apart from the mentioned bundles,
OMIVV also creates a hybrid bundle when there are 32-bit and 64-bit bundles available in the catalog for a
particular model with the same release ID.
b. To load a single firmware update from a file, select Single DUP. If you select Single DUP, go to step 6.
A single DUP can reside on a CIFS or NFS share that is accessible by the virtual appliance. Enter the File Location in one of the
following formats:
NFS share — <host>:/<share_path/FileName.exe
CIFS share — \\<host accessible share path>\<FileName>.exe
For CIFS share, OMIVV prompts you to enter the user name and password in a domain format that can access the share drive.
NOTE:
OMIVV supports only Server Message Block(SMB) version 1.0 and SMB version 2.0 based CIFS shares.
It is recommended to use SMB version 2.0 based CIFS shares.
4. Click Next.
The Select Components page is displayed.
5. Use the check boxes to select at least one firmware component from the list, and then click Next.
The components that are either in a downgrade or currently scheduled for update cannot be selected. You can select the components
that are listed for downgrade by selecting the Allow Downgrade option.
The Schedule Firmware Update page is displayed.
To filter comma-separated values from the content of the various components of the data grid, use Filter.
You can also drag columns within the component data grid. If you want to export from the wizard, click .
About firmware updates
91