WebOS 10.0 Application Guide
270 Chapter 11: High Availability 212777-A, February 2002
3. Define the virtual servers.
After defining the virtual server IP addresses and associating them with a real server group
number, you must tell the switch which IP ports/services/sockets you want to load balance on
each VIP. You can specify the service by either the port number, service name, or socket num-
ber.
Repeat this sequence of commands for the following virtual servers:
nVIP 2 200.200.200.101 will load balance HTTPS (Port 443) to Group 2
nVIP 3 200.200.200.102 will load balance POP/SMTP (Ports 110/25) to Group 3
nVIP 4 200.200.200.104 will load balance FTP (Ports 20/21) to Group 4
4. Define the client and server port states.
Defining a client port state tells that port to watch for any frames destined for the VIP and to
load balance them if they are destined for a load-balanced service. Defining a server port state
tells the port to the do the remapping (NAT) of the real server IP address back to the virtual
server IP address. Note the following:
nThe ports connected to the upstream switches (the ones connected to the routers) will need
to be in the client port state.
nThe ports connected to the downstream switches (the ones providing fan out for the serv-
ers) will need to be in the server port state.
Configure the ports, using the following sequence of commands:
>> Real server group 4 # /cfg/slb/virt 1 (Select virtual server 1)
>> Virtual server 1 # vip 200.200.200.100 (Assign a virtual server IP address)
>> Virtual Server 1 # service 80 (Assign HTTP service po rt 80)
>> Virtual server 1 http Service # group 1(Associate virtual port to real group)
>> Virtual server 1 # ena (Enable the virtual server)
>> Virtual server 4# /cfg/slb/port 1 (Select physical switch port 1)
>> SLB port A1 # client ena (Enable client processing on port 1)
>> SLB port A1 # ../port 2 (Select physical switch port 2)
>> SLB port A2 # server ena (Enable server processing on port 2)