Users Guide

About host, bare-metal, and iDRAC
compliance
To manage hosts and bare-metal servers with OMIVV, each must meet certain minimum criteria. If not compliant, they are not managed
properly by OMIVV. OMIVV displays details about the noncompliance on a bare-metal or a host, and allows you to fix the noncompliance,
where applicable.
In each case, you can view and fix the compliance issues by running one of the following:
• To view and fix vSphere host compliance issues, see Running the fix noncompliant vSphere hosts wizard.
• To view and fix bare-metal servers that have compliance issues, see Running the fix noncompliant bare-metal server wizard.
Topics:
• Reporting and fixing compliance for vSphere hosts
• Viewing baseline compliance
• Using OMSA with 11th generation servers
• Reporting and fixing compliance for bare-metal servers
Reporting and fixing compliance for vSphere hosts
A host is noncompliant when:
• The host is not assigned to a connection profile.
• The Collect System Inventory on Reboot (CSIOR) is disabled or has not been run, which requires a manual reboot.
• The OMSA agent is not installed, is out of date, or not configured properly. An ESXi host reboot is required, if OMSA is installed or
updated for 11th generation servers.
• The SNMP trap destination of the host is not configured to the OMIVV appliance IP address. The failure in SNMP trap destination
setting might be when iDRAC or host credentials provided in connection profile is invalid, or there are no free slots in iDRAC, or iDRAC
Lockdown Mode is turned on—only in 14th generation hosts.
• OMIVV fails to enable the WBEM service on hosts running ESXi 6.5.
CAUTION:
Hosts in Lockdown Mode do not appear in compliance checks, even if they are noncompliant. They do not
display because their compliance status cannot be determined. Ensure to check the compliance of these systems
manually. In such a scenario, a warning message is displayed.
You can run the fix noncompliant vSphere hosts wizard to fix noncompliant hosts. Some noncompliant ESXi hosts require reboots. An
ESXi host reboot is required, if OMSA must be installed or updated. In addition, a reboot is required on any host that has never run CSIOR.
If you select to automatically reboot an ESXi host, the following actions take place:
• For a CSIOR status fix:
If CSIOR has never run on the host, CSIOR is set to ON on the host, and then the host is set into maintenance mode and rebooted.
• For hosts that does not have OMSA installed, or is running an unsupported version of OMSA:
• OMSA is installed on the host.
• The host is set to maintenance mode and rebooted.
• After reboot is complete, OMSA is configured for the changes to take effect.
• The host comes out of maintenance mode.
• The inventory is run to refresh data.
• For an OMSA status fix where supported version of OMSA is installed, but musts be configured:
• OMSA is configured on the host.
• The inventory is run to refresh data.
To view and fix the noncompliant hosts:
1. In OpenManage Integration for VMware vCenter, from the Manage tab, click Compliance > vSphere Hosts.
14
116 About host, bare-metal, and iDRAC compliance