VMware

VMware vCenter Support Assistant 6.0 Release Notes

vCenter Support Assistant 6.0 | 9 April 2015| Build 2632669

Last Document Update: 9 April 2015

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

What's New in vCenter Support Assistant 6.0

vCenter Support Assistant 6.0 introduces usability improvements in the proactive support workflow that help you resolve the identified potential problems faster.

  • KB articles hyperlinks. When you receive a vCenter Support Assistant alarm for an inventory object, select the inventory object, click Monitor, and click the Issues tab. In the Support Assistant Issues tab, a list displays the potential problems that vCenter Support Assistant has found for the selected inventory object. The details for each issue link to the KB article that can help you resolve the problem.
  • Ability to disable a Support Assistant issue. If you want to ignore a Support Assistant issue for a known problem in your environment, you can now disable the issue and suppress future alarms for the selected issue.
  • Localization. The vCenter Support Assistant 6.0 release is the first localized release. For more information, see Internationalization Support.
  • IPv6 support. You can install and run vCenter Support Assistant 6.0 in an IPv6 environment.
    Note: VMware endpoints are IPv4 addresses.

Top of Page

Earlier Releases of vCenter Support Assistant

vCenter Support Assistant has the following releases:

  • vCenter Support Assistant 5.5.1.1
  • vCenter Support Assistant 5.5.1
  • vCenter Support Assistant 5.5

Top of Page

Upgrade to vCenter Support Assistant 6.0

Support Assistant 6.0 adds internationalization and localization support. This requires additional configurations to be performed after the appliance is updated to the latest version. The upgrade procedure consists of the following steps:

  1. Install the update from the VA Updates tab of the vCenter Support Assistant appliance.
  2. Log in to the vSphere Web Client and restart the vCenter Support Assistant appliance.
  3. In the Overview page of the vCenter Support Assistant appliance, start the Reinstall wizard and follow the steps.
    For more information, see Installing and Configuring vCenter Support Assistant 6.0 guide.

Top of Page

Scalability

vCenter Support Assistant 6.0 is tested for the following environment:

  • 5 vCenter Server instances
  • 1000 ESXi hosts
  • 15000 Virtual machines

Top of Page

System Requirements

vCenter Support Assistant is distributed as a virtual appliance, which is 678MB in size.

Hardware Requirements

You can run vCenter Support Assistant on any system that meets the minimum hardware requirements.

Minimum hardware requirements for vCenter Support Assistant vary depending on the number of vCenter Server instances and ESXi hosts for which vCenter Support Assistant will collect data.

  • 2 vCPU
  • 2GB vRAM
  • Minimum 65GB. The disk space is calculated by the equation:
    Disk space = 50GB + number of vCenter Server instances * 300MB + number of ESXi hosts*50MB

Interoperability

vCenter Support Assistant 6.0 works with vSphere 5.1, vSphere 5.5, and vSphere 6.0

vCenter Support Assistant 6.0 supports vCenter Server 5.1, vCenter Server 5.5, vCenter Server 6.0, ESXi 5.0, ESXi 5.1, ESXi 5.5, and ESXi 6.0 and can be used only with the vSphere Web Client.

vCenter Support Assistant 6.0 works with Microsoft Internet Explorer, Google Chrome, and Mozilla Firefox with the latest version of Adobe Flash Player.

Top of Page

Internationalization Support

vCenter Support Assistant 6.0 is localized and can run on a non-English OS.

vCenter Support Assistant 6.0 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Top of Page

Resolved Issues

This section contains resolved issues since vCenter Support Assistant 5.5.1.1 release.

  • The Date and Time settings might be displayed incorrectly when you set them for the first time
    Because of a problem in the date and time calculation logic related to time zones and daylight saving time, the first time you configure the collection Date and Time setting in the vCenter Support Assistant plug-in, the settings displayed after the operation might differ from the settings that you entered usually by one hour, or whatever the DST offset is.

    This problem is fixed.

Top of Page

Known Issues

This section contains known issues for the current release.

  • Missing alarms
    After update to vCenter Support Assistant 6.0 the existing vCenter Support Assistant alarms disappear from the UI.

    Workaround: none.

  • The schedule of support bundles collection does not automatically adjust to Daylight Savings Time (DST)
    After a DST time change, the support bundles collection starts one hour earlier or one hour later than configured, depending on the direction of the DST change. You can see the time of the next support bundles collection in the Manage > Proactive support tab. The schedule is also one hour ahead or behind the current DST.

    Workaround:Configure the schedule for support bundles collection after each DST change.

  • Attempts to attach a file from your local system to the Support Request, result in error
    When you open the vSphere Web Client in Mozilla Firefox and attempt to attach a file from your local system to the Support Request, and your vSphere Web Client is loaded in Mozilla Firefox, you might receive an error message #2038. This error forces you to reload the application and prevents you from attaching the file. The upload functionality does not work with Mozilla Firefox browser.
    Workaround: Use Internet Explorer or Google Chrome with the latest Adobe Flash player plug-in installed. The latest Adobe Flash player plug-in version that the upload functionality officially supports is version 11.7.700.255.

  • Attempts to schedule a support bundles collection at a time between 12:00 and 24:00 using a 24-hour notation, do not give the expected results
    If your local machine uses a 24-hour time notation format and does not support AM and PM specifiers in the regional options, you might be unable to use vSphere Web Client 5.5 to schedule a collection for an hour greater than 1200. The hour counter is reduced by twelve hours.

    Workaround: Configure the collection schedule on a machine that uses a 12-hour notation time format.

  • An exception message might be displayed on the Monitor tab of the vCenter Support Assistant plug-in
    Network problems between the vCenter Support Assistant appliance and the VMware Web site might cause an exception message to be displayed in the vSphere Web Client. The message appears on the Monitor tab of the vCenter Support Assistant plug-in.

    Connectivity problems:

    • https://vmware.com server downtime.
    • vCenter Support Assistant Appliance is disconnected from https://vmware.com. The VMware Production server address is https://vcsa.vmware.com.

    Workaround: Verify that the proxy settings are correct and the connectivity test succeeds.

    1. Navigate to the IP address of the vCenter Support Assistant appliance in a Web browser: http://your_vcenter_support_assistant_appliance_IP.
    2. On the Proxy tab, verify that the proxy settings are correct.
    3. Click Test connectivity to verify that the settings are correct.

  • After you click the Configure log gathering and collection settings link on the Configure tab of the vCenter Support Assistant Web console, you are not redirected to the vCenter Support Assistant plug-in
    When vCenter Support Assistant is configured to work with a vSphere Web Client instance, installed on a Microsoft Windows operating system that does not have a resolvable FQDN, the link to the vCenter Support Assistant plug-in location in the vSphere Web Client does not work.

    Workaround: Navigate to the vCenter Support Assistant plug-in of the vSphere Web Client to configure the log gathering and collection settings:

    1. Log in to the vSphere Web Client.
    2. On the Home page, click vCenter Support Assistant.
    3. On the Manage tab, click Proactive Support.
    4. Click Edit and configure the log gathering and collection settings as appropriate.

  • The vCenter Support Assistant UI might stop responding or might display an error

    Because of an overload of the vCenter Support Assistant appliance, the vCenter Support Assistant service cannot process the UI requests in a timely manner. The overload might occur if the vCenter Support Assistant appliance has insufficient resources.

    Workaround: There are two ways to solve this problem:

    • Wait for 15-20 minutes and reload vCenter Support Assistant UI.
    • Change the vCenter Support Assistant hardware configuration to use 2 CPUs and 4GB RAM, and restart the vCenter Support Assistant appliance.

  • The Edit buttons on the Proactive support subtab of the Manage tab in the vCenter Support Assistant plug-in might disappear
    Because of connectivity problems between vCenter Server and the vCenter Support Assistant appliance, the Edit buttons on the Proactive support subtab of the Manage tab might disappear. As a result, you cannot configure any collection settings.

    Workaround: Log out of the vSphere Web Client and log in again.

  • The attaching large files from a local file system operation is not completed successfully
    If you attempt to attach large files to a support request, you might receive an error message, similar to the following:
    An error uploading files occurred. Please check the connectivity between your machine and the Support Assistant Appliance.
    This issue occurs because the Java Virtual Machine of the appliance does not have enough free memory.

    Workaround: To upload a large amount of data successfully, split the files into smaller pieces with a maximum size of approximately 200MB. If the problem persists and the upload is still not successful, restart the vCenter Support Assistant Appliance.

Top of Page