the configuration script must be prefixed with "team-".
2 modify the configuration script to:
■ change the team type
■ add/delete physical network interfaces
■ add/delete virtual network interfaces
the syntax of the configuration script can be found below.
3 manually start the team for the first time by typing:
/etc/rc.d/init.d/basp start
4 run "netcfg" to configure the ip addresses of the virtual network interfaces.
if "netcfg" does not run, enter following command:
% ifconfig sw0 172.16.10.10 up
consult ifconfig(8) for details in manually configuring a network interface.
starting the team is only required for the first time. teams will be started automatically in subsequent reboots.
forming multiple teams is possible by copying the sample files into "/etc/ basp/" and modifying this file as described in the sample file. the files must have unique filenames. name the files "team-xxx" where "xxx" is a unique identifier for the team.
to create more that one virtual interface (vlan) for each team, refer to the respective description section in the sample files.
baspcfg command line tool
the baspcfg command line tool is used to configure the advanced server features teams, add and remove nics, and add and remove virtual devices. the following is an example of the usage of this tool.
baspcfg v1.1.6 all rights reserved.
usage: baspcfg
startup scripts
1 basp
this script is intended to be installed in /etc/rc.d/init.d directory. after copying the script, run "chkconfig --add basp". this script will be executed at runlevel 2, 3, 4 and 5. when basp runs, it will search the /etc/basp directory to list all the files with "team " prefix, and then it will invoke the "baspteam" script to add or delete the teams. it is normal, for each "team-*" file in /etc/basp, to represent 1 team.
2 baspteam
this script is called by basp to add or delete a team. to install, create "/etc/basp" directory and copy this script over.
to manually add a team, type:
baspteam team-sample add
to delete a team, type:
baspteam team-sample del
note that "team-sample" is the config script.
3 team-sample
this script contains an slb team configuration with three nics: eth0, eth1 and eth2.
the team name is "teamsample". all three nics are primary. one virtual interface is also created for this team and the name of the virtual interface is "sw0". "sw0" is the device that ifconfig should be run against to set up the ip address. no vlan is enabled in the script.
this script and "team-gec" are intended to be customized. refer to the configuration scripts section for details. this script should be copied to /etc/basp directory and retain the "team-" prefix.
4 team-gec
this configuration script creates a gec team with 3 network interfaces: eth0, eth1 and eth2. the team name is "teamgec". all 3 nics are primary. one virtual interface is added to the team with the name "sw0" and no vlan is enabled.
this script and the "team-sample" script are intended to be customized. refer to the configuration scripts section for details. this script should be copied to /etc/basp directory and retain the "team-" prefix.
starting the team is only required for the first time. teams will be started automatically in subsequent reboots.
forming multiple teams is possible by copying the sample files into "/etc/ basp/" and modifying this file as described in the sample file. the files must have unique filenames. name the files "team-xxx" where "xxx" is a unique identifier for the team.
to create more that one virtual interface (vlan) for each team, refer to the respective description section in the sample files.
configuration scripts
both team-sample and team-gec are configuration scripts that follow the same syntax, as follows:
■ team_id: this number uniquely identifies a team.
■ team_type: 0 = slb, 1 = generic trunking/gec/fec
■ team_name: ascii name of the team
■ team_pax_name: ascii name of the physical interface x, where x can be 0 to 7.
■ team_pax_role: role of the physical interface x 0 = primary, 1 = hot-standby. this field must be 0 for generic trunking/gec/fec team.
■ team_vax_name: ascii name of the virtual interface x, where x can be 0 to 63
■ team_vax_vlan: 802.1p vlan id of the virtual interface x. for untagged virtual interface, i.e., without vlan enable, set it to 0. the valid vlan id can be 0 to 4094.
nice patches
also included in this distributions are network device drivers patched with nice support. these drivers are originally taken from linux 2.2.16 kernel distribution. to install patched drivers:
1 copy the nice header file, "nicext.h", to the linux kernel include directory as follows:
cp /usr/src/basplnx-{version}/nicext.h user/src/linux/include/ linux
where /usr/src is the temp directory you created when you installed the "advanced server features" on page 67.
2 rename the original network device driver under the linux kernel source tree /usr/src/ linux/drivers/net:
mv /usr/src/linux/drivers/net/3c59x.c /usr/src/linux/drivers/ net/3c9x.orig
3 copy the patched drivers to the linux kernel network driver source directory /usr/src/ linux/drivers/net:
cp 3c59x.c /usr/src/linux/drivers/net/3c59x.c
4 follow the kernel rebuild instructions to configure kernel support of these drivers as follows:
cd /usr/src/linux
make config
5 if the patched drivers are configured into kernel, go to step 7. if the patched drivers are configured as module, go to step 6.
6 in the case of supporting only a module version of these drivers, it is possible to run the following steps to compile the patched driver, then install them into the proper module directory:
make modules
make modules_install
there is no need to compile the complete kernel, go to step (8).
7 rebuild the kernel to compile these patched drivers, as follows:
make dep
make clean
make bzimage
8 either reboot the system or unload/load the patched modules. then run configuration scripts to test the patch.
removing the driver and team configuration
to remove the rpm package, type:
rpm -e basplnx-{version}.386.rpm
to reboot the system, type:
reboot