Submit a ticketCall us

Virtualization Manager 7.0 is here!
Read the Upgrade Guide and learn how to use new features in the Getting Started Guide.

 

 

 

 

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

VMAN Upgrade Guide

Updated: December 12th, 2016 | SolarWinds Upgrade Guide 1.0

Supports: VMAN 7.0 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 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.

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.

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

  • 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, make sure to upgrade one version at a time on each poller. 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 instructions in this guide.

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.

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

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

1. Prepare

Download the VMAN product ISO file from the Customer Portal in the My Downloads area. Save this file to your systems.

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

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

5. Upgrade VIM See the next section Upgrade VIM.

Upgrade VIM

For VMAN integrated with the Orion Web Console, you need to upgrade to Virtual Infrastructure Monitor (VIM). 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).

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 VMAN 7.0 and VIM 7.0, see the VMAN 7.0 and VIM 7.0, see the product compatibility.
  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

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. Start the engines

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

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
13:19, 23 Feb 2017

Tags

Classifications

Public