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

Static IPset not reported to containerset API call in NSX-v (57834)

Last Updated: 9/29/2018Categories: TroubleshootingTotal Views: 3823Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After installing NSX for vSphere 6.3.6, 6.4.1 or 6.4.2 or upgrading from previous versions to NSX for vSphere 6.3.6, 6.4.1 or 6.4.2, when an API call is made by a third party Service Insertion solution to NSX Manager to retrieve all the Static IP sets configured as part of Service Insertion, you see these symptoms:

The NSX Manager returns an empty config for IPSets or SecurityGroups containing IPSets. As a result, IPSets or SecurityGroups containing IPSets are reported empty to the third party Manager.

The guest VMs protected by PAN or other third party firewall devices would drop the traffic as no rules match and hit default deny rule.

Running the API call https://NSXMGR_IP/api/2.0/si/serviceprofile/serviceprofile-10/containerset/ does not return any IPs for IPSets or SecurityGroups containing IPSets.

For example:

"container": [
{
"id": "securitygroup-16",
"vsmUuid": "42080AD5-D890-04C9-31C2-8A457C5588ED",
"name": "Test-Container",
"description": null,
"revision": 11,
"type": "IP",
"generationNumber": 0,
"address": [], <<<< empty
"nicNodes": null,
"universal": false
},

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.3, available at VMware Downloads.

Workaround

To work around this issue, contact VMware Support and note this Knowledge Base article ID (57834) in the problem description. To contact VMware support, see Filing a Support Request in Customer Connect (2006985) or How to Submit a Support Request.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
将许可证升级到 VMware vRealize Operations for VMware Horizon 6.0 (2095210)

KB
•
确定 ESXi 主机关闭电源或重新启动的原因 (1019238)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant