Radware Alteon Application Manual page 711

To enable GSLB availability persistence
1. DSSP version 3 must be enabled on all Alteons with GSLB configured, using the following
command:
/cfg/slb/gslb/version 3
2. The availability metric must be the first metric configured in the first GSLB rule. For information
on rule creation, see
3. Enable availability persistence on the backup Alteon (the Alteon that will take over from the
primary Alteon) using the following command:
/oper/slb/gslb/avpersis <virtual server number> enable
Note: This is an operational command that does not survive an Alteon reboot.
4. After the primary server recovers, you can revert to the configured availabilities on the Alteon
whose virtual server currently has precedence. This is the Alteon with the virtual server that is
advertising an availability of 48:
/oper/slb/gslb/avpersis <virtual server number> disable.
After both sites are reporting their configured availability, turn the feature back on by enabling
availability persistence on Alteon with the backup server:
/oper/slb/gslb/avpersis <virtual server number> enable
You can use the following command to enable or disable availability persistence on the backup
Alteon:
/cfg/slb/virt <virtual server number>/avpersis enable/disable.
GSLB Client Proximity Metric
The GSLB client proximity metric measures the proximity between each data center and the client.
It is limited to HTTP and HTTPS traffic. This section describes the basic commands used with client
proximity.
For more information about the client proximity commands, see the Alteon Application Switch
Operating System Command Reference. For example configurations using GSLB client proximity, see
Configuring GSLB with Client Proximity, page
To enable client proximity for HTTP/HTTPS
/cfg/slb/virt <x>/service <x>/http/clientprox http|https|none
Document ID: RDWR-ALOS-V2900_AG1302
Alteon Application Switch Operating System Application Guide
Rules, page 710.
734.
Global Server Load Balancing
711