Virtualization Manager 8.2.1 Release Notes
These release notes describe new features, improvements, and fixed issues in the Virtualization Manager (VMAN) 8.2.1 release. They also provide information about upgrades and describe workarounds for known issues.
SolarWinds Orion Installer for installing Orion Platform 2018.2 already includes the Orion Platform 2018.2 Hotfix 1.
New wizard for adding virtual objects for monitoring
Adding new vCenters, Hyper-V hosts, and standalone ESX hosts for monitoring is now easier. The new wizard will walk you through adding a virtual object for monitoring step by step.
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 8.2.1 fixes the following issues:
Reboot alerts that weren't working properly now work again.
SQL collector processes will no longer become locked.
Migration of virtual machines will no longer fail in cases where there are more than 12 hosts available for migration.
|00034125||The "Top 10 VMs by Snapshot Disk Usage" report's snapshot column now accurately reports snapshot disk usage.|
Issue: Some resources may have trouble loading under some circumstances, resulting in an error message: "There was an error rendering with problems".
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, VMAN monitoring for VMware ESX hosts and vCenters may poll an incorrect host device due to incorrect IP address mapping.
Issue: The "Virtual Disks and Related Storage Infrastructure" report can report incorrect drive letters related to a virtual disk when a monitored virtual machine has a large number of virtual disks.
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 a 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.
© 2018 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.