Virtualization Manager 2020.2 Release Notes
Release date: June 4, 2020
These release notes describe new features, improvements, and fixed issues in Virtualization Manager (VMAN) 2020.2. They also provide information about upgrades and describe workarounds for known issues.
New VMAN features
Expanded Nutanix monitoring support
In VMAN 2020.2, Nutanix monitoring functionality is expanded and no longer a technical preview.
Added Nutanix functionality:
- Storage statistics
- CPU/Memory/Network statistics
- Topology mapping (i.e. AppStack, Orion Maps)
- Basic management actions
FIPS compliance for VMware monitoring in VMAN
VMAN Orion polling for VMware vCenters, ESX hosts, and Nutanix is now FIPS-compliant.
As of VMAN 2020.2, to comply with Federal Information Processing Standards (FIPS), container monitoring is not supported if FIPS mode is enabled on the Orion server. If you added containers before enabling FIPS mode, delete containers and container services to stop polling, as described in the Orion Platform Administrator Guide.
Peaks in storage metrics
VMAN storage metrics in PerfStack have improved granularity, resulting in more accurate peaks.
Support for non-English Hyper-V hosts
VMAN now supports non-English Hyper-V hosts and no longer requires installing the English Language pack for Windows.
Orion Platform 2020.2 updates
- Performance enhancements for the Orion Web Console and Configuration Wizard.
- Customize Orion Maps with text boxes, labels, icons, styles, layouts, and more.
- Innovative new widgets for your custom summary dashboards.
- Enhanced volume status shows warning and critical statuses based on volume usage thresholds.
- Scripts to extract UI text from the Orion Web Console that you can translate and then deploy back to the Orion Web Console.
See the Orion Platform 2020.2 release notes for more details about updated Orion Platform features.
New user installation
For information about installing Virtualization Manager, see the Orion Installer and Virtualization Manager Installation Guide. After installation, use the VMAN Getting Started Guide to get started fast.
How to upgrade
For a detailed upgrade walkthrough, see the VMAN Upgrade Guide.
VMAN 2020.2 fixes the following issues:
|00459884, 00439671, 00397555||
VMware Events polling no longer fails with the error message "System.InvalidOperationException: The specified type was not recognized: name='HostSubSpecificationUpdateEvent'..."
|00346498||VMware ESX hosts are no longer incorrectly duplicated and monitored twice in some cases.|
|00465488, 00337166||Unmanaging a node now propagates the unmanaged status properly to associated VMware objects.|
|00338536||VMAN no longer incorrectly populates fields using the VM name instead of the host name for virtual machines in places where the host name is normally expected.|
|00436319, 00466913||The "Poll for VMware" option in the edit node dialog is available again.|
|00420149, 00428922, 00428417, 00450034, 00465863||The Virtual Machine Details page no longer shows the "Error While Rendering resource id ###" error message.|
|00471377, 00473201||VMAN no longer shows "There was an error while rendering resource with id #" when loading the Virtualization Storage Summary widget.|
|00384699||VMAN no longer has an IndexOutOfBoundsException in some cases relating to datastores.|
Identity mapping between Datastores and SRM FileShares now works correctly when the NAS Datastore is mounted to a host via hostname.
|00138629, 00327371||Database maintenance will no longer cause performance issues for VMAN polling engines in some cases.|
See the Orion Platform 2020.2 release notes to see more Orion Platform fixed issues.
|Upgrading from VMAN 8.3 with SQL server 2012 directly to VMAN 2020.2 causes loss of VSAN metric history|
|Issue: Proceeding to upgrade VMAN 8.3 to VMAN 2020.2 while your Orion database is running on an instance of SQL server 2012 will cause a loss of VSAN metric history.|
|Incorrect representation in Nutanix device summary of Hyper-V clusters monitored as part of a Nutanix cluster|
|Issue: Hyper-V clusters that are monitored as part of a Nutanix cluster are not properly represented in the Nutanix device summary.|
|Incorrect AppStack data for vCenters|
|Issue: AppStack data for a vCenter may in some cases be displayed incorrectly when the vCenter is deployed as a virtual machine under an ESXi host that is monitored by the same vCenter.|
|Account limitations may not work with VIM/VMAN groups|
|Issue: Account limitations may not work correctly in some cases with VIM/VMAN groups.|
|Custom charts show irrelevant host|
|Issue: Custom charts for VMAN clusters may sometimes show an irrelevant host in the chart legend.|
|Incorrect host in Related Node column of Cluster Memory Utilization alerts|
|Issue: Cluster Memory Utilization alerts may sometimes show an incorrect host in the Related Node column.|
|VMs with RDM disks report does not show VMs with RDM disks|
|Issue: The report "VMs with RDM disks" does not correctly populate with VMs with RDM disks.|
|Performance issues with a single shared datastore|
|Issue: A single datastore being shared among many vCenters and/or hosts can cause performance issues during polling.|
|Predicted Datastore Space Depletion widget, disappearing datastores|
|Issue: Datastores sometimes randomly disappear from the Predicted Datastore Space Depletion widget|
|Incorrect status shown for vCenter|
|Issue: If VMAN's polling process has failed for any reason, the last known status for a vCenter is shown in VMAN. This could result in a normal, green status being shown for a vCenter when it shouldn't.|
|Dashboards in the VMAN appliance may disappear|
|Issue: Dashboards in the VMAN appliance may disappear after migrating from an older (pre 7.1) appliance to a newer appliance (8.0 or newer).|
|Work-around: See this KB article.|
|Unable to connect error in VMAN appliance|
|Issue: Enabling Collection Schedules for a datasource may result in an "unable to connect" error in cases where a large number of credentials are stored in the VMAN appliance.|
|Currently running trend reports aren't shown in the "Report Schedules" tab in the VMAN appliance|
|Issue: Currently running trend reports aren't shown in the "Report Schedules" tab. However, reports are still successfully executed and available for download in the "Report Results" tab once completed.|
© 2020 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.