Users Guide

● Service Tag—Indicates the Service Tag of the host.
● Drift Status—Indicates the drift status (non-compliant or failed).
● Instance—Indicates the hardware component name.
● Group—Indicates the group name of the attributes.
● Attribute Name—Indicates the attribute name.
● Current Value—Indicates the current value of the attribute in the host.
● Baseline Value—Indicates the baseline value.
● Drift Type/Error—Indicates the reason for non-compliance. For more information about the drift type, see Component vs.
baseline version comparison matrix on page 171.
NOTE: Drift detection job fails only when the host or iDRAC is not reachable. If the host or iDRAC is inventoried
successfully, then the drift detection job shows successful. To check any other drift detection job failure reasons, see the
Drift Type/Error column in drift report.
For firmware and driver:
● Host Name or IP—Indicates the host IP or hostname.
● Service Tag—Indicates the Service Tag of the host.
● Drift Status—Indicates the drift status.
● Component Name—Indicates the name of the component.
● Current Value—Indicates the current value of the attribute in the host.
● Baseline Value—Indicates the baseline value.
● Drift Type/Error—Indicates the reason for non-compliance. For more information about the drift type, see Component vs.
baseline version comparison matrix on page 171.
● Criticality (for firmware)—Indicates the importance level of updating the version of an identified component.
● Recommendation (for driver)—Indicates the update recommendation of a driver component.
NOTE:
If more than one version of firmware is available, the latest firmware version is always used for compliance
comparison.
You can use the filter option to see the drift details based on the drift status.
NOTE:
The 32-bit firmware bundle is not supported in 5.x. If the cluster profile is associated with 32-bit firmware bundle in
4.x version, the drift status is displayed as failed when you perform the backup and restore from 4.x to 5.x. Use the 64-bit
firmware bundle with cluster profile and rerun the drift detection job.
NOTE: You might see a mismatch between the OMIVV and vSphere Lifecycle Manager drift report. This is because the
vSphere Lifecycle Manager always shows live drift report and OMIVV shows the drift report that is based on the scheduled
date and time. If you see a mismatch between the drift reports, run the drift detection job on-demand on the Drift
Detection Jobs page.
72 Compliance