Virtualization Manager 8.5 Release Notes

Last modified June 6, 2019

These release notes describe new features, improvements, and fixed issues in Virtualization Manager (VMAN) 8.5. They also provide information about upgrades and describe workarounds for known issues.

VMAN Improvement

Monitoring Virtual Disk Statistics

With VMAN 8.5, you can now monitor the IOPs, throughput and latency metrics at a virtual disk granularity.

See the VMAN 8.5 Administrator Guide (p. 63) for detailed information.

New Orion Platform features

Support for Azure SQL Database

In VMAN 8.5 and other Orion Platform 2019.2 products, you can now use Azure SQL Database to host your Orion SQL database and VMware Events Add-on database.

Learn more about deploying SolarWinds Orion Platform products to Microsoft Azure

Support for SQL Server 2019

Orion Platform products, including VMAN, now support SQL Server 2019.

Node status improvements

Customize what should be reflected in a node status - status of child entities, thresholds, or more.

Orion Maps enhancements

  • Build and customize map layouts using the new map editor.
  • Place Orion Maps on any dashboard or view using the Orion Map widget.

See the Orion Platform 2019.2 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.

Fixed issues

VMAN 8.5 fixes the following issues:

CASE NUMBER DESCRIPTION
1336793

VMAN will no longer produce false "VM rebooted" alerts whenever a VMware virtual machine migrates to another host through VMotion.

00068359 Hardware Health is no longer polled on hosts that are no longer being managed in Orion.
00124661 The "latency total" field for charts for VMware datastores is now correctly populated with data.
00168930 Temperature graphs for Hardware Health now correctly show data in cases where data was missing.
00165659 Cases where AppStack would fail to fully load, resulting in a missing AppStack, have been resolved.
00246359, 00230974 The Operational state shown for Hyper-V virtual machines will no longer report as "? Unknown" and will show as either "Running" or "Not Running".
00235117 Duplicate recommendations should no longer appear.
00099398, 00261536 Database maintenance should no longer cause missing historical data in cases where monitored clusters do not belong to a data center.
00256210

Performance issues for VIM/VMAN polling causing database deadlocking have been resolved.

00293223, 00296495, 00306493, 00304285, 00287658, 00296864, 00307941

VMAN now supports 2048-bit DHE keys, resolving polling issues that occurred when DHE is configured to use 2048-bit keys.

See the Orion Platform 2019.2 release notes to see more Orion Platform fixed issues.

Known issues

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: In some cases, performing Network Discovery on a range of nodes containing HyperV hosts may also result in child VMs of the HyperV hosts also being added as nodes in the Orion Platform.

 

Issue: Having multiple NICs on a monitored virtual machine that share the same IP address can cause a conflict, preventing configuration information about that virtual machine from being updated correctly in the Orion database.

Work-around: See this KB article.

 

Issue: The VMAN Java poller for Hyper-V devices may sometimes consume high amounts of CPU%.

Work-around: See this KB article.

 

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: 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.

Deprecation notice

The VMAN appliance is now deprecated. The appliance will no longer receive new feature updates and will eventually reach end of support.

If you're a VMAN appliance user, you should make plans to retire the appliance and move fully over to VMAN in the Orion Platform to continue to benefit from VMAN's latest features and newest developments.

Legal notices

© 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.