Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

Home > Success Center > Virtualization Manager (VMAN) > Virtualization Manager 7.1 release notes

Virtualization Manager 7.1 release notes

 

Last updated: 3-14-2017

These release notes describe the new features, improvements, and fixed issues in this release. They also provide information about upgrades and describe work-arounds for known issues.

For detailed system requirements, see recommeneded system requirements for VMAN 7.1 and VIM 7.1.

New features and improvements

Read this section for descriptions of the new features and improvements VMAN and VIM offer in this release.

For previous release information, see VMAN 7.0 Release Notes.

Recommendations enhancements

When VMAN identifies a way to optimize VM resources for active and potential issues, it makes a recommendation for one click optimization. Recommendations display in the Orion Web Console with a description for optimizing your network, and provides a series of steps you can apply immediately with a button click or schedule at a later time. This release includes the following enhancements:

  • Policy support for VM, host, cluster, and datastores

» Read more about Recommendations

Cloud Infrastructure Monitoring

Cloud Infrastructure Monitoring provides visibility into your AWS cloud infrastructure including EC2 cloud instances and attached EBS volumes. This feature completes the Orion tools you need to monitor and administer hybrid environments. With access to your cloud services account, SAM polls cloud service APIs for cloud metrics and status. This data aggregates and displays through the Orion Web Console to monitor, manage, and troubleshoot issues in your cloud environment.

  • Discover your EC2 cloud instances and EBS volumes in your AWS cloud infrastructure
  • Automatically discover and monitor new cloud instances when launched from your cloud account
  • Provide a consolidated view for cloud, hybrid, and on-premises systems
  • Configure cloud alerts for cloud issues including AWS throttling, AWS exceeded limits, Orion cloud and global thresholds exceeded, polling issues, and health status
  • Manage global cloud monitoring threshold settings to indicate warning and critical thresholds
  • Poll for application and OS metrics on cloud instances using  application monitors and templates

» Read more about Cloud Infrastructure Monitoring.

Performance Analysis charts (PerfStack)

Use the Performance Analysis (PerfStack™) dashboard to get both broad and in-depth visibility into your  environment by correlating disparate historical data points across your infrastructure, including on-premise, cloud, and hybrid environments in easy to read charts. Click My Dashboards > Home > Performance Analysis to get started correlating and analyzing data collected by your SolarWinds Orion solution to troubleshoot issues, identify root causes of intermittent issues, and make data-driven decisions on infrastructure changes.

» Read more about these changes

Global Thresholds for Alerts

Alerts created through the Virtual Infrastructure Monitor (VIM) or integrated Orion Platform trigger using Global Thresholds. To modify and manage these threshold defaults in the Orion Web Console, select Settings > All Settings and locate Thresholds & Polling. Select Virtualization Thresholds to modify virtual global thresholds. Select Orion Thresholds to modify global Orion thresholds.

The default for warnings is 80%, different than previous thresholds of 70%.

Native SSL support for the Orion Web Console

Seamlessly bind SSL certificates to the Orion Web Console and enable HTTPS connections using the Configuration Wizard. The Configuration Wizard scans the Orion server for valid SSL certificates that you can choose for the binding, or you can generate a self-signed certificate on the fly.

Other improvements

  • Support VMware vCenter 6.5
  • Support Microsoft Hyper-V Server 2016
  • Localization for Japanese and German enhanced for the Orion Web Console
  • Use the Web-based SSH client when FIPS is enabled.
  • VMAN 7.1 appliance has an updated kernel and packages with new security updates including 'Dirty Cow' vulnerability (reference ID 'CVE-2016-5195')
  • Use the Critical node status to trigger an alert or filter data in a report. 
  • Set a custom node status to Critical or Warning using an alert action. 
  • Use the Web-based SSH client when FIPS is enabled.

New customer installation

For information about installing Virtualization Manager, see the Virtualization Manager Installation Guide and the VMAN Getting Started Guide.

When installing the VMAN 7.1 appliance on VMware vSphere 6.5 using the VMAN .ova, you need to upgrade the vSphere hardware version to the latest version. See this vSphere article for version details. You may receive errors until the hardware version is updated.

Before you upgrade!

If you are upgrading from a previous version, be aware of the following considerations: 

  • When upgrading or installing VMAN 7.0 and 7.1 on VMware vSphere 6.5 using the VMAN .ova, you need to upgrade the vSphere hardware version to the latest version. See this vSphere article for version details. You may receive errors until the hardware version is updated.
  • After integrated VMAN 7.1/VIM 7.1, future releases will no longer support Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2. Integrated VMAN 7.1/VIM 7.1 currently supports these versions. SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience. For more information, see End of support notices.
  • When upgrading to integrated VMAN 7.1, if you added a site binding to a host name before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN). See this article.
  • When upgrading to integrated VMAN 7.1/VIM 7.1 with custom menus, you can not see the Performance Dashboard link in the menu. For details, see this article.
  • VMAN 7.1 requires Orion Platform 2016.2 or 2017.1. VIM 7.0 released with VMAN 7.0 includes Orion 2017.1. For full VMAN and VIM compatible products, see this article.
  • VMAN 7.0 and later no longer supports the VMware vSphere plug in.
  • For VMAN integrated with the Orion Web Console, you need to upgrade to VIM 7.1. Regardless of your installed Orion product version (such as NPM 12.1 or SAM 6.4), you should run the VIM 7.1 upgrade. This upgrade includes additional feature additions and fixed issues.

    You can find the VIM 7.1 installer zipped with the full VMAN 7.1 download in the Customer Portal (not a separate download).

  • Be aware that due to changes in group limitations in the Orion Platform, there was a change in the behavior of  group limitations applied on virtualization entities. The new behavior is more restrictive than the previous one.

    If there are entities of different types in one group (Clusters, Hosts, VMs), their hierarchy is taken into consideration. This means that, for example, hosts will be visible if they are not restricted by the parent cluster, and the same applies for VMs and their parent hosts. The visible subset of the environment depends on an intersection of limitations applied on different virtualization entity types.

    Consider the new default behavior when you configure group limitations in Orion.

  • If you have written your own code for the Orion Web Console, such as changing SolarWinds .css files or adding .js files, it may be overwritten with the upgrade. You can learn more about custom code in this article.
  • If you have NPM installed, make sure you have the latest version of NPM installed. NPM includes platform features to support all Orion platforms.

How to upgrade

Use the following resources for planning and upgrading:

Fixed issues

VMAN 7.1 fixes the following issues.

Case number Description
1093715, 1077932

Resolved issue with Configuration Wizard and properly deploying the Recommendations engine during VIM installation or upgrade.

1088199

Resolve issue with polling ESXi 6.5 and the Virtual Infrastructure Monitor (VIM).

1072184

Resolved issue with VMware nodes showing unknown status when polling with Orion agents.

1081005

Resoved issue to properly handle alert limitation categories with the All Active Virtualization Alerts resource.

Orion Platform 2017.1 fixes the following issues.

Case number Description
24135

A CPU utilization issue on multi-core nodes running Microsoft® Windows Server® 2008 R2 when using WMI or the agent polling method.

1083016, 1101815, 1100735, 

1077051, 

1085402, 1072560, 1098762, 1105707

Event resources cannot load for accounts with an alert limitation.

1031328, 1084354, 1076612, 1052668, 1061657, 1064635, 1106428, 1029471, 1037482, 1081073, 1090684, 1081073

Windows group accounts can still view hidden menu items.

1047577, 1052608, 1004357, 1021860, 1059768, 1085270, 1093656, 1108072, 1004525, 1017004, 1056172, 1064162, 1104495, 1093738

Custom time periods return incorrect results

1080679, 1104953, 1031225, 1041708, 1009688, 1007586, 1074064, 1096297, 1085714, 1007856

The Manage Alerts page either constantly refreshes or becomes unresponsive.

1009412, 1076919, 1099060, 923828, 1091945, 1088802, 911654, 911553

Active Alerts page displays the wrong name if you edited the node while an alert was active against the node.

1042185, 1067502, 1068600, 1091904, 1063084, 1069179, 1040947, 1033595, 1080742, 1086148, 1095806, 1061524

Performance degrades when there are a significant number of dependencies and may not show in the list of managed dependencies.

1018900, 1082887, 1093696

Cannot remove nodes from the WorldMap resource.

1089390

Excessive database queries to sw_GetSettingsCurrentValue.

1044217, 1041096

Syslog messages are displayed for the incorrect node when the node has multiple IP addresses or if there are duplicated IP addresses assigned to different polling engines.

1017671

Agent polling stops for applications due to a memory leak.

1084968

SNMP traps cannot be forwarded due to incorrect MIB file.

903330, 1070593

Automatic dependencies are not created if the root node is included in a cluster.

1007751, 1076260

Network discoveries time out due to the JobEngineWorker2 process crashing.

1067984, 1065390, 1080128, 1083238

Alerts do not display in the Manage Alerts page.

1059342

Cannot change Volume Properties when the warning threshold is greater than the critical threshold in the Polling Setting page.

1081793

The Upgrade Buddy tool sends false alerts during upgrades.

1080766, 1009082, 1019843, 1042578

Nodes using SNMPv3 credentials are duplicated during an upgrade.

1079813, 1061559

The Custom Property Editor modifies all objects instead of the selected objects.

1079825, 942110, 1068317, 971740, 1034431

The Orion Web Console is slow or alerts do not display due to the SolarWinds Information Service process using up to 4 GB before timing out.

1070330, 1071035, 1074365, 1070330, 1074365

Dependencies are missing from the Orion Web Console after an upgrade.

1068610

Expanding groups in the All Groups resource takes approximately 10 seconds to expand each group.

1068892, 1068879, 1067676

The Web-based SSH client does not accept user names with special characters in some browsers.

1011854, 1063374, 878151, 1036003, 1048166, 807337

Trigger conditions are missing and you cannot edit some alerts after an upgrade.

1030540, 1044126, 1068031

Network Atlas and the Orion Web Console are slow to load or stop working due to the SolarWinds Information Service using excessive amounts of memory.

1062805

The Orion-Detailed-Alert trap template contains deprecated variables.

1054525

The DiscoveredItems variable does not resolve.

1059844, 1020832, 1018423

The Log Alert to File action does not appear to work due to an encoding change after an upgrade.

1055891

The Last XX Syslog Messages resources cannot be filtered by a custom property.

1060515

The alert history table includes entries outside of the retention period.

1047190, 1059644

Port 5672 accepts unencrypted AMQP connections.

1010691, 1035604, 1027737, 1046224, 1038711, 1049203, 1052486

Receive "Error querying ServiceNow Instance Instance can be offline or not properly configured" when creating a ServiceNow alert action.

1023811

Network Atlas does not load.

1062326, 1052508

ServiceNow fields display the wrong language.

1039964

ServiceNow integration does not support integer columns.

1029447

The Managed Nodes resource does not load when the vend contains a single quote.

1031243, 1042023

When you duplicate a scheduled report, the report email is sent for each duplicated report.

1025084

Custom node thresholds does not affect how the threshold displays in tooltips.

1012913, 1014784

Topology calculations do not complete and may not display topologies in Network Atlas.

1029582

Custom Charts do not retain changes to the title or subtitle.

1008665, 1015965

Receive a website error when viewing the Transaction Details page and Step Details page when there are alert resources included.

1014191

Users with node limitations cannot add SNMPv3 nodes.

 

1029811

The All Groups resource collapses expanded groups.

964659

Syslog message resources do not apply filters.

1018353

The All Nodes Tree resource does not load if there are NULL values in the node data.

990217

The Scheduled Discovery Results cannot be viewed after the first 1000 results and cannot be grouped by date found.

982434

Cannot authenticate SMTP credentials when special characters are included in the password.

943161, 875757, 809390

Cannot list resources on a device when TLS 1.2 is enforced and the Orion Web Console may be blank.

1085116

Agents do not automatically restart and return a "Job failed to execute" error on applications polled with agents.

1062990

Linux-based computers with multiple volumes mounted to the same mount-point do not resolve correctly.

998331

Configured agents cloned from a Gold Master Image do not register with the Orion server.

1079332

When a service is listed in the registry or whitelisted, but not present on a computer that is highly available, the computer fails over to the backup computer and may constantly failover or not start.

901072, 1074013, 1028900, 1007379, 1029938, 1043849, 1051019, 1063406, 1078861, 1103781, 

1107207, 1107944, 1134456, 1054772, 1123866, 1007379, 1070626, 1074013, 1081866, 1079150, 1116768, 1125380, 1086292, 1094598, 1100915, 1024863, 1063406, 1007379, 1043849, 1078861, 1109430

The SolarWinds Job Engine crashes with high resource utilization errors.

Known issues

VMAN appliance cannot start on VMware vSphere 6.5

Issue: The VMAN 7.1 appliance cannot start when deployed on VMware vSphere 6.5 due to the virtual hardware version of the appliance.

Work-around: After deploying the VMAN 7.1 appliance on a VMware vSphere 6.5, update the VM compatibility for the server:

  1. Through the vSphere options in VMware vCenter, selection Compatibility > Upgrade VM Compatibility.
  2. Selet a Compatible option. SolarWinds recommends ESXi 6.5 and later.
  3. Click Ok.

The VMAN appliance should properly start up on the VM. For more information, see VMAN does not startup on vSphere 6.5 due to unsupported guest OS.

TLS 1.2 support on Additional Polling Engines and Additional Websites

Issue: Cannot install Additional Polling Engines (APE) or Additional Websites (AWS) when the main polling engine uses TLS 1.2.

Work-around: Revert the main polling engine to an earlier version of TLS to install the APE or AWS. Once the APE or AWS is fully installed, you can re-disable SSLv3, TLS 1.0, and TLS 1.1 on your main polling engine.

End of support

For information about supported versions of SolarWinds products, see this article.

This version deprecates the following hardware, software, and features. 

Deprecation indicates that the feature should be avoided. Deprecated features remain in the software, but will be removed in a future release. Customizations applied to a deprecated feature may not be migrated if a new feature replaces the deprecated one.

Type Deprecation
Microsoft SQL Server

Support for SQL 2008 and 2008 R2 is deprecated as of this release.

You can install on SQL 2008 and 2008 R2 for this release. Future releases will no longer support using SQL 2008 or 2008 R2 as your database server.

SolarWinds recommends that you upgrade directly to SQL 2016 at your earliest convenience.

Microsoft Windows Server

Support for Windows Server 2008 R2 is deprecated as of this release.

You can install on Windows Server 2008 R2 for this release. Future releases will no longer support installing on Windows Server 2008 R2, though you can continue to monitor computers running Windows Server 2008 R2.

SolarWinds recommends that you upgrade to Windows Server 2012, 2012 R2, or 2016 at your earliest convenience.

Export to PDF feature The Export to PDF button on dashboards is deprecated as of this release and will be removed in a future release. SolarWinds recommends that you use the Save as PDF functionality built into your browser.
Alert Manager The deprecated Alert Manager application has been removed from the Orion Platform. Use the web-based Alert Manager through the Orion Web Console to create and manage alerts.
All Active Alerts resource The current  All Active Alerts resources is deprecated as of this release. The resource will be replaced with a new, enhanced version in a future release.

 

Legal notices

© 2017 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 and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. 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 and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.

 

 

 

 

Last modified
09:16, 14 Mar 2017

Tags

Classifications

Public