NetScaler's ultra-high-end port multiplexing helps address tension in the public network

Often people ask an IP only 65535 (regardless of the reserved port), from big-IP migration to the NetScaler need not increase the number of IP addresses to cope with large throughput scenarios, especially the application of link load balancing?

As we all know, netscaler contrast big-IP has obvious savings in address characteristics, basically netscaler can use a minimum of 2 public address (management address for private network address) can provide extranet services (NAT on NetScaler rather than firewall), Big-IP requires at least 4 public addresses.

In the big-IP environment, you will have a lot of IP addresses to deal with the port is not enough, but if in the NetScaler environment can save a large number of public network address. As a result of this feature, NetScaler content Exchange has been given the possibility of implementing a wide range of IP hosting services, and a single URL is implemented for the unified gateway function in the new version to provide a unified business interface for the enterprise.

The IP of the NetScaler is characterized by ultra-high-end port multiplexing, where an IP can have millions of port statements used by TCP connections. The basic element of a socket is the src+s_port+dst+d_port+ protocol. A socket can be created as long as not all elements overlap at the same time.

Use the following command to see how many ports are available for snip:

Nsapimgr-d Freeports

For example, query the number of ports available for each IP:

[Email protected]# nsapimgr-d freeports

Displaying All-ports of all MIPs ...

Index IP Freeports

0 0.0.0.1 16513804

1 127.0.0.2 1031695

2 241.0.0.2 1032112

3 241.0.0.4 1032112

4 241.0.0.5 16513792

5 10.0.1.52 1029948

This article is from the "citrix_technical" blog, make sure to keep this source http://caojin.blog.51cto.com/12564439/1898351

NetScaler's ultra-high-end port multiplexing helps address tension in the public network