Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 57)

Brocade Virtual ADX Server Load Balancing Guide 41
53-1003247-01
Sticky and concurrent connections
2
port http
port http url "HEAD /"
port http group-id 2 2
server real Web2 10.20.1.43
port http
port http url "HEAD /"
port http group-id 2 2
server real Web3 10.20.1.44
port http
port http url "HEAD /"
port http group-id 2 2
2. On the VIP, ensure the minimum required commands for Group Sticky are present: port type
group-sticky and port type sticky. If stickiness is not configured, load balancing among the
group will not work.
Virtual ADX(config-vs-v1)#server virtual-name-or-ip vip1 10.40.1.10
Virtual ADX(config-vs-vip1)#predictor round-robin
Virtual ADX(config-vs-vip1)#port http sticky !(or port http
client-subnet-sticky)
Virtual ADX(config-vs-vip1)#port http group-sticky
Virtual ADX(config-vs-vip1)#bind http rs1 http rs2 http Web1 http Web2 http
Virtual ADX(config-vs-vip1)#bind http Web3 http
Once a group sticky session is created, all subsequent traffic will be load balanced across the
group. The first incoming sticky session will go to a real server in group 1. All subsequent
connections will also go to group 1.
If multiple clients are in the same subnet, then use the port http client-subnet-sticky command
instead of port http sticky. The group sticky behavior will apply itself to the client-subnet-sticky.
NOTE
When a real server’s port is part of two groups, the group-sticky feature takes the first listed
group ID only, if the first connection is load balanced to this server.