White Papers
Table Of Contents
- 1 Introduction
- 2 Baselining and remediation in OMIVV
- 3 Baselining using VMware vSphere Lifecycle Manager
- 1.1
- 1.1
- 1.1
- 3.1 Register vSphere Lifecycle Manager in OMIVV
- 3.2 Prerequisites to use OMIVV as HSM in vSphere Lifecycle Manager
- 3.3 Associate OMIVV as HSM in vSphere Lifecycle Manager image
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 1.1
- 3.4 Examine drift status and resolution
- 1.1
- 1.1
- 1.1
- 1.1
- 3.5 Pre-Check
- 1.1
- 1.1
- 3.6 Remediation in vSphere Lifecycle Manager
- 1.1
- 1.1
- 1.1
- 3.7 vSAN Hardware Compatibility Listing (HCL)
- 4 Common issues when using OMIVV as a Hardware Support Manager
- 1
- 1
- 1
- 5 Conclusion
- 6 Technical Support and Resources
8 Dell EMC OMIVV as a Hardware Support Manager for VMware vSphere Lifecycle Manager
2.5 Drift detection in OMIVV
Configuration drift job runs in OMIVV immediately after the cluster profile is created or modified. Later, the
drift detection job also runs for each cluster profile at the scheduled time of each week.
When a new host is added to a cluster after the cluster profile is created (and added to host credential profile
in OMIVV), the host automatically gets added to the list of hosts for the drift detection process during the next
scheduled run of the drift detection job. For more information, see OMIVV 5.1 User’s Guide
.
2.6 Remediation in OMIVV
Remediation of firmware and driver drifts can be achieved by using the firmware update functionality available
in OMIVV.
Note: Driver updates are mainly for clusters running legacy 6.x versions of ESXi, or admins not using
vSphere Lifecycle Manager (which will handle drivers in its image build).
For the configuration drift, you must correct the drifted attributes by logging in to the corresponding iDRAC
consoles. For more information, see OMIVV 5.1 User’s Guide
.