Virtualization Manager 2020.2.5 Release Notes
Release date: March 25, 2021
These release notes describe new features, improvements, and fixed issues in Virtualization Manager (VMAN) 2020.2.5. They also provide information about upgrades and describe known issues.
New features and improvements in VMAN
Amazon Web Service (AWS) region updates: The following new regions are enabled by default for standard AWS accounts used in VMAN and other Orion Platform modules that support cloud monitoring:
- Africa (Cape Town)
- Asia Pacific (Hong Kong)
- Europe (Milan)
- Europe (Stockholm)
- Middle East (Bahrain)
The following new regions are also available, but disabled by default. To enable them, see this article.
- Asia Pacific (Osaka-Local)
- AWS GovCloud (US-East)
- China (Ningxia)
To learn about security improvements, see the Orion Platform 2020.2.5 Release Notes.
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.5 fixes the following issues:
Rapid database growth has been fixed.
|00333772, 00455459, 00640518, 00647207, 00700667,||JobResultsOutput contents are now properly cleaned up, preventing unnecessary disk space usage.|
|00607813, 00671890, 00628895||VM to Node mapping - nodes polled from different polling engines are now mapped correctly.|
|00641754, 00669574||Adding a Nutanix cluster for monitoring will no longer incorrectly be unable to connect to the cluster with given credentials when the given credentials are actually correct.|
|00595370||vCenter status will no longer stay stuck as 'Unknown' in the Virtual Center Details widget after the vCenter has been unmanaged and then managed again as a node.|
|00580411||Virtualization Storage Summary widgets for vCenters now show the correct number of vSAN hosts.|
|00699530||Some situations resulting in gaps in VSAN historical data have been fixed.|
|----||VMware Alarm Alerts now correctly display the name of associated hosts and datacenters.|
|00493269||Snapshot storage sizes shown for VMs are now more accurately determined.|
|00543112||VMWare Events now correctly continues logging when the primary poller fails over to an additional poller.|
See the Orion Platform 2020.2.5 release notes to see more Orion Platform fixed issues.
|Some VMAN and SQL server upgrade scenarios can cause Database configuration failed error during VMAN upgrade|
|Issue: When upgrading VMAN, a "Database configuration failed" error may occur for some VMAN and SQL server upgrade scenarios.|
|The "Top 10 VMs by Used Space" and "Top 10 VMs by Allocated Space" widgets incorrectly show some values as 0 instead of N/A|
|Issue: Instead of showing values as N/A, some widgets show some values incorrectly as 0.|
|Storage Usage of This Guest for VMs is always zero when VM is under standalone ESXi host|
|Issue: In the Virtual Machine Details widget, for VMs hosted on a standalone ESXi host, Storage Usage of This Guest for VMs is always shown as zero.|
|Adding a vCenter that has two or more ESXi hosts with the same hostname only adds one ESXi host to the Orion Platform|
|Issue: Adding two or more ESXi hosts with the same hostname only adds one ESXi host to the Orion Platform.|
|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.|
© 2021 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.