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 5.1.0 Release Notes

Virtualization Manager 5.1.0 Release Notes

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 586 Votes: 0 Revisions: 6

Updated 12/03/2012

These release notes provide additional guidance for SolarWinds Virtualization Manager v5.1 Service Release.

You can no longer upgrade on Windows. All versions prior to v5.0 and all Windows versions of Virtualization Manager have entered the End-Of-Life (EOL) cycle. View the SolarWinds EOL Policy online.

SolarWinds provides a migration tool to help transition from both older virtual appliances and Windows installations to Virtualization Manager v5.0.x.

As of SolarWinds Virtualization Manager v5.0, the licensing restrictions have changed. If you have exceeded your license count or trial period, you will not be able to enable schedules or upgrade. However, you will be able to edit and save data sources.

New Features and Improvements

SolarWinds Virtualization Manager v5.1 includes the following new features and improvements:

  • New Attribute Search Filters

    Filter search results by VM environment - VMWare, Hyper-V, or common to both environments

  • Performance Optimization

    Increased database and daily rollup performance

  • Hyper-V Disk Volume Information

    Increased visibility to Hyper-V disk volume information

  • New Dashboard

    Added the "Admin - Desktop" dashboard for VMs running a desktop OS

  • Cluster Shared Volume Information

    View information about your cluster shared volumes

  • Map Sorting

    Items shown in the map or map widget are now sorted by criticality

Fixed Issues

Issue Case Number

Multiple upgrade issues when upgrading from older versions

318342

Cluster IOPs numbers inaccurate

313951

Unable to schedule a report

335449

Missing content when exporting data from Top-N widgets

-

Cannot logon to dashboard after upgrade

329296

Not collecting data

351398

Issues with alerts and collection jobs

352123

When exporting graphical reports, the Y-axis loses units

365525

Delete invalid collection schedules

369452

Experiencing long running collection jobs

373893

Issues with collecting data from Hyper-V clusters

376896

Cannot save hyphenated AD realm names

-

Cannot verify host server identity when hardware is not officially supported by VMWare

376071

Chargeback report contains zeros

381569

Guest Storage Space utilization not updating

381509

Cannot overwrite duplicate content when importing files

391687

Total latency data is not collected for NFS datastores for ESX 4.1 or later

-

IOPs information does not display for Hyper-V VMs and will not be calculated in the following trends: Cluster VM IOPs Usage, Cluster VM Max IOPs Usage, Cluster VM Min IOPS Usage, and EBS Monthly I/O Cost.

-

Open Issues

Issue Case Number

Multiple issues after an upgrade from 4.1 to 5.0.

113267

Null pointer exception interferes with collection jobs and alerts.

352123

Main Virtualization Manager appliance is slow to start.

329296

Different values for clusters' component values vs. standalone host IOPs.

313951

Upgraded Tomcat necessary for PCI compliance.

382484

Out of memory exception due to large DOM documents.

341221

Slow Lucene indexing results in long collection times.

355003

Cannot log on to administration site with IE10.

-

Only collects from English versions of Hyper-V servers.

-

Timestamps are saved in local time and will not respect time zone changes made to the appliance.

-

After a trend report is run, the results are only available in Report Results.

-

Queries reports fail if the query returns no results.

-

If a federated collector is polling a vCenter server behind a firewall, then Virtualization Manager cannot validate the data source.

-

If you use a cron job to schedule a report, you must also specify seconds.

-

To successfully migrate AD settings from v4.0, upgrade to v4.1 and then to v5.0.

-

Scheduled Reports may not respect the time selected when the job is saved.

-

Read and write latency and IOP data sometimes cannot be seen.

-

Search results for hosts sometimes show Running VMs values as NaN.

-

The consumption chart widget reports incorrect value for Days Remaining after a threshold is reached.

-

An edge case exists in the Capacity Planner where a negative capacity remaining value can incorrectly indicate that more VMs can be accommodated.

-

Completed reports cannot be scheduled to run it again in the same day if scheduled to Run Once.

-

Legal

Last modified
04:14, 23 Jun 2016

Tags

Classifications

Public