User's Manual

Table Of Contents
About Host, Bare Metal, and iDRAC Compliance Issues
To manage hosts, bare metal servers, and iDRAC with the Dell Management Plug-in each must meet certain minimum
criteria. If not compliant, then they are not managed properly by the Dell Management Plug-in. Use the Fix Non-
Compliant Hosts, Bare Metal Server, and iDRAC compliance links to see which host/bare metal servers/iDRACs in your
configuration are not compliant and fix them. This wizard displays hosts/bare metal servers/iDRACs where:
Hosts have not been assigned to a connection profile.
If a connection profile is not assigned to a host, a dialog box is offered to take you to the Connection Profile
screen. This configuration is outside this wizard. Return later to run this wizard.
Collect System Inventory on Reboot (CSIOR) is disabled or has not been run, which requires a manual reboot.
The OMSA agent (Host Root credentials ) is not installed, is out of date, or not configured properly.
Bare metal servers have outdated Integrated Dell Remote Access Controller (iDRAC) firmware, Lifecycle
Controller (LC) firmware, or BIOS versions.
CAUTION: Hosts in Lockdown Mode will not appear in compliance checks even if they are non-compliant. They do
not display because their compliance status cannot be determined. Make sure to check the compliance of these
systems manually. When this is the case a warning displays.
In each case, you need to fix the compliance issues by running one of the following:
To fix vSphere host compliance issues, see Running The Fix Non-Compliant vSphere Hosts Wizard
To fix bare metal servers that have compliance issues, see Running The Fix Non-Compliant Bare Metal Server
Wizard
To fix iDRAC compliance issues: iDRAC License Compliance
Related Information:
Re-Checking Bare Metal Server Compliance
Downloading An ISO For Manual Firmware Updates
Running The Fix Non-Compliant vSphere Hosts Wizard
Run the Fix Non-Compliant vSphere Hosts Wizard to fix non-compliant hosts. For information about compliance, see
About Host And Bare Metal Compliance Issues. Some non-compliant 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, then CSIOR is set to
ON
on the host, and then the host is set into
maintenance mode and rebooted.
For an OMSA status fix:
a. OMSA is installed on the host.
b. The host is set to maintenance mode and rebooted.
c. After the reboot completes, OMSA is configured for the changes to take effect.
d. The host comes out of maintenance mode.
e. Inventory is run to refresh data.
To run the Fix Non-Compliant vSphere Hosts Wizard:
31