VMware

VMware vCenter CapacityIQ 1.0.3 Release Notes

VMware vCenter CapacityIQ Version 1.0.3| 3 June 2010 | Build 262835

Last Document Update: 15 July 2010


These release notes describe the following topics:

What's New

CapacityIQ 1.0.3 is a maintenance release that supports additional VMware High Availability (HA) settings.

CapacityIQ factors reserved capacity to meet VMware HA failover commitments. CapacityIQ uses the VMware HA settings to calculate CPU and memory capacity for clusters and datacenters. The VMware HA settings do not affect host and virtual machine capacity calculations.

CapacityIQ 1.0.2 uses the enabled status of VMware HA and number of host failures in the Admission Control Policy settings of the vSphere Client as factors for modeling and forecasting capacity. CapacityIQ 1.0.3 adds the percentage of cluster resources reserved as failover spare capacity and the dedicated failover host number as factors for capacity.

The following VMware HA settings are the factors that affect CapacityIQ calculations:

  • Enabled or disabled status of high availability.
    CapacityIQ detects VMware HA settings to calculate CPU and memory capacity for clusters and datacenters. If you do not use a VMware HA cluster, CapacityIQ sums up the capacity of all hosts in the cluster.
  • Number of host failures that the cluster tolerates.
    CapacityIQ detects the number of host failures that the cluster tolerates and excludes the hosts with the most CPU and memory capacity. For example, if a cluster has 10 hosts and you set the number of host failures to three, CapacityIQ detects which three out of the ten hosts have the most CPU and memory capacity and excludes those hosts in the calculation. The CapacityIQ calculations of VMware HA CPU capacity and VMware HA memory capacity occur separately and the hosts that CapacityIQ excludes might be different for the CPU and memory calculations.
  • Percentage of cluster resources reserved as failover spare capacity.
    CapacityIQ sums up the capacity of all hosts and multiplies that value by
    (1-<percentage_reserved_as_failover_spare_capacity>). For example, if a cluster with 20 hosts has a total of 100GHz, and 20 percent of hosts are set aside for failures, the calculation for the VMware HA CPU capacity of the cluster is 100 × (1-.2).
  • Dedicated failover host.
    CapacityIQ excludes the capacity of a dedicated failover host and sums up the capacity of the rest of the hosts. For example, if a cluster has three hosts with 9GHz, 8GHz, and 6GHz, and the 9GHz host serves as a dedicated failover host, the calculation for the VMware HA CPU capacity of the cluster is 8GHz + 6 GHz.

This maintenance release does not include any additional enhancements beyond the support of VMware HA settings.

Top of Page

Prior Releases of VMware vCenter CapacityIQ

Features from prior releases of CapacityIQ are described in the release notes for each release. To view release notes for prior releases, click one of the following links:

Top of Page

Before You Begin

Before you install CapacityIQ, review the support and scalability information and the vCenter CapacityIQ Installation Guide.

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.

CapacityIQ 1.0.3 supports 200 hosts, 2000 powered on virtual machines, and a total of 3000 virtual machines. These scalability limits exist even though the limits of vCenter Server 4.0 are 300 hosts and 3000 powered on virtual machines. For information about cluster sizes that exceed 400 virtual machines, see the Known Issues section of the release notes. For more information about vCenter Server scalability limits, see the Enhanced vCenter Server 4 Scalability section of the What Is New in VMware vCenter Server 4 white paper.

Top of Page

Known Issues

The following known issues affect the 1.0.3 release.

License

  • New: When a CapacityIQ license expires, you cannot update the license because the License key text box does not appear in the Administration Portal.

    Workaround: Use an SSH client to log in to the CapacityIQ virtual appliance as the ciqadmin user, and type the ciq-admin license add --key <license_key> command.

Upgrade

  • If you upgrade vCenter Server and CapacityIQ, the CapacityIQ plug-in might disappear from the vSphere Client. The Plug-in Manager of the vSphere Client displays a connection failure with CapacityIQ.

    Workaround: From the Setup tab of the CapacityIQ Administration Portal, click Unregister, click Register, type the credentials for the vCenter Server system to which CapacityIQ connects, and click Apply.

Time

  • CapacityIQ takes an hour or two to display information associated with the following events in the user interface:
    • CapacityIQ might take up to two hours after a new host is added to vCenter Server for the host to account for the addition 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 moving it back, and you create a what-if scenario, it might take two or three hours for the changes to appear in the what-if scenario.
  • If a dashboard or view is open for more than an hour, the information might become outdated.

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

User Interface

  • On the Virtual Machine Capacity - Summary view, you might see values, such as Time Remaining > 1 year, even when the Total Capacity, Avg. Deployed, and Remaining values are null.

    This occurs only within the first two hours after the addition of an object.

  • When you enable Fault Tolerance (FT) on a virtual machine, the primary and secondary virtual machines appear with the same name in the navigation tree.
  • When you remove a host or virtual machine, the data that CapacityIQ collects before the removal cannot be reconciled with the data that CapacityIQ collects after you add the host or virtual machine back to the datacenter.

    Workaround: Disconnect and reconnect the virtual machine or host.

  • The data in the pie chart on the Common Virtual Machine Configurations - Distribution view might not appear 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 might exclude some data. The information that does appear includes the counts of the unique virtual machine configurations observed within the analysis period, rather than the average or last known configurations.
  • 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 inaccurate, but the CPU limit can be higher than the configured CPU. CapacityIQ calculates configured CPU 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 occur on a new standalone host that the vSphere 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 is added to the vSphere Client.

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

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

  • If CapacityIQ performs a shutdown that is not initiated through the ciq-admin command-line interface, the Administration Portal might not show that the connection status is disconnected. Restarting CapacityIQ updates the status.
  • Changes to roles and permissions for a user in the vSphere Client might result in a mismatched view of objects between the vSphere 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 when you expand 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 you select objects in the inventory panel, the objects might inaccurately appear to have child objects.

    The following object types might display this issue:

    • Hosts and clusters with only folders
    • A datacenter with only folders
    • A cluster with only resource pools
    • A host with only resource pools
  • If you update CapacityIQ, the Plug-in Manager in the vSphere Client does not display the latest version and build number. The Plug-in Manager continues to display the older version of CapacityIQ.

    Workaround: To display the update data, unregister CapacityIQ in the Administration Portal and reregister it to the same vCenter Server system.

Miscellaneous

  • Rendering time for certain views might be slow.

    This might happen when you select a cluster 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

    These views are available in report form on the Reports tab. CapacityIQ can start and process these reports in the background.

  • Under certain conditions, use an alternative method for registering a new instance of CapacityIQ. You might use this method when you experience difficulties with the recommended method, when spaces exist in the user name or password, or when 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 information.
  • If you create an empty folder under All Datacenters, and attempt to expand All Datacenters in Capacity IQ, you see an infinite Loading... indicator.

    Workaround: Press F5 to refresh CapacityIQ.

  • If you apply an update using the ciq-admin command-line interface, the build number in the Administration Portal header might not match the build number on the Status tab.

    Workaround: Press F5 to refresh the Administration Portal. When the Administration Portal logs you out, you can log in to the portal.

  • 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.

    This issue affects the numbers on the following pages:

    • Dashboard
      • VM Memory Consumed - this number is slightly higher because CapacityIQ adds ESX memory overhead.
      • Total VM Memory Remaining - this number is slightly lower because CapacityIQ subtracts ESX memory overhead.
    • Virtual Machine Capacity Usage - Trend view
      • VM Memory Consumed - this number is slightly higher because CapacityIQ adds ESX memory overhead.
  • On some CapacityIQ pages, the client shows an Error loading view message. CapacityIQ uses an Internet Explorer browser control for rendering its pages. This message might appear 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, 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 CapacityIQ reloads the data. 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.

Top of Page