Install Guide

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.
Resolution: Perform the following:
1. Make the previous lead chassis active and run the inventory from OMIVV.
2. Delete the chassis credential profile and all the chassis present in the group from OMIVV.
3. Add the new lead chassis to rediscover the group.
Version Affected: 5.0
• Issue 36–147023: Host firmware update fails, if a canceled firmware update job of related chassis is present.
If you cancel the firmware update job of a PowerEdge MX chassis, subsequent host firmware update job for hosts present in the same
chassis is blocked.
Resolution: Purge the canceled chassis firmware update job to release the lock on the related hosts.
Version Affected: 5.0
• Issue 37–143173: 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
• Issue 38–135743: Time shown for Power Monitoring inventory of the hosts is incorrect when viewed from datacenter and cluster
level.
Resolution: See the host level inventory for correct details.
Version Affected: 5.0
Known issues
13