Users Guide

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
Proactive HA initialization is not happening after
performing backup and restore
When you restore OMIVV from the previous version that is registered with the vSphere Client, for Proactive HA enabled clusters the Dell
Provider is disconnected.
Resolution: Disable and enable the Proactive HA for clusters.
Version Affected: 5.0
OMIVV page displays invalid session, or time out
exception, or two million errors in Firefox browser
If the OMIVV page is idle for some time (5–10 minutes), the invalid session, or time out exception, or two million errors is displayed.
Resolution: Refresh the browser. If the issue persists, log out and log in from vCenter.
To see the correct data in OMIVV, ensure that you complete the task listed in resolution.
Version Affected: 5.0
In vCenter, recent tasks pane does not show the details
column for some OMIVV task notifications
Resolution: To see the task notifications, in vCenter, go to Task Console of vCenter.
Version Affected: 5.0
When using vCenter 6.5 U2, 2000002 error might be
displayed in all the pages of OMIVV
Resolution: Use the latest patch from VMware for 6.5 U2 or migrate to 6.5 U3 and later version.
Version Affected: 5.1
The 2000002 error is displayed in all the pages of OMIVV
after performing RPM upgrade or backup and restore from
an earlier OMIVV version to a later OMIVV version
Before registering the current version, if you have an earlier version of OMIVV in vCenter server, an SSL handshake exception causes the
new version of OMIVV to be out of reach until vCenter refreshes the new plugin data. Because, the vCenter contains the data from the
earlier version of OMIVV which handles SSL traffic differently.
Resolution:
• Restart vSphere Client on the vCenter server.
• If the issue persists:
Frequently Asked Questions-FAQ
145