beautypg.com

Keeping the persistent hash table unchanged – Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual

Page 107

background image

Brocade Virtual ADX Server Load Balancing Guide

91

53-1003247-01

Hash-based SLB with server persistence

2

The Brocade Virtual ADX now attempts to reassign 3 persistent hash entries to the new real server
over 2 minutes. The system will stop after it has reassigned 2 entries of real server rs1 to new real
server rs3. The reason is that when rs3 is assigned 2 persistent hash entries, the value is equal to
the number of entries assigned to existing real server rs2.

Figure 17

shows the persistent hash table after the reassignment.

FIGURE 17

Hash table after reassignment

Keeping the persistent hash table unchanged

To configure the Brocade Virtual ADX not to clear the persistent hashing table when multiple
servers come up simultaneously and need reassignment, enter commands such as the following.

SLB-Virtual ADX(config)#server virtual-name-or-ip vs1

SLB-Virtual ADX(config-vs-vs1)#port http no-auto-clear-persist-hash-buckets

If this command is configured and multiple servers need reassignment simultaneously, then the
Brocade Virtual ADX will leave the persistent hash table unchanged.

Syntax: port port no-auto-clear-persist-hash-buckets

virtual server vs1

port http

Persistent Hash table

Hash 0

none

Hash 1

none

..............

Hash 47

rs3

Hash 49

rs1

Hash 55

rs2

Hash 53

rs1

Hash 54

rs1

Hash 56

rs2

Hash 48

rs3

Hash 50

rs1

Hash 51

rs1

Hash 52

rs1

Hash 255

none

..............