Brocade Communications Systems 12.4.00 Manual De Usuario
70
ServerIron ADX Global Server Load Balancing Guide
53-1002437-01
Site persistence in GSLB using hashing
1
Deleting sticky GSLB session for a specific client
To delete Sticky GSLB sessions for a specific client, enter a command such as the following:
ServerIronADX#clear gslb sticky-session client-ip 100.1.1.101
Syntax: clear gslb sticky-session client-ip <client-ip>
The <client-ip> is the IP address or prefix of the client for which sticky session will be deleted.
Deleting all sticky GSLB sessions
To delete all the Sticky GSLB sessions globally, enter a command such as the following:
ServerIronADX# clear gslb sticky-session all
Syntax: clear gslb sticky-session all
For a GSLB sticky session to be synced, you must configure symmetric-port with port and VLAN
information on both the master and backup ServerIron ADX switches as shown in the following:
information on both the master and backup ServerIron ADX switches as shown in the following:
ServerIronADX(config)# server symmetric-port ethernet 7 vlan-id 7
Site persistence in GSLB using hashing
Hash-based GSLB persistence provides GSLB controller persistence in a multiple GSLB controller
environment for the same domain. When users query for a host name, regardless of which GSLB
controller is contacted, the users will get the same answer.
environment for the same domain. When users query for a host name, regardless of which GSLB
controller is contacted, the users will get the same answer.
Sticky GSLB alone is sufficient for single-box and HA (hot standby, symmetric, sym-active)
topologies. However, if there are two GSLB controllers across a network providing GSLB for the
same domain but are not in an HA configuration, and if persistence is desired when the same client
is directed to either of these two GSLB controllers, then hash-based GSLB persistence should be
used.
topologies. However, if there are two GSLB controllers across a network providing GSLB for the
same domain but are not in an HA configuration, and if persistence is desired when the same client
is directed to either of these two GSLB controllers, then hash-based GSLB persistence should be
used.
Enabling hash-based GSLB persistence
Hash-based GSLB persistence can be enabled for all domains or only for specific domains. This
feature cannot be enabled concurrently with Sticky GSLB in the same policy. Although, you can
enable Sticky GSLB for one policy and hash-based GSLB persistence for another policy.
feature cannot be enabled concurrently with Sticky GSLB in the same policy. Although, you can
enable Sticky GSLB for one policy and hash-based GSLB persistence for another policy.
To enable hash-based GSLB persistence globally, enter commands on the GSLB controller, such as
the following:
the following:
SLB-ServerIronADX(config)# gslb policy
SLB-ServerIronADX(config-gslb-policy)# hash-persist
Syntax: hash-persist
Displaying the hash table
A hash table is maintained for a domain for which hash-based GSLB persistence is enabled in the
associated policy. There are 256 entries in the hash table, and there is a domain IP address
associated with each of these entries.
associated policy. There are 256 entries in the hash table, and there is a domain IP address
associated with each of these entries.