Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN Upgrade Guide

VMAN Upgrade Guide

Updated: 6-1-2017 | SolarWinds Upgrade Guide

Supports: VMAN 7.2 and earlier

This guide walks you through upgrading only your VMAN product. We include checklists to prepare and complete your upgrades, gotchas, and troubleshooting steps.

Important VMAN 7.2 appliance: You cannot upgrade the VMAN appliance from a previous version to 7.2. You must migrate to the VMAN 7.2 appliance. Migration is supported for previous VMAN appliance versions including 6.3.2, 7.0, and 7.1.

Upgrading multiple products? See our SolarWinds multiple products upgrade guide!

This video walks through installing VMAN, integrating with the Orion Platform or VIM, and setting permissions.

Upgrade paths for VMAN and VIM

The releases of Virtualization Manager (VMAN) and Virtual Infrastructure Monitor (VIM) are tied together by releases. When determining the upgrade path of VMAN with other Orion products, compare the VMAN and VIM versions to NPM.

For full information on VIM and VMAN upgrade paths, see this article.

Important VMAN 7.2 appliance: You cannot upgrade the VMAN appliance from a previous version to 7.2. You must migrate to the VMAN 7.2 appliance. Migration is supported for previous VMAN appliance versions including 6.3.2, 7.0, and 7.1.

Upgrade paths for VMAN

For stand-alone VMAN installations, you can directly upgrade older VMAN versions to the latest:

  • VMAN 6.0 through 6.3.2: directly upgrade to VMAN 7.0 or VMAN 7.1
  • VMAN 7.0: directly upgrade to VMAN 7.1

If VMAN is integrated with Orion Platform products such as NPM or SAM, see the next section to build your upgrade path.

Upgrade paths for VMAN with other Orion products

First, check your version of VIM supported by VMAN. You can compare this version with NPM to determine an upgrade path for multiple Orion products. Not sure what version you have? Check the footer in the Orion Web Console.

Select your version of VIM:

Compatible version(s) of VMAN:

  • VMAN 6.0.0
  • VMAN 6.0.1
  • VMAN 6.1.0
  • VMAN 6.1.1
  • VMAN 6.2.0
  • VMAN 6.3.0
  • VMAN 6.3.1
  • VMAN 6.3.2
  • VMAN 7.0.0
  • VMAN 7.1.0
  • VMAN 7.2.0

To find the upgrade path for VIM, select NPM versions to find the compatible version of VIM. When setting your upgrade path, you can use this version of NPM to determine your path for VMAN and VIM.

Select your version of NPM:

Compatible version(s) of VIM:

  • VIM 1.7.0
  • VIM 1.8.1
  • VIM 1.9.0
  • VIM 1.10.0
  • VIM 1.11.0
  • VIM 2.0
  • VIM 2.1
  • VIM 2.1.2
  • VIM 7.0.0
  • VIM 7.1.0

For example, if you have VMAN 6.3.2/IVIM 2.1.2 and NPM 12.0 and want to upgrade to the latest, you would use the following upgrade path:

  1. Upgrade to NPM 12.1. NPM 12.1 comes with VIM 7.0.
  2. Upgrade to VMAN 7.1 / VIM 7.1. The VMAN 7.1 zip file includes VMAN and VIM installations.

Important for VMAN 7.0 integrated

  • VMAN 7.0 requires VIM 7.0 (included with the VMAN download). This version is includes with the VMAN download, Orion Platform 2016.2, NPM 12.0.1, SAM 6.3, and NCM 7.5.1. VIM 7.0 provides an upgraded Orion Platform.
  • If you have multiple Orion Platform products installed: You must upgrade all Orion Platform products to versions supporting 2016.2 prior to upgrading to VMAN 7.0.

Preflight upgrade checklist

This preflight checklist details a number of important steps to help plan and prep for your upgrade.

Review release notes

Review product release notes and available documentation in our Success Center.

Review system requirements

Make sure your environment has all of the required hardware and software needs for your installations. You can verify the requirements for products and multi-module environments guidelines.

  • For VMAN product requirements, see: 7.1 | 7.0 | 6.3.2.
  • For VIM stand-alone product requirements, see: 7.1 | 7.0 | 6.3.2.
Review licenses Review your current product licenses and determine if you need to make any changes. You can download any updated license keys for your upgrade through your Customer Portal. Verify any license upgrades and needs with your SolarWinds account manager or contact SolarWinds.
Do you need to migrate?

You may need to migrate products and databases to new dedicated servers or to shared servers. Check if you need to migrate by reviewing new requirements, your products, and your current environment.

Migrating adds time to your upgrade, but you have the best opportunity to update to new servers during an upgrade.

Gather credentials Make sure you have all account credentials, SQL database credentials, your SolarWinds account, and local admin server credentials.
Build your upgrade path

For VMAN

Determine your VMAN upgrade path. If upgrading from an older version, you may need to upgrade to specific versions in steps. For example, VMAN 6.0 and higher can directly upgrade to VMAN 7.0.

For VMAN integrated with VIM or an existing Orion Platform

Determine your VIM upgrade path, first determining the supported version for VIM with NPM. Then use the Upgrade Product Advisor to build your upgrade path using the supported version of NPM with other products.

We recommend downloading a PDF of your upgrade path from the Product Upgrade Advisor tool. You can use it as a checklist as you complete upgrades.

Run all Windows updates Before upgrading, check for and run all Microsoft Windows Updates on your main poller, all additional pollers, and all additional web servers. As you upgrade, if a Windows update runs, your system may reboot as needed by Windows.
Schedule the upgrade Set up the maintenance window, preferably off-peak hours. Depending on the number of products, size of database(s), and size of environment, you may need hours to complete your upgrade.

Upgrades will require polling engines and SolarWinds services to be offline for a length of time, causing you to lose a portion of polling data.

Notify your company Send a message to your company of the upgrade schedule and maintenance window. If you need additional help, contact and allocate specific staff to be available.

How long does an upgrade take?

The time it takes to complete an upgrade depends on:

  • Hardware
  • Database server performance and database size
  • Number of additional pollers
  • Number of additional web servers
  • Environment performance
  • Number of modules being upgraded
  • Number of devices being polled

Since every configuration is different, we cannot predict exactly how long your upgrade will take. Coming soon, we are compiling feedback with the THWACK community about upgrade times to help give you a ballpark estimate. Through this guide, we include steps and tips to help reduce time for your upgrade.

Gotchas you should review

  • For VMAN 7.2, you cannot upgrade the appliance. You must migrate to a new appliance. See VMAN 7.2 Release Notes and the VMAN 7.2 Migration Guide.
  • 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.
  • 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 with custom menus, you can not see the Performance Dashboard link in the menu. For details, see this article.
  • After integrated integrated VMAN 7.1, future releases will no longer support Windows OS 2008 and 2008 R2 and Microsoft SQL Server 2008 R2 for Orion Platform installations. Integrated Patch Manager 2.1.4 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.
  • VMAN 7.0 no longer supports the VMware vSphere plug-in.
  • Check your VMAN license amounts prior to upgrading. The upgrade process may locate and add VMs beyond your license support causing issues.
  • VMAN 6.3.2 no longer supports Windows Server 2003, 2008, 2008 SP2, or 2008 R2 without SP1.
  • VMAN 6.3.2 has new port requirements: 5671 (Rabbit MQ messaging) and  17778 (SW Information Service, agent communication to 2012).
  • If you have edited resource properties, the All Groups resource may be empty after upgrading to VMAN 6.3.2.VMAN 6.3.2.
  • When upgrading to VMAN 6.3.2, using the VMAN 6.3.2, using the group by feature for custom properties may return no results, and the data loading may hang or not complete. All regular functionality is unaffected by the issue. 
  • VMAN 6.3.2 and later no longer support SQL 2005.

General Orion Platform gotchas

  • If you have written your own code, such as changing SolarWinds .css files or adding .js files, or been directed to make changes by Support, the code may be overwritten during the upgrade. You can learn more about upgrading with custom code here.
  • Always check that you have enough hard drive space for zipped and unzipped installers. One unzipped installer could consume a couple GBs of space.
  • During your upgrade, use the Scalability Engine Installer. If you use downloaded installers or the installer bundle, you must install one product and version at a time. The versions must match between the main and additional poller or you will receive a Database Configuration Failure Error.
  • If you are upgrading from a very early or End of Life SolarWinds product version, you may want to install a new product instead of performing an upgrade, saving or migrating your data. SolarWinds Support can provide the best advice for these upgrade scenarios.
  • If you have enabled SolarWinds High Availability, you must disable High Availability before you can upgrade. You must have the same versions of SolarWinds products on your primary and secondary server before you can re-enable your HA pools. See the Upgrade with HA section.

Prepare your environment to upgrade

When you are ready to upgrade, complete these steps. They include the common actions you need to complete before upgrading products.

If you have a test or staging environment, we highly recommend testing the upgrade first. You cannot roll back an installation once completed.

1. Back up the DB

Snapshot your VMs

Back up your SolarWinds SQL database. If you need help, please check your vendor's site for documentation and instructions.

If you have your database on a VM, create a snapshot or copy of your VM.

You cannot roll back an upgrade. Always create a database backup.

2. Back up custom code (Optional)

(Optional) Back up your custom code. When upgrading, any custom additions or changes to the interface will be saved over.

3. Back up Report Writer reports (Optional)

Upgrading to an Orion Platform 2016.1 or later product? You can skip this step.

If you use Report Writer reports (NPM 10.5 and earlier) or still have legacy reports, back up the reports folder to save your custom reports:

  • 64-bit OS: C:\Program Files x86\Solarwinds\Orion\Reportsx86\Solarwinds\Orion\Reports
  • 32-bit OS: C:\Program Files\Solarwinds\Orion
4. Exclude files on anti-virus software

To ensure the best performance on your server host and provide full file access, exclude specific file paths and directories from anti-virus software scans. See this article for details.

You can also place your systems behind a firewall to completely disable your anti-virus software during an upgrade.

5. Stop services Stop services in the Orion Service Manager on the main polling engine, all additional polling engines, and all web servers.

Upgrade VMAN appliance

This checklist details the steps for upgrading the VMAN virtual appliance.

For VMAN 7.2, you must migrate the appliance to a new VM. Follow the installation instructions in VMAN 7.1 to 7.2 appliance migration for CentOS 6. After migrating, you can complete upgrades of VIM / the Orion Platform.

1. Download the VMAN install

Download the VMAN product ISO file from the Customer Portal in the My Downloads area. Save this file to your systems. This file includes the VMAN appliance and VIM install for the Orion Platform:

  • VMAN-Appliance-Install-1st.ova - deploys the VMAN appliance. Use this file in your deployment.
  • VMAN-Orion-Install-2nd.exe - installs the Virtual Infrastructure Monitor for a standalone Orion Platform. If you do not have an existing Orion Platform, VIM provides all Orion and additional VMAN features through the Orion Web Console.

2. Upgrade on vSphere 5.x or later

If you have VMAN hosted on Hyper-V, go to 3. Upgrade on Hyper-V.

  1. Save the ISO file to the computer you use to access the vSphere client.
  2. Start the vSphere client, and log in as an administrator.
  3. Select the virtual machine currently running SolarWinds Virtualization Manager.
  4. Click the CD/DVD icon, and click CD/DVD Drive 1 > Connect to ISO image on local disk.
  5. Select the ISO file, and click Open.
  6. Open a browser to https://ip_address:5480 where ip_address is the IP address or name of the SolarWinds Virtualization Manager VM.
  7. Log in to the website.
  8. Click Update > Check Updates.
  9. Click Install Updates, and click OK.

For more information, see Upgrade a virtual appliance.

When upgrading VMAN 7.0 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.

3. Upgrade on Hyper-V
  1. Save the ISO file to a data storage you can access from the virtual machine running SolarWinds Virtualization Manager.
  2. Run the Hyper-V Manager.
  3. Select the virtual machine currently running SolarWinds Virtualization Manager.
  4. Click Settings > DVD Drive.
  5. Select the Image file, and click Browse.
  6. Select the ISO file, click Open, and click OK.
  7. Open a browser to https://ip_address:5480 where ip_address is the IP address or name of the SolarWinds Virtualization Manager VM.
  8. Log in to the website using your SolarWinds Virtualization Manager credentials.
  9. Click Update > Check Updates.
  10. Click Install Updates, and click OK.

For more information, see Upgrade a virtual appliance.

4. Verify the upgrade

If VMAN displays unusual behavior after upgrading, clear the browser cache.VMAN displays unusual behavior after upgrading, clear the browser cache.

5. Upgrade VIM / Orion Platform

To access the full range of VMAN features, make sure to upgrade your stand-alone or existing Orion Platform. You will use the second file VMAN-Orion-Install-2nd.exe. This install updates all virtualization features part of the Orion Platform and adds or updates VMAN specific features, for example Recommendations.

Continue to that section.

Upgrade federated collectors

Upgrading to the latest version of VMAN upgrades the Virtualization Manager software on both the master virtual appliance and on federated collectors. The upgrade also raises the CentOS version on the master appliance, but you must manually upgrade CentOS on federated collectors using the .ISO file.

If the federated collector is not updated automatically from the master appliance through port 443, enable communication over port 80 for a limited period of time. The upgrade checker runs hourly by default, and the collectors will upgrade automatically during this period.

Upgrade VIM/Orion Platform for integrated VMAN

For VMAN integrated with the Orion Web Console, you need to upgrade to Virtual Infrastructure Monitor (VIM) using the file VMAN-Orion-Install-2nd.exe. Regardless of your installed Orion product version (such as VMAN integrated with the Orion Web Console, you need to upgrade to Virtual Infrastructure Monitor (VIM).

If you upgrade VIM before VMAN, make sure to upgrade the appliance after.

Multiple Orion Platform product integration: Regardless of your installed Orion product version (such as NPM 12.0.1 or SAM 6.3), you may need to run this installer:

  • VIM 7.0: This version is included with NPM 12.0.1 and SAM 6.3 installations.
  • VIM 7.1: This version is included with SAM 6.4 installation. If you have installed NPM 12.1, you must run the VIM 7.1 upgrade.

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

  • VMAN-Appliance-Install-1st.ova - deploys the VMAN appliance. Run this file first when deploying the VMAN appliance to Hyper-V or vSphere servers. A Hyper-V zip file is also available for those servers.
  • VMAN-Orion-Install-2nd.exe - installs the Orion Platform and Virtual Infrastructure Monitor (VIM) for virtualization monitoring. This is a full Orion Platform installation.

 

1. Upgrade other Orion products (optional)

If the Orion Platform has additional Orion products such as NPM, SAM, or NCM, you may need to upgrade those products to upgrade VIM or integrate the upgraded VMAN.VMAN.

  1. Verify if your upgraded VMAN requires specific versions for your installed Orion products.VMAN requires specific versions for your installed Orion products.
    For compatibility and upgrade path information, see the upgrade path section.
  2. Get your upgrade path from the SolarWinds Product Upgrade Advisor for the required version(s).
  3. Upgrade your products using the upgrade path and the SolarWinds Upgrade Guide. You must upgrade on the main poller first, then each additional polling engine, then additional web servers.
2. Upgrade VIM / Orion Platform

You must upgrade on the main poller first, then each additional polling engine, then additional web servers. The versions must match across all servers as you upgrade.

  1. Download the VIM product installation file from your Customer Portal in the My Downloads area.
  2. Save this file to your Orion server.
  3. Run the installation file as an administrator.
  4. Run the Configuration Wizard. Steps populate with previously configured settings including the Orion SQL database.
3. Upgrade additional polling engines and additional web server

If your Orion Platform has additional polling engines or an additional web server, you should upgrade using the Scalability Engine Installer.

  1. Install your modules on the Main Poller. When complete, you will need to upgrade your additional polling engines and additional web servers.
  2. Download this installer through the Orion Web Console.
    • For the APE installer, click Settings > All Settings > Polling Engines.
    • For the AWS installer, click Settings > All Settings > Web Console Settings. 
  3. Copy the installer to your APE or AWS.
  4. Run the appropriate installer on your APE and AWS. This single installer will upgrade all Orion modules on each of these servers. If you are upgrading one or more modules, all modules are upgraded.
3. Start the engines

Start services in the Orion Service Manager on the main polling engine, all additional polling engines, and all web servers.

You are done! Access the Orion Web Console to verify VMAN is integrated, updated, and data is polling correctly.

After the upgrade check your system

All product versions should be installed properly. Open the application and verify the versions displayed in the footer of the Web Console. Try current and new features with your system to check performance and expected functionality. If you run into issues, check the troubleshooting tips.

Troubleshooting

If you receive errors, try the following:

  • If you experience issues and are not on the latest product versions, we recommend completing a full upgrade. Use the Product Upgrade Advisor to create the upgrade path. Many of these updates solve issues you may experience part way through your upgrade.
  • Check our Success Center for troubleshooting. We recommend searching the name of the product, the version number, any error codes or messages displayed, and the general issue you found.
  • Check your Customer Portal for any new hotfixes.
  • If you receive (500) internal server error after an upgrade, use the Orion permission checker to make sure your Group Policy is not locked. See this article for full details.
  • If your views do not load when first opening the console, run the Configuration Wizard again.

If an issue occurs you need additional help with, contact Support. We recommend gathering diagnostics, a screenshot of the issue, and any error codes you receive. Attach and add this information to your ticket.  You may also want to gather additional diagnostics on your additional pollers and web servers.

Want to learn more?

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
11:44, 1 Jun 2017

Tags

Classifications

Public