Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

VMware Support for Partner management integrations through vSphere and NSX-T Public APIs (57780)

Last Updated: 6/27/2023Categories: InformationalTotal Views: 48314Language:
English

76 like this article

Subscribe to get an email
newsletter with new updates

76 people found this helpful Please provide article feedback:

Purpose

This article provides clarification on VMware Support for Partner Switches integrated through vSphere and NSX-T Public APIs.

Resolution

VMware support desires a demarcation point to effectuate changes on the distributed switch without affecting other infrastructure switching and connectivity. This demarcation point is required to avoid causing a customer to experience a distorted configuration between the vSphere distributed virtual switch and the control and data planes of a partner switch when manipulating the distributed switch to troubleshoot issues. Most automation tools do not create a configuration link between the vSphere distributed switch and the physical switches.

In cases where there is no clear demarcation line,* VMware will require the following two steps to troubleshoot or manage issues related to vSphere, NSX-T, or NSX environments. VMware will request the creation of an environment free of the partner component in question** for troubleshooting purposes per the support policy for third-party integrations. https://www.vmware.com/support/policies/thirdparty.html.

·     If the issue is reproducible without the partner component, VMware will support and investigate as normal.
·     If the issue is not reproducible after removing the partner component, VMware will not investigate further. At this point, Customer Support at the partner should be contacted.

*One such partner integration that has no clear demarcation point is the Cisco ACI VMM integration and other related Cisco ACI integrations leveraging the vSphere and NSX-T APIs. Due to the operational nature this integration, VMware will require the steps described above to troubleshoot the issue.
**for example, the Cisco ACI VMM

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESX

VMware vSphere

VMware vCenter Server

Related Versions:

VMware NSX-T

Take Our Survey

Support Assistant