Release Notes

Version Affected: 4.3 and later
● Issue 20: 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 21: 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 22: 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 23–156807: Invalid task name might be displayed for OMIVV tasks under VMware Task Console.
Resolution: None
Version Affected: 4.3.1 and later
● Issue 24–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 25–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 26–109760: Proactive HA-related features are not working after modifying user credentials in OMIVV Dell EMC
administration console.
12
Known issues