Manualshelf

Users Guide

ManualsBrandsDell ManualsAnalyticsOpenManage Integration for VMware vCenter Version 5.2
151152153154155156157158159160
Resolution: Rediscover the server. If the missing server is supported, then it is listed in the bare-metal inventory.
Version Affected: 5.0
After OS deployment, OMIVV failed to add ESXi host to vCenter or
failed to add Host Profile or Enter Maintenance Mode is failed for
host
After OS deployment, OMIVV queries vCenter to perform the host actions (Add host, Add Host Profile, or Enter Maintenance
Mode). If the query does not receive a response within two minutes, the specific action on vCenter is timed out, and a message
is displayed in the task history indicating that the communication failure. However, at times, the vCenter query operations are
successful.
Resolution: Take the host IP from the task history and add manually.
iDRAC license status is displayed as compliant on the management
compliance page when the iDRAC IP is not reachable
After performing periodic inventory, if iDRAC not reachable, iDRAC License status is displayed as compliant on the management
compliance page.
Resolution: Ensure that the iDRAC is reachable and run the inventory again to get the right iDRAC license details.
ESXi host is either disconnected or not responding state after
successful OS deployment using OMIVV.
ESXi host fails to send heartbeat packets to vCenter because its DNS is not properly configured to lookup FQDN of the
vCenter.
Resolution: Perform the following tasks:
1. Remove the ESXi host from the vCenter inventory.
2. Add the host in vCenter using the Add host wizard.
3. Create a host credential profile and run the inventory.
Deployment job times out when network interface card (NIC) of
OMIVV is not connected to the ESXi host network
OS deployment has dependency on the selection of NIC. If the correct NIC is not selected, then OSD job times out.
Resolution: Select appropriate 'Appliance NIC connected to Host ' from Configure Host Settings page of Deployment wizard .
This is needed by OMIVV to reach ESXi network during OS installation process.
Warranty job is not running for certain hosts
In a PSC environment with multiple vCenters, if you add a host using FQDN to one vCenter and IP to another vCenter, warranty
job runs only for one host instance.
Resolution: Remove the disconnected host instance from the host credential profile and run the inventory and warranty job.
Version Affected: 5.0
160
Frequently Asked Questions-FAQ