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
16 Dell EMC OMIVV as a Hardware Support Manager for VMware vSphere Lifecycle Manager
Figure 8: Pre-check in progress
Figure 9: Pre-check results
3.6 Remediation in vSphere Lifecycle Manager
For the firmware remediation, the HSM must be associated to vCenter. HSP selected in the cluster image
should be active (Optional).
During remediation, OMIVV performs the following:
• Download firmware components from network share to OMIVV Share
OMIVV downloads all the drifted firmware components from the share that is given in the firmware
repository that is attached to cluster profile to OMIVV share. If there are any failures occurred at this
stage, access OMIVV user facing logs for more information.
Ensure that the share that is given in the firmware repository is reachable. If there is a private network,
ensure that OMIVV is reachable using proxy.