Users Guide

● System Peak Power—displays the host peak power.
● System Peak Power Start Date—displays the date and time when the host peak power started
● System Peak Power End Date—displays the date and time when the host peak power ended
● System Peak Amps—displays the hosts peak amps.
● System Peak Amps Start Date—displays the starting date and time of the host peak amps.
● System Peak Amps End Date—displays the end date and time of the host peak amps.
NOTE: Time that is shown for Power Monitoring inventory of the hosts is incorrect when viewed from data center and
cluster level. See the host level inventory for correct details.
View warranty information of a data center and cluster
To view a warranty status, ensure to run a warranty job. See Schedule warranty retrieval jobs on page 99. The Warranty
Summary page lets you monitor the warranty expiration date. The warranty settings control when server warranty information
is retrieved from Dell online by enabling or disabling the warranty schedule, and then setting the Minimum Days Threshold alert.
● Warranty Summary—the host warranty summary is displayed using icons to visually show the number of hosts in each
status category.
● Host—displays the hostname.
● Service Tag—displays the service tag of the host.
● Description—displays a description.
● Warranty Status—displays the warranty status of the host. Status options include:
○ Active—the host is under warranty, and has not exceeded any threshold.
○ Warning—the host is Active, but exceeded the warning threshold.
○ Critical—same as warning, but for a critical threshold
○ Expired—the warranty has expired for this host.
○ Unknown—OpenManage Integration for VMware vCenter does not get warranty status because the warranty job is not
run, an error has occurred getting the data, or the system does not have a warranty.
● Days Left—displays the amount of days left for the warranty.
Firmware update
The OMIVV enables you to perform BIOS and firmware update jobs on the managed hosts. You can perform concurrent
firmware update jobs across multiple clusters or nonclustered hosts. Running concurrent firmware update on two hosts of the
same cluster is not allowed.
NOTE:
In a multi-appliance environment, to perform firmware update on cluster or host, ensure that the appliance
registered with target vCenter is loaded.
The following are the two methods to perform the firmware updates:
● Single DUP—performs firmware update for iDRAC and BIOS by pointing directly to the DUP location (either CIFS or NFS).
The single DUP method can be used only at the host level.
● Repository Profiles—performs firmware and driver updates. The method can be used at both host level and cluster level.
The following are the repository profiles that are used for firmware and driver updates:
○ Firmware Repository—A repository profile that uses firmware catalog to get the firmware information.
The following are the two types of firmware repository:
￭ User-created firmware repository
￭ Factory-created firmware repository: The following are the two types of factory created catalogs: Factory-created
catalogs are not applicable for vSAN cluster firmware update and baselining.
- Dell Default Catalog: A factory-created firmware repository profile that uses the Dell EMC Online catalog to get
the latest firmware information. If the appliance does not have an Internet connection, modify this repository to
point to a local CIFS or NFS or HTTP or HTTPs based shares.
- Validated MX Stack Catalog: A factory-created firmware repository profile that uses the Dell EMC online catalog
to get the validated firmware information for MX chassis and its corresponding sleds.
○ Driver repository—A repository profile contains offline bundles that can be used to update the driver for vSAN clusters.
Host Management
121