Users Guide

• Hardware Configuration Compliance—Displays the drift in attributes between the system profile that is used in the cluster profile and
the associated hosts that are part of cluster.
• Firmware Compliance—Displays the firmware version drift between the firmware repository profile that is used in the cluster profile
and the associated hosts that are part of cluster.
• Driver Compliance—Displays the driver version drift between the driver repository profile that is used in the cluster profile and the
associated vSAN hosts that are part of cluster profile.
View configuration compliance
1. On the OMIVV home page, click Compliance & Deployment > Compliance > Configuration Compliance.
A table displays clusters with associated cluster profile, system profile, firmware repository profile, and driver repository profile.
For Basic and Advanced system profile types, the system profile name is displayed in the following format: Basic_<system profile
name>, Advanced_<system profile name>.
2. On the Configuration Compliance page, select a cluster.
The configuration compliance information and compliance status are displayed.
The following information is displayed in the Configuration Compliance section:
• Cluster Name—The name of the cluster
• Compliance Status—Displays the compliance status (compliant or non-compliant). If any one of the hosts in the cluster is non-
compliant, the status is displayed as non-compliant.
• Number of hosts—The total number of hosts present in the cluster
• Schedule—The day and time when the next drift detection job is scheduled.
• Last Drift Detection Time—The date and time when the last drift detection job is completed.
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.
Hardware drift is not applicable for the hosts that are managed using chassis credential profile.
The driver drift is not applicable for the hosts that are part of vSphere cluster.
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.
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.
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.
62 Compliance