Release Notes

Version affected: 1.5 and later
Resolution/Workaround: Restart the appliance.
● Issue 28: Health Status is showing Warning for chassis while one or more Power supply is critical.
Description: The overall health information is displayed warning on summary page for VRTX chassis that has power supply in
critical state.
Version affected: All
Resolution/Workaround: Each power supply status is shown correctly as critical.
● Issue 29: Health Status is showing as Healthy for chassis while Storage status is Warning.
Description: The overall health information is displayed Healthy on summary page for VRTX chassis that has a storage
component as Warning.
Version affected: VRTX firmware version 2.0
Resolution/Workaround: Storage component health status is shown correctly as Warning.
● Issue 30: Blower information is showing as N/A for a chassis when a Blower is removed.
Description: Blower inventory information is displayed as N/A on the Monitor page for VRTX chassis when a Blower is
removed from a slot.
Version affected: 2.0 and later
Resolution/Workaround: You can see the fan inventory before the blower was removed.
● Issue 31: File type '.csv' is not be appended to the file, if the file name is anything other than "Export List".
Description: When we export any of the grid details from any OMIVVC pages (from IE9), the default File Name "ExportList"
is shown. If saved as is, it will be saved as "ExportList.csv". If the file name is changed to anything other than "Export List",
the file will be saved without any extension.
Opening the file will show all details in comma separated value format. Issue is just to append.
Version affected: M1000e firmware version 5.0
Resolution/Workaround:
1. Login to web client from IE 9, and export any grid value from pages like HW profile, Hypervisor profile, Host - firmware
inventory.
2. While saving, change the file name from ExportList to something else, say ExportList123.
3. Save the file with the file extension (in case the default name is changed.)
● Issue 32: I see a web communication error in the vCenter web client after changing the DNS settings in OpenManage
Integration for VMware vCenter?
Description: If you see any kind of web communication error in the vCenter web client while doing any OpenManage
Integration for VMWare vCenter related tasks after changing the DNS settings, clear the browser cache or logout and login
from the web client.
Version affected: 2.x and later
Resolution/Workaround: Clear the browser cache or log out and log in from the web client.
● Issue 33: OMIVV RPM Upgrade fails when Proxy is configured with Domain user authentication
Description: If OMIVV appliance is configured with proxy to reach the internet and proxy is authenticated using NTLM
authentication, then the RPM update will fail due to the issues in the underlying yum tool.
Version Affected: OMIVV 4.0 and above
Resolution/Workaround: Do Backup and Restore to update the OMIVV appliance.
● Issue 34: Sometimes OMIVV Inventory, Driver Update and Drift detection jobs for vSAN clusters runs for long time and
times out.
Description: If OMIVV appliance is configured to manage vSAN clusters, then sometimes the inventory and firmware update
(if driver included) and drift detection jobs runs for long time and eventually fails after time out. This is because the OMIVV
appliance fails to retrieve the thumbprint information from the registered vCenters in the last reboot. This thumbprint
information is used for collecting driver inventory.
Version Affected: OMIVV 4.2
Resolution: Keep the vCenters server instances up and reboot the OMIVV alliance.
7