Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Virtualization Manager (VMAN) > VMAN 7.2 Release Notes

VMAN 7.2 Release Notes

Last updated: 6-1-2017

These release notes detail the new release of VMAN 7.2 appliance for CentOS 6 migration. For all new features, fixed issues, and known issues, use VMAN 7.1 Release Notes.

For full product release notes, additional features, and resolved issues, see VMAN 7.1 Release Notes.

For detailed system requirements, see recommended 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 additional new features, see VMAN 7.1 Release Notes.

CentOS support for VMAN appliance

VMAN 7.2 provides a new appliance based on CentOS 6. Previous VMAN appliances used CentOS 5. To update to the new appliance, you will need to migrate to a new VMAN 7.2 deployment on a new VM. For full details and instructions, please see VMAN 7.1 to 7.2 appliance migration for CentOS 6.

Deprecation Notice from Red Hat: As of March 31, 2017, CentOS 5 was deprecated by Red Hat. For information on CentOS versions and lifecycle, see Red Hat Enterprise Linux Life Cycle.

To upgrade, you must migrate to a new VMAN 7.2 deployment. See the VMAN 7.1 to 7.2 appliance migration guide for details.

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

VMAN 7.2 supports the following hotfixes available through the Customer Portal:

VMAN 7.2 includes VMAN 7.1 HotFix 1. The downloaded installation files includes VMAN 7.2 appliance and VIM 7.1 (your Orion Platform install). If you have SAM 6.4 installed with VMAN, you do not need to install VIM 7.1.

Before you upgrade!

Important: You cannot upgrade the VMAN appliance from a previous version to 7.2. You must migrate to the VMAN 7.2 appliance.

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

  • When upgrading or installing VMAN 7.0, 7.1, and 7.2 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 and 7.2/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 and 7.2/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 and 7.2, 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 and 7.2/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 and 7.2 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:

Known issues

The following issues are known issues for this release.

Appliance version may display incorrectly

Issue: After completing the transplanting of the data disk for VMAN 7.2 appliance, you will see an incorrect version in License Information module, Help module, the SolarWinds Management tab, and Application Version field.

Work-Around: The correct version displays in the System tab, Appliance Version field, and the master.log. A resolution is in consideration.

Deprecation notices

CentOS 5 is no longer supported by Red Hat. As of March 31, 2017, CentOS 5 was deprecated by VMware. For information on CentOS versions and lifecycle, see Red Hat Exterprise Linux Life Cycle.

SolarWinds strongly recommends upgrading. VMAN 7.1 and earlier appliances are on a deprecated version of CentOS 5. SolarWinds can continue providing updates for SolarWinds features for older VMAN appliance versions. However, SolarWinds cannot provide vulnerability and security upgrades for CentOS 5 based appliances due to Red Hat deprecation.

© 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
12:49, 3 Aug 2017

Tags

Classifications

Public