White Papers

7 Dell EMC OMIVV as a Hardware Support Manager for VMware vSphere Lifecycle Manager
2 Baselining and remediation in OMIVV
OMIVV provides an ability to baseline the clusters with respect to a desired state.
Baselining in OMIVV is achieved using cluster profile. A cluster profile consists of firmware repository profile,
driver repository profile, and system profile, or any combination of these profiles.
When a cluster is associated to a cluster profile, all the OMIVV-managed hosts in the corresponding cluster
automatically becomes part of the drift detection job.
2.1 Firmware repository profile
Based on your environment and requirements, you can choose to use one of the default available repositories,
or create a custom repository using Dell EMC Repository Manager
(DRM) that matches your server inventory
and your data center requirements. You can use the firmware repositories in cluster profile.
For vSAN, the storage controller must be at specific levels. Online repositories can be updated every two weeks,
and those updates may move a specific vSAN cluster out of VMware support compliance. Hence, baselining
vSAN cluster baselining against online repository is not supported.
Create a custom repository using DRM that aligns with the vSAN firmware requirements as per Hardware
Compatibility List (from VMWare) and copy it in either CIFS or NFS share and create a firmware repository
profile in OMIVV. For more information, see OMIVV 5.1 User’s Guide
.
2.2 Driver repository profile
Baselining against driver repository profile is supported only for vSAN clusters. Download the drivers as
applicable to your vSAN clusters and copy them in a CIFS or NFS. Create a driver repository profile in OMIVV
pointing to the share location, it can be used in cluster profile. For more information, see
OMIVV 5.1 User’s
Guide.
2.3 System profile
System profile can be created referencing either a bare-metal server or a managed host. This profile captures
the component-level settings and configuration of iDRAC, BIOS, RAID, Event Filters, FC, and NICs.
Baselining against a system profile helps you in getting notification when a configuration drift is detected in any
of the machines in the baselined cluster against the desired state in machine-level settings.
2.4 Update cluster profile
The cluster profile will not refresh itself when the source repository changes. To identify the updated profiles
that are associated with cluster profile, go to the Cluster Profiles page. Yellow warning icon will be displayed
next to the updated cluster profile.
To update the cluster profile with the latest available driver or firmware, or system profiles, select the
impacted cluster profile, click Update Profiles on the cluster profile page. For more information, see
OMIVV
5.1 User’s guide