Users Guide

● Select a cluster, in the right pane, select Monitor > OMIVV Cluster Information > Firmware > Run Firmware
Wizard.
2. On the Firmware Update Checklist page, ensure that all the prerequisites are verified before scheduling the update, and
then click GET STARTED.
3. On the Update Source page, select the firmware and driver repository profiles.
If the cluster profile is associated to the cluster in which the host is present, by default, the associated firmware, and driver
repository profiles are selected.
If you change the firmware or driver repository profiles, a message is displayed indicating that the selected repository profile
is not associated to baseline and using a different repository may affect the baseline comparison.
NOTE: If you have both driver and firmware repositories are associated with the cluster profile, it is recommenced to
update both driver and firmware simultaneously.
If you do not want to update firmware or driver, or firmware or driver is up-to-date, from the drop-down menu, select No
Repository selected.
The default firmware catalogs (Dell EMC Default Catalog and Validated MX Stack Catalog) are not displayed in the
repository profile option. To use the repository profiles, create a custom repository in OMIVV.
Perform the following to create a custom repository profile:
a. Go to Dell EMC Repository Manager (DRM) and create a catalog.
For more information about creating a catalog using DRM, see Creating catalog in Dell EMC Repository Manager (DRM)
using OMIVV on page 143.
b. Download the catalog and corresponding files.
c. Create a repository profile in OMIVV using the downloaded catalog.
For more information about creating a repository profile, see Create repository profile on page 50.
4. Based on the firmware repository profile you have selected, select an appropriate bundle, and then click NEXT. Only 64-bit
bundles are supported.
NOTE:
Only one bundle can be selected for OEM (debranded) servers even if they are of different models. Even if the
bundle is not applicable for one or more of the OEM servers, the components page of the firmware update wizard lists
each OEM server or firmware component pair. If the firmware update fails for a given firmware component pair, retry
with the alternate bundle displayed for the OEM server.
5. On the Select Driver Components page, select the driver components that require an update, and then click NEXT. When
you select a driver component for update, all the components in the package are selected.
You can use the filter option to filter the data based on the specific column names.
6. On the Select Firmware Components page, select the firmware components that require an update, and then click NEXT.
The count of the components that is based on criticality status such as Urgent, Recommended, Optional, and Downgrades
are displayed.
You can use the filter option to filter the data based on the specific column names.
The components which have lower version than the available version in the catalog, or it is in the same level (Up-to-Date), or
scheduled for an update cannot be selected. To select the components which have lower version than the available version,
select the Allow Firmware downgrade check box.
To select all the firmware components across all the pages, click
.
To clear all the firmware components across all the pages, click .
7. On the Schedule Updates page, enter the firmware update job name and description. The description is an optional field.
The firmware update job name is mandatory. If you purge the firmware update job name, you can reuse the job name again.
8. Under the Additional Settings section, do the following:
a. Enter the Maintenance Mode timeout value between 60–1440 minutes. If the wait time goes beyond the specified time,
the update jobs fail and enter maintenance task will be canceled or timed out. However, the components may get
updated automatically when the host is restarted.
b. From the Enter Maintenance Mode Option drop-down menu, select an appropriate data migration option. For more
information about the data migration option, see the VMware documentation.
NOTE:
Enter maintenance mode task fails if the cluster configuration does not support full data migration or the
storage capacity is insufficient.
144 Host Management