VMware vCenter Support Assistant 5.5.1 Release Notes
vCenter Support Assistant 5.5.1 | 27 May 2014 | Build 1828479
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
This release of vCenter Support Assistant 5.5.1 includes a number of bug fixes that have been documented in the Resolved Issues section.
Earlier Releases of vCenter Support Assistant
Features and known issues of vCenter Support Assistant are described in the release notes for each release. Release notes for earlier releases of vCenter Support Assistant 5.5 are:
vCenter Support Assistant 5.5.1 is tested for the following environment:
- 5 vCenter Server instances
- 1000 ESXi hosts
- 15000 Virtual machines
vCenter Support Assistant is distributed as a virtual appliance, which is 678MB in size.
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
vCenter Support Assistant 5.5.1 works with vSphere 5.1 and vSphere 5.5.
vCenter Support Assistant 5.5.1 supports vCenter Server 5.1, vCenter Server 5.5, ESXi 5.0, ESXi 5.1, and ESXi 5.5 and can be used only with the vSphere Web Client.
vCenter Support Assistant 5.5.1 works with Microsoft Internet Explorer, Google Chrome, and Mozilla Firefox with the latest version of Adobe Flash Player.
vCenter Support Assistant 5.5.1 can run on a non-English OS but does not accept non-English characters as input and is not localized.
- When you attach logs to a support request, log collection from some hosts might fail, returning an authentication error
When you collect logs from ESXi 5.1U2 hosts, the collection task might fail and result in an authentication error:
Collection log support bundles from the following hosts failed:
<ESXi Host> (host-download-failure=reason-code.authentication-error)
For additioal information, see VMware vCenter Support Assistant 5.5 unable to collect/upload logs from an ESXi 5.1.x host (KB 2076185).
This issue has been fixed for this release.
- Logs for wrong ESXi hosts and vCenter Server instances are uploaded to support request
When you try to upload logs to a support request, logs from wrong vCenter Server instances or ESXi hosts are collected and uploaded to the support request. In addition, occasionally loading the system log categories fails with the following message: No system logs loaded. You might encounter this problem when the vSphere Web Client inventory contains more than one vCenter Server instance. vCenter Support Assistant collects logs correctly only for one of the vCenter Server instances. Attempts to collect logs from the remaining vCenter Server instances and the hosts they manage result either in collection of the wrong logs, or in failure to load system log categories.
For more information, see Uploading logs through VMware vCenter Support Assistant when using more than one vCenter Server in the inventory fails with error: No available manifests (KB 2075584)
This issue has been fixed for this release.
- 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.
- 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.
Workaround: Configure the Date/Time settings again.
- 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.
- 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.
- Navigate to the IP address of the vCenter Support Assistant appliance in a Web browser: http://your_vcenter_support_assistant_appliance_IP.
- On the Proxy tab, verify that the proxy settings are correct.
- 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:
- Log in to the vSphere Web Client.
- On the Home page, click vCenter Support Assistant.
- On the Manage tab, click Proactive Support.
- 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.