Virtualization Manager 8.3 Release Notes
Released September 18, 2018
These release notes describe new features, improvements, and fixed issues in the Virtualization Manager (VMAN) 8.3 release. They also provide information about upgrades and describe workarounds for known issues.
New features and improvements
Virtualization Manager now monitors VMware vSAN cluster information. If you're using VMware vSAN, monitoring is enabled automatically once you upgrade to 8.3. vSAN information is surfaced in cluster details and other summary views.
vSAN monitoring comes with new widgets for use in your views and works with PerfStack so that you can compare vSAN data alongside your other collected metrics.
Examples of monitored information include the amount of storage used and available, whether or not a resynchronization is in progress for any virtual hosts, and how much storage space the de-duplication and compression feature is saving you.
This release adds support for basic container monitoring, supporting Docker, Kubernetes and Apache Mesos environments.
Three new object types are now available for creating Custom Properties in the Orion Web Console: Virtual Machines, Virtual Hosts, and Virtual Datastores.
Recommendations in Orion Maps
You can now see recommendations for VMAN-monitored elements in Orion Maps.
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.3 fixes the following issues:
Resources that would not load with the message "There was an error rendering with Problems" now load properly.
The MSMQ message queue should no longer become backed up during message processing.
VMAN will now prioritize mapping virtual machines and hosts to nodes on the same polling engine as a parent node of the virtual machine or host in question, preventing previously incorrect IP address mappings and addressing an issue where in some cases, VMAN monitoring for VMware ESX hosts and vCenters may have polled an incorrect host device due to incorrect IP address mapping.
|00055971||The "Virtual Disks and Related Storage Infrastructure" report now reports the correct drive letters in cases where there are a large number of virtual disks.|
|00058364||Capacity Planning Reports trend accuracy has been improved.|
|--||VSAN cluster tooltips no longer state "NOT FOUND We have no data for this item."|
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, Hardware Health polling may sometimes cause Orion database deadlocks.
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.
© 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.