Radware Alteon Application Manual page 722

Alteon Application Switch Operating System Application Guide
Global Server Load Balancing
>> Virtual server 1 http service# group 1
>> Virtual server 1 http service# /cfg/slb/virt
1/ena
5. On the Denver Alteon, define the type of Layer 4 processing each port must support, as follows:
>> # /cfg/slb/port 11
>> SLB port 11# server ena
>> SLB port 11# /cfg/slb/port 12
>> SLB port 12# server ena
>> SLB port 12# /cfg/slb/port 2
>> SLB port 2# client ena
6. On the Denver Alteon, enable SLB.
>> # /cfg/slb/on
To configure the Denver Site for GSLB
Following the same procedure described for San Jose (see
page 717), configure the Denver site as follows:
1. On the Denver Alteon, turn on GSLB.
>> Virtual server 1# /cfg/slb/gslb/on
2. Enable DSSP version 2 to send out remote site updates.
Note: Unless you are in the middle of network migration from an Alteon version prior to 22.0,
you should always enable DSSP version 2.
>> # /cfg/slb/gslb/version 2
3. On the Denver Alteon, define each remote site.
When you start configuring at the Denver site, Denver is local and San Jose is remote. Add and
enable the remote Alteon's IP address interface. In this example, there is only one remote site: San
Jose, with an IP interface address of 200.200.200.1. Use the following commands:
>> # /cfg/slb/gslb/site 1
>> Remote site 1# prima 200.200.200.1
>> Remote site 1# ena
Each additional remote site would be configured in the same manner. You can enable up to 64
remote sites.
4. On the Denver Alteon, assign each remote distributed service to a local virtual server.
722
(Associate virtual port to real group)
(Enable the virtual server)
(Select physical Port 11)
(Enable server processing on Port 11)
(Select physical Port 12)
(Enable server processing on Port 12)
(Select physical Port 2)
(Enable client processing on Port 2)
To configure the San Jose Site for GSLB,
(Select Remote Site 1)
(Define remote IP interface address)
(Enable Remote Site 1)
Document ID: RDWR-ALOS-V2900_AG1302