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.
About this task
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:
Steps
In OpenManage Integration for VMware vCenter,
from the Manage tab, click Compliance > vSphere Hosts.
In the vSphere Hosts page, view the list of noncompliant hosts.
A table is displayed that lists the noncompliant hosts along with the host IP or host name, model, connection profile, the CSIOR status, OMSA status, WBEM status, SNMP trap status, hypervisor, and the iDRAC license status.
To view further details of a noncompliant
host, select a noncompliant host.
To swap the columns within the table, drag
and drop columns within the data grid.
To fix noncomplaint hosts, click Fix non-compliant vSphere Hosts.
The Fix Non-compliant vSphere Hosts wizard is launched. This is a dynamic wizard and only those pages are displayed that are related to the selected noncompliant hosts.
If all the selected noncompliant hosts are CSIOR-compliant, you can view the Turn On CSIOR page in the wizard.
In the Fix Non-compliant
vSphere Hosts wizard, click Next in the Welcome page.
In the Select vSphere Hosts to the Fix Compliance wizard page, select the check boxes
for the hosts you want to fix.
Click Next.
A warning message is displayed, if there
are selected hosts that are not assigned to a connection profile and
prompts you to either continue with the compliance wizard or cancel
the fix compliance wizard. To fix the connection profile noncompliance,
do any one of the following:
To exclude the hosts without the connection profile
assigned to it from the compliance wizard, click Continue
Compliance Wizard.
To exit the wizard and fix the systems from the Connection Profile page, click Cancel. See Creating connection profile. After connection profile is created, you can return
to the wizard.
If you click Continue Compliance
Wizard for the warning message, in the Turn On CSIOR window, select the check boxes
to turn on CSIOR for the selected hosts.
Click Next.
In the Fix OMSA window, select the check boxes to fix OMSA for the selected hosts.
Click Next.
In the Reboot Hosts window, view the ESXi hosts that must be rebooted.
An ESXi host reboot is required, if OMSA is installed
or updated. In addition, a reboot is required on any host that has
never run CSIOR. Do one of the following:
If you want to automatically put hosts in maintenance
mode and reboot when required, select the Automatically
put hosts in maintenance mode and reboot whenever required check box.
If you want to reboot manually, reboot the host after installing OMSA, configure OMSA manually or through the compliance wizard after the host is running and if OMSA is not configured, and run the inventory again. See Running Inventory
Jobs.
Click Next.
In the Summary window, review the actions that take place on the noncompliant hosts.
Manual reboots are required for actions in
the summary page to take effect.
Click Finish.
Results
The wizard configures the SNMP trap destination status to Configured after you fix the iDRAC or host credentials by providing valid information in connection profile, or make any one of the first four slots available in the iDRAC trap destination, or disable System Lockdown Mode in iDRAC.
NOTE System Lockdown Mode is applicable only for 14th generation servers.
If hosts with WBEM noncomplaince exist, ensure to manually fix the conditions for those hosts that caused the WBEM service enablement to fail. You can fix the error conditions by viewing them in the user logs, and then allowing OMIVV to enables the WBEM service for those hosts during inventory.
Fixing iDRAC
license compliance for vSphere hosts
About this task
The vSphere
hosts listed in the vSphere host compliance pages are noncompliant because they do not
have a compatible iDRAC license. The table displays the status of
the iDRAC license. You can click a noncomplaint host to view more details such as, how many days are remaining
for the iDRAC license, and then you can update it, as required. The Run inventory job link is active if the iDRAC compliance status is "non-compliant" or "Unknown" for any one of the host associated to a connection profile.
Steps
In OpenManage Integration for VMware vCenter,
from the Manage tab, click Compliance > vSphere Hosts.
Select a host where iDRAC License Status is Non-compliant.
If license is out of date, click the Purchase/Renew iDRAC License link.
Log in to the Dell License
Management page and update or purchase a new iDRAC license.
Use the information in this page to identify
and update your iDRAC.
After you install an iDRAC license, run an
inventory job for the vSphere host and return to this page after the
inventory job is successfully complete for the host to be compliant.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\