Release Notes

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 notices 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 39–160776: Unable to associate the cluster profile that is deleted and created using the same name in vSphere
Lifecycle Manager.
This issue occurs when the cluster profile that is associated with vSphere Lifecycle Manager image is deleted and if you
create the 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–109760: Proactive HA-related features are working after modifying user credentials in OMIVV Dell EMC
administration console.
If the credentials are modified using the OMIVV Dell EMC administration console after registering the OMIVV to a vCenter,
the Proactive HA-related features will not function as expected.
Resolution: If you are using the Proactive HA feature along with OMIVV, do not modify the registered user credentials. If the
credentials require modification, unregister the old credentials and register by using the new credentials.
Version affected: 4.3 and later
● Issue 41–158524: vSphere Lifecycle Manager shows firmware version for PCIe SSD or NVMe SSD as blank for vSAN
cluster.
When the Hardware compatibility is triggered, vSphere Lifecycle Manager does not validate PCIe SSD or NVMe SSD. If
these components exist in the server, firmware version is shown as blank because vSphere Lifecycle Manager is not
considering OMIVV output for these components.
Resolution:
○ See that the firmware versions drifted in vSphere Lifecycle Manager firmware compliance page and compare the same
with vSAN HCL supported firmware.
○ For vSAN cluster, see the supported or recommended firmware in health service.
Version affected: 5.1 and later
● Issue 42–170114: During auto discovery, OMIVV allows you to apply lower complex password to iDRAC even if the password
complexity level is set to high in iDRAC.
This issue occurs when you set the password complexity as high in iDRAC and initiate auto discovery in OMIVV. During Auto
discovery, iDRAC takes the simple password set on the Deployment Credentials page of OMIVV even if the password
complexity is set high at iDRAC.
Resolution: Perform any of the following:
1. Update the password at Deployment Credentials with complexity meeting the level set at iDRAC.
2. Update the password while deploying the System Profile in OMIVV.
Version affected: 5.0 and later
● Issue 43–176707: The health status of the server node having storage sled in a chassis is listed twice on the Chassis
Health page.
The health status of a server node having storage sled in a chassis is listed twice in the Storage and Server sections of
Chassis Health page. The corresponding slot health is shown as Unknown in the Server section.
14
Known issues