bea.com | products | dev2dev | support | askBEA |
|
e-docs > WebLogic Server > Using WebLogic Server Clusters > Configuring AlteonTM Hardware with Clusters |
Using WebLogic Server Clusters |
Configuring AlteonTM Hardware with Clusters
This section describes how to configure an Alteon WebSystems Web switch and server load balancing software to operate with a WebLogic Server cluster. It assumes that you have some familiarity with Alteon configuration tasks, such as using the Web OS administration tools and attaching hardware to the Web switch.
Some step-by-step instructions for configuring Alteon products are included. However, if you require detailed setup and administration instructions, refer to your Alteon product documentation. This topic contains the following sections:
The configuration instructions in this section require that you use the following products:
The steps in this section reference an example WebLogic Server cluster with the following components:
Your actual configuration will likely use different IP addresses, and different ports on the Web switch. If your system includes an iSD-SSL Accelerator, follow the steps in Configuring Alteon with a WebLogic Server Cluster to configure the basic load balancing features, then refer to Configuring Alteon SSL Accelerator with a WebLogic Server Cluster.
Configuring Alteon with a WebLogic Server Cluster
The following steps summarize the process of configuring Alteon products with a WebLogic Server cluster:
>> # /cfg/vlan 2
>> VLAN 2# add 6
>> VLAN 2# add 7
>> VLAN 2# add 8
>> VLAN 2#ena
>> # /cfg/ip/if 1
>> IP Interface 1# addr 192.168.0.20
>> IP Interface 1# ena
>> # /cfg/ip/if 2
>> IP Interface 2# addr 172.17.10.100
>> IP Interface 2# vlan 2
>> IP Interface 2# ena
>> # /cfg/slb/real 1
>> Real Server 1# rip 192.168.0.10
>> Real Server 1# ena
>> Real Server 1# /cfg/slb/real 2
>> Real Server 2# rip 192.168.0.11
>> Real Server 2# ena
>> Real Server 2# /cfg/slb/real 3
>> Real Server 3# rip 192.168.0.12
>> Real Server 3# ena
>> # /cfg/slb/group 1
>> Real server group 1# add 1
>> Real server group 1# add 2
>> Real server group 1# add 3
>> # /cfg/slb/group 1
>> Real Server group 1# metric hash
>> # /cfg/slb/virt 1
>> Virtual server 1# vip 172.17.10.100
>> Virtual server 1# service http
>> Virtual server 1 http Service# group 1
>> Virtual server 1 http Service# ..
>> Virtual server 1# ena
Note: The following example uses the default values for the WebLogic Server cookie offset, size, and name. These values can be configured in the weblogic.xml file for the deployed application.
>> # /cfg/slb/virt 1/service 80
>> Virtual server 1 http service# pbind
Enter clientip|cookie|sslid persistence mode: cookie
Enter passive|rewrite cookie persistence mode: passive
Enter Cookie Name: JSESSIONID
Enter the starting point of the cookie value: 53
Enter the number of bytes to extract: 10
Look for cookie in URI [e|d]: dis
>> # /cfg/slb/port 6
>> Port 6# server ena
>> # /cfg/slb/port 7
>> Port 7# server ena
>> # /cfg/slb/port 8
>> Port 8# server ena
>> Port 8# /cfg/slb/port 1
>> Port 1# client ena
>> # /cfg/slb
>> Server Load Balancing# on
>> Server Load Balancing# apply
>> Server Load Balancing# save
Configuring Alteon SSL Accelerator with a WebLogic Server Cluster
If you use an Alteon SSL accelerator with the WebLogic Server cluster, you will also need to configure a Virtual LAN for the accelerator and create routing policies for directing traffic between the cluster and accelerator. The following steps extend the example system described in Configuring Alteon with a WebLogic Server Cluster to use an Alteon iSD100-SSL accelerator. The accelerator is attached to port 2 of the Alteon web switch.
To use an SSL accelerator with a WebLogic Server cluster:
>> # /cfg/vlan 2
>> VLAN 2# add 2
>> VLAN 2# ena
>> # /cfg/stp/port 2
>> STP PORT 2# off
>> # /cfg/stp/port 6
>> STP PORT 6# off
>> # /cfg/stp/port 7
>> STP PORT 7# off
>> # /cfg/stp/port 8
>> STP PORT 8# off
>> # /cfg/ip/if 2
>> IP Interface 2# addr 192.168.0.21
>> IP Interface 2# vlan 2
>> IP Interface 2# ena
>> # /cfg/isd/ssl/setport 81
>> # /cfg/slb/filt 100
>> FILTER 100# proto tcp
>> FILTER 100# dport https
>> FILTER 100# action redir
>> FILTER 100# group 256
>> FILTER 100# rport https
>> FILTER 100# ena
>> # /cfg/slb/filt 101
>> FILTER 101# sip any
>> FILTER 101# dip any
>> FILTER 101# proto any
>> FILTER 101# action allow
>> FILTER 101# ena
>> # /cfg/slb/port 1
>> PORT 1# add 100
>> PORT 1# add 101
>> PORT 1# filt ena
>> # /cfg/slb/filt 102
>> FILTER 102# proto tcp
>> FILTER 102# sport 81
>> FILTER 102# action redir
>> FILTER 101# group 256
>> FILTER 101# ena
>> # /cfg/slb/port 6
>> PORT 6# add 101
>> PORT 6# add 102
>> PORT 6# filt ena
>> # /cfg/slb/port 7
>> PORT 7# add 101
>> PORT 7# add 102
>> PORT 7# filt ena
>> # /cfg/slb/port 8
>> PORT 8# add 101
>> PORT 8# add 102
>> PORT 8# filt ena
>> # /cfg/slb
>> Server Load Balancing# on
>> Server Load Balancing# apply
>> Server Load Balancing# save