Users Guide

Version Aected: This issue might be only seen when restoring a backup from OMIVV 3.0.0.173 build number to OMIVV 3.0.0.197

build number.

OMIVV version for is not updated from About Screen after the Appliance is updated

This is a known issue with the Internet Explorer where it is still using the old cache values. Clearing the IE's cache would show the

correct version.

Using OpenManage Integration for VMware vCenter to update an Intel Network card with the

rmware version of 13.5.2 is not supported.

There is a known issue with Dell PowerEdge 12th generation servers and some Intel Network cards with the rmware version of

13.5.2. Updating some models of Intel network cards at this version of rmware fails when the rmware update is applied using the

Lifecycle Controller. Customers with this version of rmware must update the network driver software using an operating system. If

the Intel Network card has a version of rmware other than 13.5.2, you can update using OpenManage Integration for VMware

vCenter. For more information, see http://en.community.dell.com/techcenter/b/techcenter/archive/2013/03/20/intel-network-

controller-card-with-v13-5-2-rmware-cannot-be-upgraded-using-lifecycle-controller-to-v13-5-6.aspx

NOTE: Note: When using the one-to-many rmware update, avoid selecting Intel network adapters that are at version

13.5.2, as the update will fail and stop the update task from updating remaining servers.

On running a warranty retrieval job, the warranty job status is not listed in the Warranty Job

Queue page

If your network needs proxy details to connect to the internet and the proxy is not set on the OMIVV appliance, the warranty

retrieval job fails and the job is not listed under warranty job queue.

Resolution: Set the proxy details and trigger the warranty job again.

Version Aected: All

Using OpenManage Integration for VMware vCenter to update an Intel Network card from 14.5

or 15.0 to 16.x fails due to staging requirement from DUP

This is a known issue with NIC 14.5 and 15.0. You must use the custom catalog to update the rmware to 15.5.0 rst before updating

the rmware to 16.x.

Version Aected: All

On trying a rmware update with an invalid DUP, the hardware update job status on the

vCenter console neither fails nor times-out for hours, though the job status in LC says

‘FAILED’. Why is this happening?

When the invalid DUP is picked for rmware update, the status of the task in the vCenter console window remains ‘In Progress’ but

the message is changed to the reason of failure. This is a known VMware defect and will be xed in the future releases of VMware

vCenter.

Resolution: The task has to be cancelled manually.

Version Aected: All

Administration Portal is still showing the unreachable Update Repository location.

If the user provided a unreachable Update Repository path, the error message “Failed: Error while connecting to the URL …. ” is

displayed on the top of the Appliance Update view, however the Update Repository Path is not cleared out to the value before

update.

Resolution: Move out of this page to another page and make sure the page is refreshed.