Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Collecting diagnostic information for VMware Infrastructure SDK (1001457)

Last Updated: 1/9/2014Categories: Best PracticesTotal Views: 17066Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

IMPORTANT: This article is updated for the SFTP release, due on January 24th, 2014. Do not republish the article until the release.

VMware Technical Support routinely requests diagnostic information from you when a support request is handled. This diagnostic information contains product-specific logs and configuration files from the host on which the product is run. The information is gathered using a specific script or tool for each product.

This article provides procedures for obtaining diagnostic information for VMware vSphere SDKs.

The diagnostic information collected can then be uploaded to VMware Technical Support. To uniquely identify your information, use the Support Request (SR) number you received when you opened your Support Request.

For more information, see:

Opening a Support Request

Uploading diagnostic information to VMware (1008525)

Collecting diagnostic information for VMware products (1008524)

Solution

If you have critical production-related issues, call the VMware support hotline.

All nonproduction support requests are handled through email. Allow up to 48 hours for a response. Submit one support request per issue.

For additional information, see the VMware SDK Support Policy: http://www.vmware.com/support/policies/sdk.html. These instructions apply to:

VMware Infrastructure SDK version 2.5.

vSphere Web Services SDK 4.0 and later.

vSphere PowerCLI 4.0 and later.

VMware Infrastructure Perl Toolkit version 1.0 or later.

vSphere SDK for Perl 4.0 and later.

vSphere vCLI 4.0 and later.

CIM SDK SMASH and SMI-S and Guest SDK

Creating an SDK Support Request

To file an SDK support request:

Ensure that the error was captured in the log files.

Note the approximate time of the error.

Collect the required diagnostic files and information.

Three sets of data are needed to properly diagnose your VMware Infrastructure SDK issue:

SDK related information: Complete the SDK support form. See 1001457_VMware_SDK_Support_Form.zip, attached to this article.

ESX Server related information: Collect ESX Server files. For more information, see Collecting diagnostic information for VMware products (1008524).

VirtualCenter related information: Collect the VirtualCenter files. For more information, see Collecting diagnostic information for VMware products (1008524).

Create and submit the Support Request. For more information, see Filing a Support Request in Customer Connect (2006985).

Upload the diagnostic files to the VMware SFTP/FTP site. For more information, see Uploading diagnostic information to VMware (1008525).

Collecting SDK Related Data

All the SDK-related information needed to evaluate your support request and help diagnose your problem is listed in the VMware SDK Support Form.

Download and save the VMware SDK Support Form. See 1001457_VMware_SDK_Support_Form.zip, attached to this article.

Complete the form, providing as much detail about your computing environment as possible. Attach a complete code example that demonstrates the problem, with exact errors and screenshots if possible.

Upload the completed form with your support request.

Collecting ESX Server Related Data

For information about obtaining diagnostic information for ESX Server, see Collecting diagnostic information for VMware products (1008524).

Collecting VirtualCenter Related Data

For information about obtaining diagnostic information for VirtualCenter, see Collecting diagnostic information for VMware products (1008524).

Set the logging option to Trivial to ensure that all information is collected and includes time stamps.

Send the script-collected files with your support request.

Enhancing the Logs that are Captured
Some issues require that you submit log files by using an enhanced capture level.

Set logs to Trivial for hostd when collecting files in ESX Server:

On each host, open the hostd configuration file for editing:

/etc/vmware/hostd/config.xml

Set the <level> tag to trivia mode. For example:

<log>
<level>trivia</level>
</log>

Restart management services with the first command on ESX, or the second command on ESXi:

service mgmt-vmware restart
/sbin/services.sh restart

Set logs to Trivial for vpxa when collecting files in ESX Server:

On each host, open the vpxa configuration file for editing.

Note: This file is /etc/opt/vmware/vpxa/vpxa.cfg, or /etc/vmware/vpxa.cfg before ESX 3.5.

Set the <level> tag to trivia mode. For example:

<log>
<level>trivia</level>
</log>

Restart the vpxa management agent with the first command on ESX, or the second command on ESXi:

service vmware-vpxa restart
/sbin/services.sh restart

Set logs to Trivial when collecting files in VirtualCenter. For Virtual Center, you can use the VI Client to configure the amount of detail that VirtualCenter collects in log files:

Connect the VI Client to the VirtualCenter Server. Go to Administration > Server Settings and select Logging Options.

Configure the level of detail for log files. From the VirtualCenter Logging list, choose Trivia (Extended verbose) and click OK.

Set all the clocks in the systems (VI Client, VirtualCenter, ESX Server, and so on), to the same time. If you cannot synchronize all of the system clocks, note any difference between the clocks of the different systems.

Reproduce the error.

Record the time the error occurs.

Capture the logs.

Debugging Tips

These are some best practices for debugging code when using VMware Infrastructure APIs:

Generate complete logs with as much detail as possible including time stamps. Provide case samples of successful completions and failures with time stamps.

Submit code samples that are as self-contained as possible and reproduce the problems.

Use the VMware Infrastructure Perl Toolkit to reproduce problems found when you use VM Perl.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

1001487_VMware_SDK_Support_Form.zip

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

VMware Infrastructure SDK

Related Versions:

VMware vCenter Server 4.0.x

VMware Infrastructure SDK 2.0.x

VMware Infrastructure SDK 1.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant