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

NSX Edge Load Balancing fails when the VIP contains TCP port range from 10000-64000 (53006)

Last Updated: 3/3/2018Categories: Best PracticesTotal Views: 6666Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In an environment where a Load Balancer Virtual Server IP contains TCP port range covering 10000-64000, you see these symptoms:

Load Balancing fails.

In the Load Balancer logs, you see entries similar to:

loadbalancer[8626]: [default]: Connect() failed for backend pool-test: no free ports.

Cause

Ports 10000-64000 are used by the Linux OS Kernel for several services such as HA proxy health check monitor, routing Service, HA rsync, etc. In addition, NSX Load Balancers use ports in this range to initiate connections to back-end pool members.

For example:

[root@NSX-edge-1-0 /var/db/vmware/vshield]# cat /proc/sys/net/ipv4/ip_local_port_range
10000 64000

When a VIP is configured for all port ranges from 10000-64000, it creates a network socket (IP Address/Port Bind) for the VIP IP with all the ports in this range.

For example:

[root@NSX-edge-4-0 ~]# netstat -anp | less
tcp 0 0 172.16.10.10:62343 0.0.0.0:* LISTEN 2311/haproxy
tcp 0 0 172.16.10.10:62311 0.0.0.0:* LISTEN 2311/haproxy
tcp 0 0 172.16.10.10:62279 0.0.0.0:* LISTEN 2311/haproxy

A total of 54000 sockets are created covering the full local port range.

For example:

[root@NSX-edge-4-0 ~]# netstat -anp | grep 172.16.10.10: | wc -l

54002

From the output below, the Pool Members have been marked down since there are no available ports in the Edge to initiate connections to the backend pool members hence the issue occurs.

For example:

NSX-edge-4-0> show service loadbalancer pool
-----------------------------------------------------------------------
Loadbalancer Pool Statistics:

POOL Web-Tier
| LB METHOD leastconn
| LB PROTOCOL L7
| Transparent disabled
| SESSION (cur, max, total) = (1, 2, 35)
| BYTES in = (4704), out = (8520)
+->POOL MEMBER: Web-Tier/Web-01_172.16.10.11, STATUS: DOWN
| | HEALTH MONITOR = BUILT-IN, default_https_monitor:L4CON
| | | LAST STATE CHANGE: 2018-02-28 17:30:10
| | | FAILURE DETAIL: Out of local source ports on the system
| | SESSION (cur, max, total) = (0, 1, 3)
| | BYTES in = (1488), out = (5112)
+->POOL MEMBER: Web-Tier/web-02a_172.16.10.12, STATUS: DOWN
| | HEALTH MONITOR = BUILT-IN, default_https_monitor:L4CON
| | | LAST STATE CHANGE: 2018-02-28 17:30:12
| | | FAILURE DETAIL: Out of local source ports on the system
| | SESSION (cur, max, total) = (1, 1, 3)
| | BYTES in = (2661), out = (3408)

Impact / Risks

Load balancer Monitoring would not work and will mark the pool members down. The NSX Edge will not be able to load balance the traffic since there are no available ports to initiate connections to the backend pool members.

Resolution

VMware does not recommend configuring a Load Balancer VIP spanning the ip_local_port_range values on the edge from 10000 to 64000. Changing this value is not supported as this is not persistent if the NSX Edge is redeployed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

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 NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant