Operating instructions

190 Cisco Systems Intelligent Gigabit Ethernet Switch Module
Figure 7-21 Verifying an Active/Standby SLB team
SLB Active/Active teaming on BladeCenter HS20 with Red Hat Linux
In this section, we demonstrate how to create an SLB team to connect to the Cisco Systems
IGESMs as an access port on a BladeCenter HS20 running Red Hat AS 2.1. The following
configuration, which we discuss here as an example, is basically the same configuration as
BladeServer3 in previous topology examples, except for the IP address used in this example:
򐂰 The server uses the BASP software to create a single teamed logical interface for VLAN
30, and the IP configuration is performed on this single logical interface (not on the
physical interfaces).
򐂰 This logical port connects to both CIGESM1 and CIGESM2 and is placed in VLAN 30,
respectively, through access port settings on each Cisco Systems IGESM. All IP
configuration is performed on this single logical interface (not on the physical interfaces).
򐂰 We use the following IP address (24-bit masks):
BASP logical port, to CIGESM1: 10.1.30.11 (default gateway = 10.1.30.254)
To create a team on Linux using BACS, you need to configure teaming settings with
configuration scripts. To create a configuration script, you should copy a sample script from
the /etc/basp/samples directory to the /etc/basp directory and use it as a template. The
configuration script name must be prefixed with “team-”. After you create the configuration
script, manually start the team for the first time with % /etc/init.d/basp start. For complete
steps, refer to the BACS readme file.
Copy the team-sample file from the /etc/basp/sample directory and name it
team-toBothVLAN. Modify the file as follows. Modified or added items are in red italics.
TEAM_ID=0
TEAM_TYPE=0
TEAM_NAME=toBothVLAN
# 1st physical interface in the team
TEAM_PA0_NAME=eth0
TEAM_PA0_ROLE=0
# 2nd physical interface in the team
TEAM_PA1_NAME=eth1
TEAM_PA1_ROLE=0
# 3rd physical interface in the team