Virtualization Manager 2019.4 Release Notes
Released November 5, 2019
These release notes describe new features, improvements, and fixed issues in Virtualization Manager (VMAN) 2019.4. They also provide information about upgrades and describe workarounds for known issues.
New VMAN feature
Basic Nutanix monitoring support
In VMAN 2019.4, you can now add a Nutanix cluster and begin basic Nutanix monitoring.
See this topic for more information about what's supported in this release.
New Orion Platform features
New version numbering
Orion Platform products now follow a new, consistent naming structure. VMAN 2019.4 is part of the Orion Platform 2019.4 release.
Support for new languages
Orion Platform products are now localized to German and Japanese. You can choose the language during a fresh install of an Orion server.
The basic shared virtualization monitoring functionality available to NPM, SAM, and VMAN has been localized. However, the full-fledged VMAN product is not yet fully localized.
Orion Log Viewer
Orion Log Viewer is now included as an optional add-on during installation or upgrade for all Orion products. Orion Log Viewer was previously included with VMAN as part of the optional VMware Events Add-on.
Support for Azure SQL Managed Instance
You can now use the Azure SQL Managed Instance deployment option for your Orion database.
Orion Maps improvements
Orion Maps 2019.4 allows users to customize their maps with personalized images and enhancements, multi-select and reconfigure groups of entities on the canvas at one time, and quickly identify contextual relationships between entities from the entity library without leaving the Orion Maps Editor.
See the Orion Platform 2019.4 release notes for more details about new 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 2019.4 fixes the following issues:
Having multiple NICs on a monitored virtual machine that share the same IP address no longer causes a conflict.
|00246913||Performance issues where the Java Poller would max out CPU usage have been resolved.|
|00268269||Cases where Orion services would consume increasingly large amounts of memory have been resolved.|
|00336329||The Storage Summary resource no longer incorrectly shows html tags along with the actual LUN IDs/paths.|
|----||When creating a report for a datastore, adding in the depletion date column no longer causes an error.|
|00252695, 1076658, 1112219, 1188174||VMAN now polls the correct IP addresses for virtual machines with Network Load Balancing.|
|00315974||A configuration issue causing an unnecessary performance load on the SQL server has been resolved.|
|00309468||Capacity Planning reports will no longer fail in some cases with the error: Index was outside the bounds of the array.|
|00040659||Performing Network Discovery on a range of nodes containing Hyper-V hosts no longer causes VMs of the HyperV hosts to be added as nodes in the Orion Platform.|
|----||VMAN no longer has Unexpected Website Errors when date, time, or number formats are not set to a supported language in Windows Regional settings.|
See the Orion Platform 2019.4 release notes to see more Orion Platform fixed issues.
Issue: Hyper-V clusters that are monitored as part of a Nutanix cluster are not properly represented in the Nutanix device summary.
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.
Issue: Account limitations may not work correctly in some cases with VIM/VMAN groups.
Issue: Custom charts for VMAN clusters may sometimes show an irrelevant host in the chart legend.
Issue: Database maintenance can in some cases cause performance issues for VMAN polling engines.
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.
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.
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.
© 2019 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.