Release Notes

Table Of Contents

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

certificate 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 first time deployment, user might observe the error "No inventory record found

for the host <IP / Host name>".

Resolution: Intermittent inventory failure post first time OSD can be resolved by running the inventory manually.

Issue 3: Test connection for iDRAC in the connection profile 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 profile 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 Affected: 3.1

Issue 5: Dell Management Center does not display all the relevant logs when trying to filter a severity category. How can I view

all the logs?

Description: When you select a severity category to filter the log data by choosing All Categories from the drop-down, all the

logs belonging to specific category are displayed accurately. However, if you filter 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 Affected: 3.1

Issue 6: How do I resolve error code 2000000 caused by VMware Certificate Authority (VMCA)?

Description: When you run the vSphere certificate manager and replace the vCenter server or Platform Controller Service

(PSC) certificate with a new CA certificate 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 certificate thumbprint as the

input argument and the new certificate is installed. The old certificate is the certificate before the replacement and the new

certificate is the certificate after the replacement. See the following for more information:

● http://kb.vmware.com/selfservice/search.do?

cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2121701

● http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=D T_KB_1_1&externalId=2121689

● Dell OpenManage Integration for VMware vCenter 3.1 User's Guide for Web client

Version Affected: 3.1

Issue 7: Firmware Update Wizard shows a message mentioning that the bundles are not retrieved from firmware repository.

How can I continue with the firmware update?

Description: In Web client, when you are running the Firmware Update wizard for a single host, the Select Components screen

displays the firmware details for the components. If you select the desired firmware updates and click Back twice to arrive at

6 Known Issues