VMware

VMware vCenterTM AppSpeed 1.5 Release Notes

VMware vCenter AppSpeed 1.5 | 15 September 2010 | Build 49657

Last Document Update: 05 Sep 2010

These release notes cover the following topics:

VMware vCenter AppSpeed 1.5 Features

VMware vCenter AppSpeed provides proactive performance management and service-level reporting for services running within virtual appliances. By analyzing the traffic that flows between end users, Web applications, and back-end servers, AppSpeed provides visibility into multitier services and enables rapid identification of performance issues originating from inadequate resource allocation and service problems.

The new AppSpeed features include:

  • In the main vSphere Client interface, a new Services tab appears after you install AppSpeed.
    • The Services tab provides an intuitive AppSpeed starting point in the familiar vSphere Client interface.
    • The content shown in the Services tab focuses on vSphere inventory objects, with a service overlay.
  • You can now access the AppSpeed user interface from Web browsers.
  • The AppSpeed user interface has been redesigned to meet the needs of vSphere administrators.
    • The new Overview portal provides high level information about the health of the monitored environment.
    • A Summary view is provided for each service and server that is monitored by AppSpeed.
    • Clear, intuitive performance analysis is accessible through drill down views.
    • Topology management has been redesigned and the topology map has been removed.
  • You can view a side-by-side comparison of vCenter Key Performance Indicators (for example, CPU, memory, and disk I/O) with AppSpeed performance indicators (for example, latency and errors).
    • You can quickly identify whether performance issues are related to services or underlying virtual machine resources.
    • You can customize how the AppSpeed and vCenter KPIs are displayed.
  • AppSpeed can automatically generate health indicators (SLAs) for services and servers, based on monitored response times.
  • Installation has been simplified and distributed virtual switch support is provided “off the shelf”.

Other VMware vCenter AppSpeed 1.5 Documentation

VMware vCenter AppSpeed Installation and Upgrade Guide

VMware vCenter AppSpeed User's Guide

System Requirements for VMware vCenter AppSpeed 1.5

AppSpeed is supported for the following ESX and vCenter versions:

  • Probes: ESX 3.0x, 3.5x or 4.x Server: ESX 3.5x or 4.x
  • vCenter 4.0, 4.1
  • In addition, the successful installation of the AppSpeed virtual appliance and plug-in, and the deployment of the probes, requires that the following prerequisites be met:

    • Administrator privileges on vCenter Server, for the installation process
    • SSL private keys for HTTPS sites that AppSpeed is to monitor
    • Administrator privileges on the vSphere Client machine, to install Adobe Flash Player 10

    The following system resource requirements must be met:

    • Server
    • 40GB HDD
    • 4GB RAM
    • 2 vCPUs
    • Probes
    • 5GB HDD
    • 0.5GB RAM
    • 2 vCPUs
      Note: Virtual CPUs are created as part of the AppSpeed probe deployment. Two vCPUs require no more than the equivalent resources of a single physical CPU because AppSpeed configures resource limits to ensure that no more resources than are available on one physical CPU are required at any time.

    Web Interface Support

    Supported Web browsers:

    • Internet Explorer 7
    • Internet Explorer 8
    • Google Chrome
    • Mozilla FireFox 3.6

    Installation Notes

    Upgrading to AppSpeed 1.5

    You can upgrade from AppSpeed 1.2 and AppSpeed 2010 Beta to AppSpeed 1.5.

    To upgrade to AppSpeed 1.5

    1. Download the AppSpeed 1.5 ISO file and save it to a location on your local disk.
    2. In the vSphere Client, connect AppSpeed Server to the ISO file.
      1. Select the AppSpeed Server virtual machine in the vSphere Client inventory tree.
      2. Click the Connect CD/DVD devices icon and select Connect to ISO image on local disk from the menu.
      3. Browse to the location of the ISO file.
    3. Log in to the AppSpeed Server console as the console user.
    4. From the default console shell, run the command upgrade_AppSpeed.
    5. Press Enter to run the upgrade script.
      After AppSpeed Server boots from the ISO image, it continues the upgrade process, including rebooting and recreating the probes. This process can take several hours.
      A message appears when the AppSpeed Server upgrade is complete.
    6. When prompted, disconnect the ISO file in the vSphere Client.
      The probes are recreated in the new version. You can monitor the redeployment process from the AppSpeed Probes Deployment window.

    After the upgrade is complete, restart the vSphere Client and verify the redeployment of the probes.

    Upgrading from VMware vCenter AppSpeed 1.2

    When you upgrade from AppSpeed 1.2, VMware recommends that you perform a state reset to avoid conflicts resulting from the new algorithms and the monitoring mechanism. Note that the state reset also clears the AppSpeed history and collected data.

    Known Issues with VMware vCenter AppSpeed 1.5

    Server Installation

    • You can only monitor the vCenter environment on which AppSpeed Server is installed. Similarly, with linked vCenter environments, each environment must have an AppSpeed Server installed so that it can be monitored.
      AppSpeed Server must reside on the vCenter on which monitoring is to be performed.
    • You cannot specify the vCenter name in setup. You must specify the vCenter IP address.
    • Harmless FAILED messages are displayed when starting up an AppSpeed machine.
    • In rare cases, AppSpeed Server starts up without a network connection meaning that the "Connect" check box is not selected in the virtual appliance settings, and there is a blank network label.
      Manually select the network label and the Connect check box.

    Upgrading

    • Upgrading AppSpeed from 1.2 removes all root and local internal password settings for AppSpeed virtual appliances.
      If you specified a password for an AppSpeed virtual appliance, you must respecify it following the upgrade.
    • AppSpeed VMware Tools are not upgraded in this version and might appear as out of date.
      This has no effect on AppSpeed. AppSpeed Server does not allow upgrade of tools in this version.
    • Some VMware Tools services do not start automatically after an upgrade.
      Start the Tools services manually.
    • Following upgrade, monitoring data is unavailable for pre-existing SQL services until the servers on which the services are running are remapped.
    • Following upgrade, Exchange service is removed.
    • When you upgrade from AppSpeed 1.2 and your topology includes the Outlook Offline Address Book Web service, the service must be manually remapped to enable monitoring.
      In the Topology Management page of the Mapping module, select the service and click Remap.

    Probe Deployment

    • Sufficient disk space is not automatically verified before deploying probes.
      During probe deployment, when there is insufficient disk space for the probes, an internal error message is displayed and the Recent Tasks pane displays Insufficient disk space.
    • An AppSpeed probe template snapshot is automatically created for probe deployment.
      You can remove the snapshot at any time. VMware recommends that you delete the snapshot after the initial probe deployment is complete.
    • After a probe is deleted, its directory sometimes remains in the datastore.
      The deleted probe's directory and contents can be removed.
    • In vSphere, if you use the Enable individual virtual machine automation levels feature, the AppSpeed probe is not attached to the host, and is subject to VMware Distributed Resource Scheduler and VMware High Availability. The probe might move if automatic migration using vMotion occurs, in which case the probe is not be able to monitor the correct traffic.
    • In vSphere, if you disable the Enable individual virtual machine automation levels feature for a cluster, the probes' coverage of traffic can be unpredictable.
    • In some cases, the Failure due to malformed requests from the server message appears when probe deployment fails.
      Delete the failed probe and redeploy it. If the probe deployment freezes, restart AppSpeed from the server console and try again.
    • If probe deployment fails, you might have to manually remove the temporary linked-clone virtual machine that was created during the deployment process.
    • Probe deployment might fail during multi-probe deployment, with the following error: Operation is not allowed in the current state.
      Delete the probe and deploy a new one.
    • If a probe deployment fails, the failed probe is not automatically deleted.
      Select the probe in the Deployment page of the Administration module and click Delete Probe.
    • Distributed Power Management (DPM) might not work on hosts that contain AppSpeed probes.
    • Multiple AppSpeed probes that are installed on a single host can result in inaccurate mapping and monitoring data when you try to monitor multiple distributed virtual switches.

    User Interface

    • For optimal viewing of AppSpeed, open AppSpeed in a Web browser. Alternatively, use a screen resolution higher than 1024 by 768 for viewing AppSpeed, and close the vSphere Client Recent Tasks pane.
      Note that a 1024 by 768 screen resolution is also supported in most scenarios.
    • The list of virtual machines and services displayed by AppSpeed reflects the current mapping status, regardless of the selected time frame. Topology history is not saved.
    • In some cases, you cannot save export data in CSV format.
      Ensure that the file name has a .csv extension specified.
    • In some cases, limited functionality might occur related to time frame selection. For example, time prior to AppSpeed Server installation cannot be selected.
      Specify a time frame as close as possible to the time frame you want to display.
    • If you connect to the AppSpeed user interface for the first time using a port other than port 80, an error is returned.
      In the vSphere Client, go to Administration > vCenter Server Settings > Ports and change the HTTP port value to 80, or run vcenter_settings and specify the port setting that you are using.
    • If you attempt to run a search while other search results are being loaded, the search function stops working.
    • In the vSphere client, an AppSpeed Server tab continues to be displayed after the AppSpeed Server has been deleted.
    • When the name of a virtual machine that you delete contains non-ASCII characters, an error message is displayed.
      The virtual machine is deleted. The error message can be ignored.

    Mapping

    • SSL connections that use the Diffie-Hellman key-exchange algorithm are not monitored. In the case that only the Diffie Hellman key-exchange algorithm is used by a service or transaction, that service or transaction is not mapped.
    • During the mapping process, object names might change several times.

    Interoperability

    • IP address changes might compromise AppSpeed Server operations (changes due to DHCP, or any other cause).
      If the AppSpeed Server IP address changes, manually delete all probes from the vCenter inventory, run setup in the AppSpeed Server console and redeploy the probes. All data and history are lost.
    • AppSpeed Server time is synchronized with the ESX host.
      VMware recommends that you synchronize the AppSpeed Server ESX host using NTP, to maintain consistent time. If AppSpeed Server is installed in a cluster, and is subject to VMware Distributed Resource Scheduler, ensure that all hosts in the cluster are synchronized using NTP.
    • If AppSpeed Server time is not synchronized, gaps might be encountered in the data monitored by the AppSpeed probes.
    • When you use vMotion to migrate an AppSpeed Server to hosts with different time settings, time jumps might occur in the AppSpeed Server.
      The time jumps might result in inaccurate monitoring data for that time. If time moves backward, some data are erased. If time moves forward, a gap occurs in the monitoring data.
    • In rare instances, the AppSpeed Server might incorrectly determine that traffic is being monitored by a probe other than the one that is actually performing the monitoring.
      To avoid this situation, ensure that none of the management port groups or monitored vSwitches for any of the probes are in Promiscuous mode.
    • If you upgrade vCenter Server from 4.0 to 4.0.1, you must rerun setup from the console before you can connect to the user interface.
    • There might be a gap of up to two minutes between the timestamp of data in the performance view of vSphere and the vCenter performance indicators displayed in AppSpeed.

    General

    • AppSpeed does not map and monitor servers or services that use IPv6.
    • Deleting probes leaves the dedicated AppSpeed port group on the host, even after the last probe that uses the port group is removed.
      You can manually remove the port group.
    • There is no progress bar for the Delete Probe, Power On, and Power Off actions in the Deployment page of the Administration module.
      Although it takes time for the actions to complete, it appears as if an action was performed immediately. You can monitor the actions in the vSphere Client Recent Tasks pane.
    • In rare cases, the virtual machine's disks of AppSpeed Server or an AppSpeed probe might become read-only. When you connect to the virtual machine console, a Read-only file system message appears.
      • If the virtual machine disks reside on a network-attached datastore, verify that the datastore is available.
      • Attempt to restart the relevant virtual machine.
        If the restart attempt is unsuccessful; in the case of an AppSpeed probe virtual machine, delete and redeploy the probe. In the case of an AppSpeed Server virtual machine, delete all the probes, reinstall AppSpeed Server, and redeploy the probes.
    • If an AppSpeed Server virtual machine has insufficient disk space, you might be unable to connect to the AppSpeed Server user interface.
      1. Delete any AppSpeed Server snapshot.
      2. Log in to the console. If the disk is full, a message is displayed. Follow the instructions in the console.
    • The status of a probe might be Down in the Deployment page of the Administration module, even though it receives traffic.
      Restart the relevant probe, either by restarting the probe's virtual machine, or by logging in to the probe's virtual machine console and restarting AppSpeed.
    • Harmless FAILED messages might indicate that the Guest memory manager, and Guest vmxnet fast network device VMware Tools failed to start.
      VMware Tools load successfully. The messages can be ignored.
    • In the event that AppSpeed Server is restarted following an unexpected shutdown, the AppSpeed Server internal database might become corrupt.
      Run setup on AppSpeed Server.
    • If an AppSpeed Server is migrated using vMotion, AppSpeed Server might need to be restarted.
    • Virtual machines that have an identical IP address in the vCenter environment cannot be monitored by AppSpeed.
    • The following issue might arise when entering Maintenance mode on an AppSpeed Server host located on a network-attached datastore. The virtual machine does not migrate automatically when a AppSpeed Server virtual machine snapshot exists.
      Remove the snapshot and try again.
    • If a host is removed from the vCenter environment while it is in Maintenance mode, and then reloaded, probes that were originally deployed on the host might no longer remain on that host, and will be powered off.
      Delete the original probe and deploy a new one on the host.
    • When you enter Maintenance mode on a host that has a probe deployed, the probe is powered off and moved to another host. If the probe is manually powered on, it might result in inaccurate monitoring data.
    • AppSpeed is not compatible with VMware Site Recovery Manager.
    • After you update an SSL key certificate, verify that the probes are detecting traffic. If traffic is not detected, restart the relevant probe.