Release Notes

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–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 32–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 33–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 34–148838: Unable to delete the ISO profile.
Resolution: None. You can edit the profile and use the same profile for different deployment task.
Version Affected: 5.0
• Issue 35–156807: Invalid task name might be displayed for OMIVV tasks under VMware Task Console.
Resolution: None
Version Affected: 4.3.1 and later
• Issue 36–157172: After you modify the Data Retrieval Schedule settings, Event Posting Level settings are cleared.
Resolution: Reconfigure the Event Posting Level settings.
Version Affected: 5.0 and later
• Issue 37–156357: Firmware remediation from vSphere Lifecycle Manager fails on host having iDRAC version lower than 2.70.70 and
IDSDM component.
The support for IDSDM firmware update is introduced from iDRAC firmware version 2.70.70. When the machine gets updated to
2.70.70, it will notice the presence of IDSDM and with older firmware. If you are managing cluster having iDRAC version lower than
2.70.70 and IDSDM component using vSphere Lifecycle Manager, the host remains in non-complaint after firmware remediation.
Resolution: Perform the remediation operation twice. Alternatively, you can use the firmware update functionality from OMIVV to
update the iDRAC to 2.70.70, and then use the vSphere Lifecycle Manager flow.
Version Affected: 5.1
• Issue 38–159900: Unable to view the proper remediation failure message in vSphere Lifecycle Manager.
When remediation of a host fails, the vSphere Lifecycle Manager displays "Unknown Message" instead of proper message sent from
OMIVV. This is a limitation in vCenter 7.0. For more information, see the VMware documentation.
Resolution: See the OMIVV logs for proper failure message.
Version Affected: 5.1
• Issue 39–160776: Unable to associate the cluster profile deleted and created using the same name in vSphere Lifecycle Manager.
This issue occur when the cluster profile associated with vSphere Lifecycle Manager image is deleted and if you create the new cluster
profile with the same name and try to associate the new cluster profile to vSphere Lifecycle Manager image.
Resolution: Create a cluster profile with different name and associate the same in vSphere Lifecycle Manager image.
Version Affected: 5.1
• Issue 40–162621: Unable to downgrade the MX chassis firmware using OMIVV
Known issues
13