Virtualization Manager 2020.2.1 Release Notes
Release date: August 25, 2020
These release notes describe new features, improvements, and fixed issues in Virtualization Manager (VMAN) 2020.2.1. They also provide information about upgrades and describe known issues.
New VMAN features
In VMAN 2020.2.1, VMAN in the Orion Platform now delivers chargeback reporting so IT groups can gain a better understanding of the costs associated with their virtual infrastructure. VMAN allows IT to specify reporting based on hosts or clusters, choose a given timeframe, and deliver an accounting of their costs based on CPU, Memory, Storage, and vCPU usage.
Nutanix custom properties
Nutanix clusters, hosts, and VMs are now available for use in custom properties for alerting and reporting.
Orion Platform 2020.2.1 updates
See the Orion Platform 2020.2.1 release notes for 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.1 fixes the following issues:
In cases where multiple hosts with the same name are added, VMAN now adds all the hosts with duplicate names instead of just the first host processed.
|00563025||Upgrading from VMAN 2019.4 to VMAN 2020.2.1 with the Orion database hosted as an Azure database will no longer cause _ERROR OrionDatabaseCreator - System.Data.SqlClient.SqlException (0x80131904).|
|00557211||Alerts in VMAN triggering from VMware Alarms now have a proper identifying display name for cluster objects.|
|----||Hyper-V clusters that are monitored as part of a Nutanix cluster are now properly represented in the Nutanix device summary.|
|00468816||Instances where adding a Nutanix cluster for monitoring has actually failed will no longer incorrectly result in a message that the Nutanix cluster was successfully added.|
|00291401, 00284310, 00331890, 00217434, 00334836||A new out of box alert has been included with VMAN that will warn users when a VM has multiple snapshots, which can affect polling performance.|
|00046423, 00042414, 00049145, 00260831||You can now filter out service tags for chassis to correct polling in situations where the same service tag exists for both a chassis and an ESX host. See this KB for more details.|
|00387915||The "VMs with RDM Disks" report now correctly reports VMs with RDM disks.|
|00448922, 00437676||The "other" sensor group is now shown for Hardware Health for vCenters and ESXi hosts.|
|00432655||The Virtual Machine Details page now supports and correctly displays NOC mode.|
|00554121, 00566643, 00567684, 00584134, 00573896, 00575613, 00595126, 00582238, 00567989, 00571627, 00573412||Users accessing Orion through Windows Authentication can now add Nutanix clusters and standalone HyperV or VMware hosts for monitoring.|
See the Orion Platform 2020.2.1 release notes to see more Orion Platform fixed issues.
|Upgrading from VMAN 8.3 with SQL server 2012 directly to VMAN 2020.2.1 causes loss of VSAN metric history|
|Issue: Proceeding to upgrade VMAN 8.3 to VMAN 2020.2.1 while your Orion database is running on an instance of SQL server 2012 will cause a loss of VSAN metric history.|
|Nutanix devices are not supported for Chargeback reports|
|Issue: Chargeback reports cannot be generated for Nutanix clusters or AHV hosts.|
|German language environments are not supported for Chargeback reports|
|Issue: Chargeback reports cannot be generated for VMAN instances in a German language environment.|
|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.|
|Gray vCenter status and System.OutOfMemoryException in logs|
|Issue: In some cases, polling a vCenter may fail, resulting in a gray vCenter status. Recorded in VMAN logs is the message: "Failed to allocate a managed memory buffer of 1073741824 bytes. The amount of available memory may be low. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown".|
|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|
|VMAN polling engines performance issues after Database maintenance|
|Issue: Database maintenance can in some cases cause performance issues for VMAN polling engines.|
|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.|
End of life, end of support, and deprecation notices
The legacy VMAN appliance has reached end of life and is no longer supported. Integrating VMAN in the Orion Platform with a legacy appliance is no longer possible.
© 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.