Virtualization Manager 2020.2.6 Release Notes
Release date: July 15, 2021
These release notes describe the new features, improvements, and fixed issues in Virtualization Manager 2020.2.6. They also provide information about upgrades and describe workarounds for known issues.
New features and improvements in VMAN
VMAN 2020.2.6 offers new features and improvements compared to previous releases of VMAN.
See also the Orion Platform 2020.2.6 Release Notes.
VMAN now has visibility into your VMware tags and which objects you've assigned them to in vSphere. Bring the organization you've already created with VMware tags over to VMAN: Create custom tables, widgets, reports, and alerts, and even run chargeback reports, all utilizing VMware tags.
Nutanix bulk registration
Add multiple Nutanix clusters for monitoring all at the same time by just adding a Nutanix Prism Central host. All Nutanix clusters associated with the Prism Central host will now be added for monitoring automatically.
Chargeback report improvements
Improved chargeback reports can now be made based on VMware tags and any custom properties you have created and assigned to monitored clusters or hosts.
Container monitoring improvements
Secure container-related data with a new type of Orion Platform credential — SolarWinds Tokens. Other improvements include a simplified deployment flow, the ability to edit container services, and improved handling of short-lived, ephemeral containers, as described in the Orion Platform Administrator Guide.
If upgrading from an earlier version, update all existing container services to use SolarWinds Tokens instead of Orion credentials. Otherwise, any existing container monitoring will stop.
- Some improvements have been made to the Add Node wizard for adding virtual entities.
- The version of OpenJDK included with VMAN has been updated to version 16, the latest available version as of this release.
New customer 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.
Fixed issues in VMAN 2020.2.6
VMAN 2020.2.6 fixes the following issues:
Version 7.0.2 vCenters and ESXi hosts can now be properly added for monitoring and gather metrics as expected no longer showing status unknown.
|00791630||Links utilizing target="_blank" have been corrected to no longer use target="_blank".|
|00783503||ERROR SolarWinds.Orion.VIM.WebApi.Tooltips.Dal.TooltipsDal will no longer incorrectly appear in the ApoloWebApi.log after hovering the mouse over a monitored vCenter or host in the Orion Web Console.|
|00323934, 00737551||Datastores no longer randomly disappear from the Predicted Datastore Space Depletion widget.|
|00645366, 00740546||Adding a vCenter that has 2 or more ESXi hosts with the same DNSHostName now shows the ESXi hosts under the correct vCenter and with the correct status.|
|00632748, 00699936||Views that contain the Resource Utilization widget will no longer cause an error when the page is loaded without an active VMAN license (full or trial).|
|----||The "Storage Usage of this Guest" value under virtual machine details for monitored standalone ESXi hosts is now populated correctly and no longer always zero.|
|00609105||Database maintenance for very large amounts of orphaned VMs no longer causes the database's SQL server to crash.|
|00573060||The Top 10 VMs by used space and Top 10 VMs by allocated space now no longer show VMs that have larger than 0 used space and capacity.|
|00424192||When VMAN is used with EOC, Virtual Machines now appear in EOC as "Virtual Machines" instead of "Virtual Instances".|
|00339341||VMAN logs no longer stop collecting.|
|00169006||Alerts on the node details page are now shown in the correct time zone.|
See also the Orion Platform 2020.2.6 Release Notes.
|Incorrect size shown for VMware VM snapshots|
|Issue: Pages and reports that show snapshot sizes for VMware VMs can sometimes be incorrect|
|"Triggered by Event" widget update delay|
|Issue: The "Triggered by Event" widget may in some cases not show the latest event that triggered the alert.|
|Monitoring a VMWare vCenter via ROP (Remote Orion Poller) shows unknown status|
|Issue: Unknown status can be incorrectly shown when monitoring a VMWare vCenter through a Remote Orion Poller.|
|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.
|Cluster Memory Utilization alerts sometimes show incorrect host|
Issue: Incorrect hosts, even ones not in the relevant cluster, can sometimes be shown in Cluster Memory Utilization alerts.
|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.