For more details, please see ourCookie Policy.

Application Delivery (ADX)

Setting/Changing/Enabling Persistence connections - primary and secondary grouped protocol services

by pmorrissey on ‎05-29-2009 03:20 PM - edited on ‎10-30-2013 05:42 PM by bcm1 (349 Views)


How to set/change/enable persistence connections to the same real server (for primary/and related secondary service connections) using application grouping – track port


Figure below shows an example of servers configured with sticky ports and an application group. In this example, the content on each real server is identical. However, some applications on the server require that clients use the same server for subsequent requests to application and/or group related application services to the same real server.



The virtual server is configured to make the ports sticky and to group the TFTP and Telnet ports under the HTTP port.


The example below illustrate the track port function. The sticky parameter makes the TCP/UDP ports sticky.

The track command groups the Telnet port (23) and the TFTP port (69) under the HTTP port (80); the HTTP port

is established as the “primary” port. After the ServerIron ADX sends a client to a real server for the HTTP port,

subsequent requests from that client for the HTTP, TFTP, or Telnet port go to the same real server. Up to four

ports can be grouped with the primary port.


Sample Script/Code/Configuration

server real-name r1
port http
port tftp
port telnet
server real-name r2
port http
port tftp
port telnet
server virtual v1
port 80 sticky
port 69 sticky
port 23 sticky
track 80 69 23
bind 80 r1 80 r2 80
bind 23 r1 23 r2 23
bind 69 r1 69 r2 69


Tips / Caveats




Further Reading