Users Guide

Steps
1. On the OMIVV home page, click Compliance & Deployment > Compliance > Management Compliance > Add OEM
Hosts.
2. In the Add OEM Hosts window, from the vCenter Instance drop-down list, select an instance of vCenter.
3. From the Host Credential Profile drop-down list, select an appropriate host credential profile.
4. To add or remove the associated host, click ADD/REMOVE HOST.
The Add or Remove Hosts window is displayed.
a. On the Add or Remove Hosts page, expand the tree view, select or remove the host, and then click OK.
Only the hosts that are not managed by OMIVV are displayed in the Select Hosts window.
OMIVV tests the connection automatically and test connection results are displayed in the Add OEM Hosts window.
The iDRAC Test and Host Test columns displays the test connection result for iDRAC Credentials and Host
Credentials.
To stop all the test connections, click ABORT TEST.
The selected hosts are added to the selected host credential profile and inventory is triggered.
Configuration Compliance
The Configuration Compliance page displays the compliance status that is based on the drift detection for all the clusters
that are associated with the cluster profile. In vCenter linked mode environment with multiple vCenter servers, configuration
compliance page list all the clusters from all the vCenters that belong to the same vCenter linked mode environment registered
with same appliance.
Remediation of firmware and driver drifts can be achieved by using the firmware update functionality available in OMIVV.
For the configuration drift, you must correct the drifted attributes by logging in to the corresponding iDRAC consoles. You
cannot fix configuration drift in OMIVV. Configuration remediation might impact RAID settings, Network settings, iDRAC
settings, and System BIOS settings.
● 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
Steps
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 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.
Compliance
77