VMware Capacity Planner 2.7.2 Release Notes

VMware Capacity Planner Version 2.7.2| 29 January 2010 | Build 38649

Last Document Update: January 29, 2010

These release notes describe the following topics:

Introducing Capacity Planner

Using Capacity Planner, you can assess your capacity planning needs, consider virtualization, and run consolidation assessments. These assessments help to virtualize and consolidate data center infrastructure, redeploy strategic IT assets, and optimize workload capacity utilization.

Known Issues

The following are known issues in this release.

  • When the collector system uses different locales, more specifically, different decimal separators, the collector system gathers values that are too high for the CPU MHz on Unix and Linux systems. In addition, the collector does not support non-US operating systems. For example, Capacity Planner does not support the collector on a German version of Windows XP, even if it is set to a US locale.
  • When Capacity Planner collects inventory from a Dell PowerEdge system with DRAC, the inventory reports a Virtual Floppy of 32TB. The root cause of this issue has not been identified and there is currently no solution available. A probable cause is the absence of an uploaded floppy image in the DRAC, which causes the DRAC to report a very high media size to the operating system.
  • For Unix and Linux systems, currently there is no reliable method to get the CPU rated speed. As a result, the CPU rated speed is assumed to be the same as the current speed. The current speed can vary from the standard rated speed due to dynamic frequency scaling (CPU throttling).
  • The Quick Assessment table has a different purpose than the optimization report. The goal of Quick Assessment is to help you in selecting new hardware for the scenario. That's why during a quick assessment existing servers are not redeployed. Servers will only be placed on the selected new hardware. Optimization reports present the actual results from running the scenario and might redeploy existing hardware based on scenario settings. There can be substantial deviations in results between the two.
  • Duplicate entries might be present on the Administration > Configure Collectors > Manage Systems > Collection Details - Task Status page if two collectors used to own the same system and sent inventory and performance data to the Dashboard. The duplicate entries are not deleted when remote configuration is run again.
    Workaround: Duplicate entries are deleted only when you load balance on the Dashboard.
  • For Microsoft Windows 2008 systems, when inventory is collected using remote registry, the collector is not able to collect the display name and description of services in the appropriate form.
    For example, for W32Time service:
    Display name: @%SystemRoot%\system32\w32time.dll,-200 - instead of Windows Time
    Description: @%SystemRoot%\system32\w32time.dll,-201 - instead of 2)_A_RUNNING Maintains date and time synchronization on all clients and servers in the network. If this service is stopped, date and time synchronization will be unavailable. If this service is disabled, any services that explicitly depend on it will fail.
  • Video card information (current resolution and current color depth) is not collected from Microsoft Windows Vista and Windows 2008 machines using WMI.
  • When you upgrade from Capacity Planner 2.6 to Capacity Planner 2.7, all the Capacity Planner 2.6 notices are deleted from the Dashboard-Notices page.
  • In the Assessment Report: ThinApp Summary Table, only ThinApp software profiles, which are included in base images, are shown. This is expected behavior. The breakdown is not per application but per base image.
  • In the assessment report, the information present in the Overview subsection of Collection Results is misleading when the date range is specified.
    Workaround: Disable (make inactive) systems discovered during periods not specified on the selected date range.
  • A new Internal Error message appears if ColdFusion is temporarily unavailable and long running reports are present.
    Workaround: Rerun the report.
  • For optimization reports, sometimes the title omits the name of the company for which the report is being generated.
  • Results from consolidation are not always the same even if the settings are the same because, if more than one option for grouping virtual machines for virtual machine templates with the same efficiency is present, only one option is selected and displayed.
  • When you modify an exiting hardware template from any location, you might see the message indicating that you should enter a numeric value; for example, Disk I/O speed must have a positive numeric value. This could occur with some hardware templates that are accessible from the Hardware Selection page or when you modify a hardware template created as a duplicate of a predefined template from Assessment > Assessment Tools > Hardware Templates.
    Workaround: Enter a positive numeric value for Disk I/O speed.
  • The custom report display limit shown in the online help topic Optimizing Resources > Reports > Create a Custom Report is no longer correct.

Resolved Issues

The following issues have been fixed in this release.

  • Previously, in 2.7.1, the sequential failure count on the Troubleshoot Systems page did not update properly.
  • In 2.7.1, for specific groups you were not able to select consolidation rules that allow cross boundaries and redeployment of systems on existing and new hardware scenarios used in optimization reports. Select All Systems was selected by default, Cross Boundaries was disabled for Department, Environment, Functions, and Locations, and Redeployment was always done on new hardware.
  • In 2.7.1, the progress report and the vintage systems report displayed different values for collected inventory for the same systems due to formulaic differences in the generation of the two reports.
  • Previously, to see specific details when running a report for a scenario in 2.7.1, you had to select the correct option for that report. The Summary and individual machine details option on the Specify Consolidation Rules page is specific to a scenario report. From Reports > Optimization Reports Settings > Edit Report Settings > Select Report Output, the Include Individual Virtual Machine Details setting is specific to the assessment report.