Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN Documentation > Previous Versions > SolarWinds Virtualization Manager 7.1 HotFix 1

SolarWinds Virtualization Manager 7.1 HotFix 1

 

Updated: 4-4-2017

 

You can find this and other VMAN Hotfixes in the Customer Portal product downloads section.

Fixed issues

This hotfix addresses the following issues:

  • Latest data is not computed because of wrong VM identity matching. The VMware Replication Engine is used for VM cloning.
  • VMAN configuration does not accept IPv6 addresses.
  • Users do not see any recommendations even though VMAN has been installed and integrated with the Orion Platform for over a week.
  • No data is transferred with a successful integration with Orion. Users do not receive any recommendations, sprawl metrics, and so on.
  • Some trend values are empty because of wrong VM identity matching.

Environment

  • VMAN 7.1
  • VIM 7.1

Notes

  • Installing the hotfix replaces the Virtualization Manager application.
  • The original files are renamed and saved for rollback to the original.  
  • The install script restarts the Tomcat service, and the Virtualization Manager runs the hotfix.

Installation instructions

Install automatically

After applying the hotfix, the issues outlined above do not occur.

  1. Log in to the management interface at https://[VMan IP/Hostname]:5480
  2. On the SolarWinds Mgmt tab, switch to the HotFix view.
  3. Enter the URL of the archive, or upload the file directly.

Install manually

  1. Use SCP to copy the enclosed VMAN-v7.1.0-HF1.tgz file to the admin user home directory on the master appliance (/home/admin).
  2. Log in to the appliance as an admin user using SSH (for example using putty):

    $ cd /home/admin
    $ tar xf VMAN-v7.1.0-HF1.tgz
    $ sudo bash ./install-v7.1.0-HF1.sh

After applying the hotfix, the issues outlined above do not occur.

Uninstall the hotfix automatically

  1. Log in to the management interface at https://[VMan IP/Hostname]:5480.
  2. On the SolarWinds Mgmt tab, switch to the HotFix view.
  3. Click the Uninstall button.

Uninstall the hotfix manually

Log in to the appliance as an admin user, and sudo bash.
    $ cd /var/solarwinds/hotfix
    $ sudo bash ./uninstall-v7.1.0-HF1.sh

 

For more information, contact Technical Support at https://support.solarwinds.com/Succe...g_With_Support

Last modified

Tags

Classifications

Public