Users Guide

The Compliance Status section displays the compliance state of the hardware, firmware, and driver components. The
different compliance states are:
● Compliant—Displays the count of hosts that are compliant with associated hardware, firmware, and driver components.
● Non-compliant—Displays the count of hosts that are non-compliant with associated hardware, firmware, and driver
components.
● Not applicable—Displays the count of not applicable hosts.
The driver drift is not applicable for the hosts that are part of vSphere cluster.
Hardware drift is not applicable for the hosts that are managed using chassis credential profile.
If the cluster profile is created using the online catalog, the firmware compliance is not applicable for vSAN clusters.
3. To view the drift details, click VIEW DRIFT REPORT. This link is enabled only for non-compliant clusters. For more
information about viewing drift report, see View drift report on page 78.
View drift report
Steps
1. On the OMIVV home page, click Compliance & Deployment > Compliance > Configuration Compliance.
2. Click VIEW DRIFT REPORT.
The Configuration Compliance Report page displays the drift details of the hardware, firmware, and driver components.
The drift detection job status is displayed in the Summary section.
For Hardware:
● 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 (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 183.
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 183.
● 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.
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: If more than one version of firmware is available, the latest firmware version is always used for compliance
comparison.
78 Compliance