Release Notes
2
Known Issues
The following section lists the open issues and resolutions with the OpenManage Integration for VMware vCenter:
Issue 1: OMIVV cannot act as a provisioning server during the auto discovery process.
Description: If OMIVV IP address is used as a provisioning server in the iDRAC settings for the newly added Dell servers, these Dell
servers will not be auto discovered. The auto discovery process fails as OMIVV 3.2 does not support MD5 encrypted SSL certicate
signatures to enhance more secure encryption.
Resolution:None.
Issue 2: Intermittent inventory failure for 1st time after OSD.
Description: In case of intermittent failure post rst time deployment, user might observe the error "No inventory record found for
the host <IP / Host name>".
Resolution: Intermittent inventory failure post rst time OSD can be resolved by running the inventory manually.
Issue 3: Test connection for iDRAC in the connection prole page fails in DNC once OSD is successful.
Description: After OS deployment, immediate test connection to iDRAC fails and shows an error, "Fail - Unable to connect to
iDRAC" in the connection prole page.
Resolution: This issue occurs since BMC is unable to obtain an IP address. To resolve this issue, you must restart the management
network. If the issue still persist, user will have to restart the ESXi host.
Issue 4: Dell privileges that are assigned while registering the OMIVV appliance are not removed after unregistering OMIVV.
Description: After registering vCenter with an OMIVV appliance, several Dell privileges are added to the vCenter privilege list. Once
you unregister vCenter from the OMIVV appliance, the Dell privileges are not removed.
NOTE: Although the Dell privileges are not removed, there is no impact to any OMIVV operations.
Version Aected: 3.1
Issue 5: Dell Management Center does not display all the relevant logs when trying to lter a severity category. How can I view all
the logs?
Description: When you select a severity category to lter the log data by choosing All Categories from the drop-down, all the logs
belonging to specic category are displayed accurately. However, if you lter by choosing Info from the drop-down, the Firmware
update logs are not displayed and only the task initiation logs are displayed.
Resolution/Workaround: To view all the logs in Dell Management Center, select All Categories from the Filter drop-down.
Version Aected: 3.1
Issue 6: How do I resolve error code 2000000 caused by VMware Certicate Authority (VMCA)?
Description: When you run the vSphere certicate manager and replace the vCenter server or Platform Controller Service (PSC)
certicate with a new CA certicate and key for vCenter 6.0, OMIVV displays error code 2000000 and throws an exception.
Resolution/Workaround: To resolve the exception, you should update the ssl Anchors for the services. The ssl Anchors can be
updated by running the ls_update_certs.py scripts on PSC. The script takes the old certicate thumbprint as the input argument and
the new certicate is installed. The old certicate is the certicate before the replacement and the new certicate is the certicate
after the replacement. See the following for more information:
6