Users Guide

Table Of Contents
Troubleshooting
Use this section to find answers to troubleshooting questions. This section includes:
Frequently asked questions (FAQ)
Bare metal deployment issues
Contacting Dell on page 124
Related product information
Topics:
Frequently Asked Questions (FAQ)
Bare Metal Deployment Issues
Contacting Dell
OpenManage Integration for VMware vCenter Related Information
Frequently Asked Questions (FAQ)
This section contains some common questions and solutions.
Dell privileges that are assigned while registering the OMIVV
appliance are not removed after unregistering OMIVV
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
Dell Management Center does not display all the relevant logs
when trying to filter a severity category. How can I view all the
logs?
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: To view all the logs in Dell Management Center, select All Categories from the Filter drop-down.
Version Affected: 3.1
How do I resolve error code 2000000 caused by VMware
Certificate Authority (VMCA)?
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: 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
41
108 Troubleshooting