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
14 Dell EMC OMIVV as a Hardware Support Manager for VMware vSphere Lifecycle Manager
Figure 6: Save image
3.4 Examine drift status and resolution
After you save the image, any of the following states is displayed for the host:
• Compliant: Host is compliant with the image, add-on as and HSP.
• Non-Compliant: Host is not compliant with at least image, or add-on, or HSP.
• Unknown: Host might be not reachable.
To resolve the issue, ensure that host is in reachable state. If the host is reachable, check whether
iDRAC associated to the respective host is reachable or not.
Ensure that hosts that are associated to cluster are inventoried successfully.
• Incompatible: The HSP selected in the vSphere Lifecycle Manager image is not associated to this
cluster. Select relevant HSP which is applicable to the selected cluster. See the description present in
each HSP to get HSP and cluster mappings.
Access OMIVV user facing logs for any errors that are related to intermediate failures in this operation.