beautypg.com

Configuring a track port group, Track port group health checks for real servers – Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual

Page 61

background image

Brocade Virtual ADX Server Load Balancing Guide

45

53-1003247-01

Application port grouping

2

NOTE

Every port in a track port group must be configured to be “sticky” and be bound to the real servers
involved.

NOTE

If no track port group configured, the sticky session age is not refreshed if any data session exists.
Only the data session's age will be refreshed if the connection is still alive.

NOTE

If a track port group is configured into the VIP (i.e. for two ports), the sticky session refreshes and
will not expire as long as one of the ports has an alive session.

Configuring a track port group

To configure a track port group, enter commands such as the following:

Virtual ADX(config)#server virtual-name-or-ip v1 10.157.22.1

Virtual ADX(config-vs-v1)#port 80 sticky

Virtual ADX(config-vs-v1)#port 69 sticky

Virtual ADX(config-vs-v1)#port 23 sticky

Virtual ADX(config-vs-v1)#track-group 80 69 23

Virtual ADX(config-vs-v1)#bind 80 r1 80 r2 80

Virtual ADX(config-vs-v1)#bind 23 r1 23 r2 23

Virtual ADX(config-vs-v1)#bind 69 r1 69 r2 69

Virtual ADX(config-vs-v1)#exit

In this example, the track-group command groups the HTTP port (80), TFTP port (69), and Telnet
port (23) together. Whenever a client attempts to connect to a port within the port group, the
Brocade Virtual ADX ensures that all ports in the group are active before granting the connection.

Syntax: [no] track-group TCP/UDP-port...

The sticky parameter makes the TCP or UDP ports sticky. The sticky parameter must be set for all
ports in the group.

After the Brocade Virtual ADX sends a client to a real server for any of these three ports,
subsequent requests from that client for port HTTP, TFTP, or Telnet will go to the same real server.

Track port group health checks for real servers

The Brocade Virtual ADX enables you to configure track port groups for both virtual servers and real
servers; thereby reducing the need to create large numbers of Boolean health checks.

You can track the health of multiple application ports under a real server definition. If the health of
one of the application ports fails, the aggregated health will be marked as fail.

Track port group health checks co-exists with existing health checks and other features of the
Brocade Virtual ADX. If even one of the application ports under real server is not up, the track port
group state will be down and the traffic will not be forwarded to any of the ports in the track port
group.

A sample configuration is shown below.

Virtual ADX(config)#server real r1 10.1.1.1

Virtual ADX(config-real-server-r1) port 80

Virtual ADX(config-real-server-r1) port 8081