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

Floating IP Pool exhausts rapidly in VMware Enterprise PKS 1.4.x (71354)

Last Updated: 7/16/2020Categories: TroubleshootingTotal Views: 14279Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When you create a PKS cluster in fresh deployment, you see that many IPs from Floating IP pool were used immediately.

After some time, all the IPs were exhausted even though you didn’t use them for any cluster or service.

If you try to deploy a new cluster/service, it fails with error similar to:
ncp/error.loadbalancer: IP_POOL_EXHAUSTED

In the NSX-T edge syslog, you see the error similar to:
“[NAT] NAT action SNAT is NOT supported on the HaMode ACTIVE_ACTIVE of Logical Router 790a637f-3cdf-45cc-a2f8-758c74c7bde5.”

Cause

This issue occurs if you configure the T-0 router in Active-Active mode in edge cluster. Currently PKS does not support SNAT namespaces when the T0 is Active-Active.

One reason why the IpPool is getting exhausted is that it is possible that the SNAT IP are not getting released on above namespace related failures and every retry of namespace creation exhausts another IP address.

Resolution

To resolve this issue, release the floating IPs and configure the T0 on Active-Standby mode:

Release the floating IPs which are used by Virtual Servers and NAT rules.

List all the floating IP allocations by running the command:
curl -X GET -H Content-Type:application/json -H X-Allow-Overwrite:True -ku Username:Password https://NSX-T_Manager_IP/api/v1/pools/ip-pools/Floating-IP-Pool-ID/allocations
Example:
curl -X GET -H Content-Type:application/json -H X-Allow-Overwrite:True -ku admin:VMware1! https://192.168.110.42/api/v1/pools/ip-pools/700e436d-4c49-4e16-bc84-ec8f1baaa273/allocations

Release the Floating IP stale entries by running the command:
curl -X PUT -H Content-Type:application/json -H X-Allow-Overwrite:True -ku Username:Password https://NSX-T_Manager_IP/api/v1/pools/ip-pools/Floating-IP-Pool-ID?action=RELEASE’ -d ‘{“allocation_id”:”IP_Address″}’
Example:
curl -X PUT -H Content-Type:application/json -H X-Allow-Overwrite:True -ku admin:VMware1! https://192.168.110.42/api/v1/pools/ip-pools/700e436d-4c49-4e16-bc84-ec8f1baaa273?action=RELEASE’ -d ‘{“allocation_id”:”10.0.80.11″}’

Configure the T0 router in Active-Standby mode.

Restart NCP service on K8S Primary nodes.

Related Information

In NCP 2.5.0, we release the SNAT IP when the SNAT rule creation for namespace fails. Hence, IP pool will not get exhausted in NCP 2.5.0

However, you still need to use Tier-0 router in Active-Standby mode only.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
对文件 /opt/vmware/vcloud-director/data/transfer 解压存档失败：cpio：chown (71340)

KB
•
使用 Cohesity 保护 vCloud Director 环境 (71326)

KB
•
新しいプロバイダ VDC を作成するときに、ストレージ ポリシーが表示されない (71321)

KB
•
尝试通过 api 删除计算机前缀时出现错误“400 错误请求 (400 bad request)” (71344)

KB
•
Usage Meter 无法完成 vROPS 配置 (71305)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant