VMware vCenter CapacityIQ 1.0.1 Release Notes

VMware vCenter CapacityIQ Version 1.0.1| 15 December 2009 | Build 214574

Last Document Update: 15 December 2009

These release notes describe the following topics:

Introducing vCenter CapacityIQ

VMware vCenter CapacityIQ is a capacity management and planning tool for VMware Infrastructure environments. CapacityIQ helps you:

  • Eliminate waste by identifying any unused or over-allocated capacity
  • Reduce operational overhead by automating routine capacity monitoring and management tasks
  • Minimize business risk of outages or failures resulting from capacity bottlenecks and shortfalls

CapacityIQ supports VirtualCenter 2.5, Update 4 and Update 5 and vCenter Server 4.0.x, managing hosts running ESX Server 3.0.1 through ESX 4.0.x.

Key Features

This section describes the key features available in CapacityIQ.

Capacity Awareness

  • View and analyze past, present, and future capacity states at-a-glance with dashboard graphs and tables.
  • Eliminate costly routine monitoring and management tasks through automation using customized capacity thresholds and alerts.

Capacity Optimization

  • Reclaim excess capacity from idle, oversized, or powered-off virtual machines.
  • Size and allocate capacity for each virtual machine based on historical and future needs.
  • Place virtual machines in the most optimal clusters to eliminate further waste.

Capacity Prediction

  • Simulate one-time business events to quantify potential business impact.
  • Identify the timing of potential capacity shortfalls based on trends and forecasts.
  • Purchase and provision capacity as and when needed.

Before You Begin

When you are ready to install CapacityIQ, see the vCenter CapacityIQ Installation Guide for instructions.

CapacityIQ 1.0.1 Support and Configurations

Review the following support and configurations that affect the performance of CapacityIQ 1.0.1.

CapacityIQ 1.0.1 Scalability Limits

The scalability limits of CapacityIQ 1.0.1 are the same as the limits for CapacityIQ 1.0. CapacityIQ 1.0.1 supports 200 hosts, 2000 powered on virtual machines, and a total of 3000 virtual machines. This is the case even though the scalability limits of vCenter Server 4.0 are 300 hosts and 3000 powered on virtual machines. For cluster sizes that exceed 400 VMs, see the Known Issues section for more information.. For more information about vCenter Server Scalability limits, see Enhanced vCenter Server 4 Scalability in the What Is New in VMware vCenter Server 4 white paper.

High Availability Rules

In modeling and forecasting capacity, CapacityIQ 1.0.1 factors high availability (HA) failover capacity when it is configured in vCenter Server 4.0 using certain parameters. CapacityIQ factors HA when a fixed number of failover hosts are selected in the Admission Control Policy. CapacityIQ will not factor HA failover capacity if the Admission Control Policy is set to one of the following:

  • Percentage of cluster resources reserved as failover spare capacity
  • Specify a failover host

Known Issues

The following are known issues in this release.

Issues with Time

  • It takes an hour or two for information associated with the following events to appear in the user interface.
    • It can take up to two hours after a new host is added to vCenter Server for the host to be considered in capacity estimates.
    • After installation, it takes 40 minutes or more for inventory information to appear in the user interface.
  • If you make changes in a cluster, such as moving a host out of the cluster and then moving it back, and then create a what-if scenario, it might take two or three hours for the change to be reflected in the what-if scenario.

    Workaround: There is no workaround at this time.

  • If a dashboard or view is open for more than an hour, the dashboard or view should be refreshed.

    Workaround: Click the selected object in the inventory panel to get the latest data.

How Information Appears in the User Interface

  • On the Virtual Machine Capacity - Summary view, it is possible to see values, such as Time Remaining > 1 year, even though the Total Capacity, Avg. Deployed, and Remaining values are null.

    This occurs only within the first two hours after an object is added.

  • When Fault Tolerance (FT) is enabled on a Virtual Machine, both the primary and secondary virtual machines appear with the same name in the navigation tree.

    Workaround: There is no workaround at this time.

  • After removing a host or virtual machine, the data you collected prior to removing either of them cannot be reconciled with data that is collected after you re-add them to the datacenter.

    Workaround: Consider disconnecting and reconnecting the virtual machine or host.

  • The data in the pie chart on the Common Virtual Machine Configurations - Distribution view might not display properly if you change the Capacity Calculation Rules in Capacity and Trend Analysis global settings. The default Capacity Calculation Rules setting is Use last known capacity per interval. If you change the setting to Use average capacity per interval, the pie chart could be missing data. The information that does appear is counts of the unique virtual machine configurations observed within the analysis period, rather than the average or last known configurations.

    Workaround: There is no workaround at this time.

  • In the Determine Virtual Machine Capacity Usage-Trend view, the CPU Limit trending line can show a greater value than the Configured CPU trending line.

    This information might appear to be in error, but CapacityIQ allows the CPU Limit to be set higher than the configured CPU. Configured CPU is calculated as vCPU count x host CPU speed per core.

  • Trend views might mishandle the display of information on the view page. If you use a computer with the screen resolution set smaller than 1024 x 768, the text string that appears below the Data Window bar might be truncated.

    Workaround: Change the screen resolution to a higher resolution when working with trend views.

  • What-if analysis cannot be performed on a new standalone host that VI Client has not finished adding to inventory.

    Workaround: Links for applying what-if scenarios to the host, either in the dashboard or in views, do not appear until an hour or two after the host has been added to VI Client.

  • If you click Combine/Compare while a what-if scenario is being applied, the scenario is not applied to the view.

    Workaround: Wait for the scenario application to complete before you click Combine/Compare.

  • If CapacityIQ performs a shutdown that was not initiated through the ciq-admin command-line, the Admin Portal might not show that the connection status is disconnected. The status updates when you restart CapacityIQ.

    Workaround: There is no workaround at this time.

  • Changes to roles and permissions for a user in the vShpere Client might result in a mismatched view of objects between the VI Client inventory panel and the CapacityIQ inventory panel.

    Workaround: Press F5 to refresh the Capacity IQ client view.

  • When a cluster has 400 virtual machines or more, an Internet Explorer warning might appear while expanding the cluster. The warning asks you if you want to abort the currently running script.

    Workaround: Click No to allow the script to continue running.

  • When certain objects are selected in the inventory panel, they might appear to have clickable child objects, but this is not accurate.

    The affected object types include the following:

    • Hosts and clusters with only folders
    • A datacenter with only folders
    • A cluster with only resource pools
    • A host with only resource pools

    Workaround: There is no workaround at this time.

  • If you update CapacityIQ from 1.0 to 1.0.1, the vCenter Client Plug-In Manager does not display the latest version and build number. The vCenter Client Plug-in Manager will continue to display the older version of CapacityIQ.

    Workaround: To display the update data correctly, consider un-registering the CapacityIQ plug-in using the Admin Portal and then reregister it to the same vCenter Server.

Miscellaneous Issues

  • Rendering time for certain views might be noticeably slow.

    This might happen when a cluster is selected in the inventory panel, or when the selected object contains over 500 virtual machines. In these cases, the following views can take up to a minute to render in the user interface:

    • Powered-Off Virtual Machines
    • Idle Virtual Machines
    • Oversized Virtual Machines

    Note: These views are also available in report form under the Reports tab. These reports can be started and processed in the background.

  • Under certain conditions, use the alternative method for registering a new instance of CapacityIQ. Use the alternative method if you experience difficulties with the recommended method, there are spaces in the user name or password, or you no longer know the address of the original CapacityIQ instance.

    See the vCenter CapacityIQ Installation Guide for instructions.

  • When the vCenter Server is down, the License or Status tabs in CapacityIQ might take some time to update.

    Workaround: Determine if the vCenter Server is running when the CapacityIQ License or Status tabs are slow to respond.

  • If you create an empty folder under All Datacenters, and attempt to expand All Datacenters in Capacity IQ, you get an infinite Loading... indicator.

    Workaround: Press F5 to refresh CapacityIQ.

  • If you apply an update manually using the ciq-admin command-line, the build number in the Admin Portal header might not match the build number shown on the Status page under CapacityIQ vApp Info.

    Workaround: Press F5 to refresh the Admin Portal, which logs you out. Log back in.

  • Numbers for memory consumed are slightly higher than the numbers reported by vCenter Server. On the Dashboard and on the Virtual Machine Capacity Usage - Trend view of a virtual machine page, the numbers of memory consumed are slightly higher than the numbers reported by vCenter Server. This occurs because CapacityIQ adds ESX memory overhead to the consumed memory number for the virtual machine.

    The numbers on the following pages are affected:


    • VM Memory Consumed - this number is slightly higher, because ESX memory overhead is added.
    • Total VM Memory Remaining - this number is slightly lower, because ESX memory overhead is subtracted.

    Virtual Machine Capacity Usage - Trend view

    • VM Memory Consumed - this number is slightly higher, because ESX memory overhead is added.
  • On some CapacityIQ pages, the client shows an Error loading view message. CapacityIQ uses a Internet Explorer browser control for rendering its pages. This message might display after upgrading CapacityIQ and the Internet Explorer cache is full.

    Workaround: Clear the Internet Explorer cache. See Microsoft knowledge base article 260897 for instructions. If the problem persists, after clearing the cache, please contact a VMware Service Representative.

  • The wrong start time appears in the slider if you selected a different time zone for the interval range start date. If the current time is Standard Time (non-Daylight Savings Time), and you select Daylight Savings Time for the interval range start date, the slider displays the wrong start time (non-Daylight Savings Time) when data is reloaded. The correct requested interval range appears in the view, but not in the slider. The start time appears as one interval before the actual requested start date.

    Workaround: Set the start date to the correct date before updating the interval range for the view.