Release Notes

Description: During firmware update, when you downgrade or upgrade the iDRAC versions such as 3.20.20.20, 3.21.21.21,
and 3.21.21.22, the job status is indicated as failed even when the job was successfully run.
Resolution: Refresh the inventory after the job failure and rerun the job for other components.
Version Affected: 4.3 and later
● Issue 28: Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the
cluster has successful inventory."
Description: Configuring the System Lockdown mode at a cluster level sometimes displays a message "No hosts under the
cluster has successful inventory." This message is displayed even when the cluster has successfully inventoried the 14G
hosts that are managed by OMIVV.
Resolution: Reboot the vCenter.
To reboot the vCenter, do the following:
1. Log in to the vSphere Client with a vCenter Single Sign-on Administrator account.
2. Go to Administration > Deployment > Deployment > System Configuration.
3. Click Nodes, select the vCenter Server Appliance node, and click the Related Objects tab.
4. Reboot the vCenter node.
Version Affected: 4.3 and later
● Issue 29: Sometimes post RPM upgrade of OMIVV appliance, multiple entries in the logs are seen in vCenter Recent Tasks.
Description: Sometimes, after RPM upgrade, multiple entries are displayed in logs when viewed on vCenter Recent Tasks.
Resolution: Restart the vCenter services.
Version Affected: 4.3 and later
● Issue 30: Sometimes, the storage inventory data is not displayed for the host managed using chassis credential profile and
present in member chassis.
Description: The storage data may not be displayed for an MX host managed using the chassis credential profile and for a
host present in the member chassis. Though the inventory data of other components is displayed, only the storage-related
data is not displayed
Resolution: Do one of the following:
1. Update the MX7000 chassis firmware version to 1.00.10.
2. Manage the host using iDRAC.
3. Reinstall the host in another slot of the same MX7000 chassis and retry the operation.
Version Affected: 4.3 and later.
● Issue 31–146440: Chassis firmware update fails on small deployment mode.
Resolution: Chassis firmware update is supported only on medium, large, and extra large mode.
Version Affected: 5.0
● Issue 32–147664: Guest OS details of OMIVV appliance are incorrectly displayed in ESXi.
Resolution: This is a known issue with open-vm-tools 10.2.5 which is bundled with CentOS 7.6. OMIVV 5.0 appliance runs on
CentOS 7.6.1810 (64-bit).
● Issue 33–147679: Inventory or warranty job fails to trigger after backup and restore.
Description: Before taking the backup from 4.x, if you clear the inventory or warranty schedule days, and disable the
inventory or warranty schedule, and then restore this backup to 5.x, inventory or warranty job fails to trigger.
Resolution: Contact Dell EMC technical support for further assistance.
Version Affected: 5.0
● Issue 34–148132: For a non-administrator user, inventory fails indicating that the enabling WBEM service is failed on host.
Resolution: For more information about the required privilege for non-administrator user, see the OMIVV 5.0 User's Guide.
Assign the required privilege to user and run the inventory again.
Version Affected: 5.0
● Issue 35–144171:Chassis inventory fails in OMIVV after promoting backup lead as a lead.
When the lead chassis of the MCM group is powered off or not functional, the backup lead gets promoted as the lead
chassis. In this case, inventory of the lead and member chassis fails in OMIVV.
Known issues
13