Virtualization Manager 8.4 Release Notes

Released March 12, 2019

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

VMAN 8.4 runs on Orion Platform version 2018.4 Hotfix 3.

New feature

VMware Events Monitoring Add-on

Available as an optional add-on to Virtualization Manager 8.4, VMware Events Monitoring gives you further connection to VMware based systems by giving you a list of VMware events includable in reports and available in widgets. In addition, you can set up rules to trigger standard and near real-time alerts from VMware Events.

While VMAN 8.4 requires SQL Server 2014 or later, the VMware Events Add-on has an additional requirement - your Orion server must have SQL Server 2016 SP1 or newer installed, with full text search support configured.

Learn more about the VMware Events Monitoring Add-on for VMAN 8.4

 

Health monitoring for virtual entities hosted on UCS chassis and blade servers

New in Orion Platform version 2018.4 Hotfix 3 is health monitoring for UCS chassis and blade servers. With VMAN, this includes health monitoring for virtual entities hosted on UCS chassis and blade servers.

Improvements

Capacity Planning - Multiple clusters

In VMAN 8.4, you can now run a Capacity Planning scenario for multiple clusters at once. Just select multiple clusters in the Capacity Planning wizard when setting up the scenario. A unique report will be generated for each cluster, and you can open multiple previously created reports at once.

 

Node status improvements

Improved consistency of visualization of node status for virtual entities. The node status visualization for virtual entities is now closer to the visualization of node status for network entities.

 

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.4 fixes the following issues:

CASE NUMBER DESCRIPTION
00199123

Appstack now shows the correct number of datastores for monitored virtual machines.

Known issues

Issue: vCenters can have polling issues when DHE is configured to use 2048-bit keys, showing status as "unknown".

Work-around: See this KB article.

 

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: A false "VM rebooted" alert may trigger after a VM is moved to another host by vMotion.

 

Issue: In some cases, Hardware health data may still be polled for vCenters, ESX hosts, or HyperV hosts that are no longer managed by VMAN, triggering alerts even for hosts that are no longer managed.

 

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: In some cases, total disk latency for virtual machines may be incorrectly calculated, showing a zero total disk latency.

 

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

 

End of Support

As of VMAN 8.4, because they have reached the end of VMware's extended support period, the following versions of vCenter Server are no longer officially supported for monitoring by VMAN:

  • vCenter Server 5.0
  • vCenter Server 5.1

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.