> Back to Contents Page

> ## Broadcom Advanced Server Program Driver Software (NetWare): Broadcom NetXtreme® 57XX User Guide

> BASP Overview

> Balance Modes and Limitations

> NESL Compliance

> Loading Broadcom Advanced Server Program

> Configuring Teaming

> ### BASP Overview

> BASP.LAN is Broadcom's virtual Ethernet driver for NetWare 5.1 and 6.x that provides load balancing, fault-tolerance, and VLAN features. These features are provided by creating teams (virtual adapters) that consist of multiple NIC interfaces. A team can consist of one to six (eight on some systems) NIC interfaces and each interface can be designated primary or standby*. All primary interfaces in a team will participate in Load-balancing operations by sending and receiving a portion of the total traffic**. Standby interfaces will take over in the event that all primary interfaces have lost their links. VLANs can be added to a team to allow multiple VLANs with different VLAN IDs to share the virtual adapter.

> Load-balancing and fault-tolerance features work with any third-party NIC adapters. VLANs only work with Broadcom or Alteon NIC adapters.

> *Standby can only be used in Smart Load-Balance mode (See below).

> **In IEEE 802.3ad mode, the number of NIC interfaces aggregated is automatically determined through LACP (see below).

> ### Balance Modes and Limitations

> Smart Load-balance (SLB) is a protocol-specific scheme and the level of support for IP, IPX, and other protocols are listed below.

> Table 1: Balance Modes and Limitations
> Protocol | Load Balancing Support | Fault Tolerance Support
> --- | --- | ---
> IP | Yes | Yes
> IPX | Yes* | Yes**
> Other protocols | No | Yes**

> *Only outbound load-balancing for IPX (on NetWare only).
> **Only for Broadcom NICs. Alteon's driver ALT.LAN must be version 2.05b or newer released by Broadcom.

> SLB works with all Ethernet switches without configuring the switch ports to any special trunking mode. Only IP traffic is load-balanced in both inbound and outbound directions. IPX traffic will be load-balanced in outbound direction only. Other protocol packets will be sent and received through one primary NIC only. Fault-tolerance for non-IP traffic is only supported using Broadcom or Alteon NICs.

> The Generic Trunking mode requires the Ethernet switch to support some form of port trunking mode (Cisco's Gigabit EtherChannel or other switch vendor's link aggregation mode). Trunking mode must be statically configured on the switch ports that are connected to the team. This mode is protocol-independent and all traffic should be load-balanced and fault-tolerant.

> The IEEE 802.3ad mode requires the Ethernet switch to support IEEE 802.3ad with LACP (Link Aggregation Control Protocol). LACP will try to configure the maximum number of NICs in the team that are compatible for link aggregation. If LACP determines that some NICs are not able to aggregate (because of some restrictive limitations or configurations on the switch), the remaining NICs that cannot aggregate will be idle. If LACP is completely disabled on the switch, then only one of the NICs in the team will be used. Some switches require the LACP ports to be in full-duplex mode for them to work. LACP can be configured active or passive on the team and most switches allow active or passive selections on a per port basis. At least one side of each connection must be active otherwise the connection will never be selected for aggregation. This mode is also protocol-independent and all traffic should be load-balanced and fault-tolerant.

> ### NESL Compliance

> For optimum fault tolerance and recovery operations, the BASP.LAN driver relies on the adapter drivers to generate NetWare Event Service Layer (NESL) events during link changes and other failure events. NESL is an optional feature in the ODI driver specification, and not all drivers support it. For NESL events to propagate properly to the BASP.LAN driver, the ODINEB.NLM driver must be loaded before the NESL-compliant ODI drivers are loaded.

> Do the following to check if an adapter driver supports NESL events: Load the BASP.LAN driver and create a team by binding the adapter to the virtual slot (see the following instructions and examples). In the Virtual Adapter X Team Members console, the link status of all bound adapters is shown. Disconnect or connect the adapter cable. If the adapter driver supports NESL events, the link status should change immediately.

> ### Loading Broadcom Advanced Server Program

> 1. Load the BASP.LAN driver just as you would a standard LAN driver with all necessary frame types for the team. The BASP.LAN driver requires a special VSLOT parameter to specify the virtual slot. The virtual slot can be viewed as team numbers 1 through 4, which supports up to eight adapters and up to four teams.

> NOTES:

> 2. Be sure to load BASP.LAN before loading your standard LAN driver.
> 3. The BASP configuration procedure also applies when you are adding an adapter by hot plugging.

> Example:

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1

> 4. Load the network drivers for the adapters that are to be on the team. The frame types loaded should be the same for all adapters on the team and the same as those loaded for BASP.LAN in step 1. Do not bind protocols directly to these adapters. Be sure to load ODINEB.NLM (supplied by Novell) before all network drivers are loaded.

> Example:

>     LOAD ODINEB.NLM
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

> After BASP.LAN is successfully loaded, a new screen similar to the one above appears. This screen displays all virtual adapter settings and statistics. Press ALT+ESC to switch back to the console and continue with step 3.

> 1. Bind BASP.LAN to the adapters on the team by using a custom BASP BIND command at the console.

> Example:

>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII

> NOTE: If there are multiple frame types loaded on the virtual and the physical adapters, it is necessary to bind only one frame type on the virtual adapter to the same frame type on the physical adapter. The other frame types are automatically bound.

> 2. Bind protocols to BASP.LAN.

> Example:

>     BIND IP BASP_1_EII ADDR=x.x.x.x MASK=x.x.x.x

> NOTE: The recommended sequence is to load BASP.LAN before the network drivers as outlined above. This allows BASP.LAN to determine the initial link state of the bound adapters without delay.

> ### Unloading BASP

> To unload Broadcom Advanced Server Program, unload the adapter driver and the BASP drivers.

> For the adapter driver, at the Command Line Interface (CLI):

>     UNLOAD B57

> The response is:

>     Module B57.LAN unloaded

> For the BASP driver, at the Command Line Interface (CLI):

>     UNLOAD BASP

> The response is:

>     Module BASP.LAN unloaded

> NOTE: BASP can not be unloaded if one or more adapters are bound to BASP.

> ### Configuring Teaming

> Balance Mode Selection

> Loading Frame Types

> Hot Standby

> Configuring VLANs

> Jumbo Frames

> Additional Command Line Keywords

> Editing the Autoexec.ncf File

> Using INETCFG

> For further information regarding teaming, see "Teaming" and "Broadcom Gigabit Ethernet Teaming Services".

> NOTES:

> - Spanning Tree Protocol should be disabled on all switch ports to which teamed adapters are connected.
> - If remote management (IPMI) is enabled on a device, the IPMI service could be disrupted when the device is added to a team other than an SLB team.

> ##### Balance Mode Selection

> Use MODE=SLB for a Smart Load-Balancing type of team, MODE=TRUNK for a Generic Trunking type of team, or MODE=802.3AD for an 802.3ad type of team. The default selection is SLB.

> Example:

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 MODE=TRUNK

> NOTES:

> - For an SLB type of team, IPX traffic is load-balanced only on the send side, but not on the receive side.
> - For optimum fault tolerance and recovery operations, the BASP.LAN driver relies on the adapter drivers to generate NESL (NetWare Event Service Layer) events during link changes and other failure events. NESL is an optional feature in the ODI driver specification and not all drivers support it. For NESL events to propagate properly to BASP.LAN, ODINEB.NLM must be loaded before the NESL compliant ODI drivers are loaded.

> Do the following to check if an adapter driver supports NESL events: Load the BASP.LAN driver and create a team by binding the adapter to the virtual slot. Disconnect or connect the adapter cable. The link status of each bound adapter is shown on the Virtual Adapter X Team Members screen of the BASP.LAN menu interface. If the adapter driver supports NESL events, the displayed link status shown on the screen should change immediately.

> In IEEE 802.3ad mode, an untagged Ethernet II frame type must be loaded before LACP frames can be transmitted and received. LACP defaults to active for all adapters in the team. Use the parameter LACP=PASSIVE to change LACP to passive mode for all adapters in the team. Note that at least one side (system or switch) must be in LACP active mode for it to work.

> Example:

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 MODE=802.3AD LACP=PASSIVE

> ##### Loading Frame Types

> After one or more adapters are bound to a virtual adapter, additional frame types can only be loaded in the virtual adapter if the corresponding frame types are also loaded in the bound adapters. For example, ETHERNET_802.2 can be loaded in BASP VSLOT 1 if ETHERNET_802.2 is loaded for the B57 driver in SLOT 1 and 2 in the example below. Similarly, a virtual adapter can only be bound to a physical adapter if the physical adapter has all the frame types loaded in the virtual adapter.

> Example:

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_802.2 NAME=BASP_1_E82 VSLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_1_E82 SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_2_E82 SLOT=2

> ##### Hot Standby

> For a Smart Load Balancing™ (SLB) type of team, only one adapter can be designated as a hot standby member. Use the keyword standby in the BASP bind command to bind an adapter as a hot standby member.

> Example:

>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII STANDBY

> In the above example, B57_1_EII and B57_2_EII are bound as primary and hot standby members, respectively. Note that a standby member can be used only on a Smart Load Balancing type of team.

> NOTE: No traffic is passed to the standby member until the primary member fails

> ##### Configuring VLANs

> NOTES:

> - VLANs are not supported on non-Broadcom adapters. VLANs are supported on the Alteon® adapters if the ALT.LAN driver provided by Broadcom is used. If a non-Broadcom adapter is a member of a failover team, VLANs are not supported for that team.
> - To avoid failover problems when using BASP, make sure that the spanning tree is disabled on the switch to which the network adapter is connected.

> To add VLANs to a team, do the following:

> 1. Load the BASP.LAN driver with the all necessary frame types and specify the VLAN ID for each frame type. You can specify a maximum of 64 VLAN IDs and each VLAN ID can be loaded up to four times with four different frame types.

> Example: (VLAN ID 2 for Ethernet II)

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V2_EII VSLOT=1 VLAN=2

> NOTE: When adding 64 VLANs, the 64th VLAN must have a VLAN ID of 0 (63 VLANs are tagged and 1 VLAN is untagged)

> 2. Load the network drivers for the adapters on the team with all the frame types specified in step 1. Note that the one or more VLAN IDs specified in step 1 do not have to be specified when loading the network drivers. Each frame type loaded in step 1 needs to be loaded only once for each network driver, even if it is loaded multiple times with different VLAN IDs in step 1. Only Broadcom and Alteon® NIC adapters can be used. The ALT.LAN driver must be version 2.05b or later (released by Broadcom) and must include the keyword FORVLANS.

> Example: (Broadcom adapters)

>     LOAD ODINEB.NLM
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

> Example: (Alteon adapters)

>     LOAD ODINEB.NLM
>     LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_1_EII SLOT=1 FORVLANS
>     LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_2_EII SLOT=2 FORVLANS

> 3. Bind BASP.LAN to the NIC adapters in the team for each protocol.

> Example:

>     BASP BIND BASP_1_V2_EII B57_1_EII
>     BASP BIND BASP_1_V2_EII B57_2_EII

> If there are multiple VLANs (each with one or more frame types) loaded on the virtual adapter, it is only necessary to bind one frame type on one VLAN on the virtual adapter to the same frame type on the physical adapter. The other VLANs are automatically bound.

> 4. Bind protocols to BASP.LAN.

> Example:

>     BIND IP BASP_1_V2_EII ADDR=x.x.x.x MASK=x.x.x.x

> This example creates a team with two adapters using VLAN ID 2. Outbound packets are tagged with VLAN ID 2, and only similarly-tagged packets can be received by the adapters on the team. Additional VLANs with different VLAN IDs can be created on the same team. The maximum number of VLANs per virtual slot is 64. The valid range of values for VLAN IDs is from 1 to 4094. VLAN=0 indicates the VLAN is untagged and is the default. Use decimal numbers to specify the VLAN ID.

> The following are examples of multiple VLAN configurations:

>     LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=100
>     LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V200_EII VSLOT=1 VLAN=200
>     LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V300_EII VSLOT=1 VLAN=300

>     LOAD ODINEB.NLM
>     LOAD B57 FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57 FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

>     BASP BIND BASP_1_V100_EII B57_1_EII
>     BASP BIND BASP_1_V100_EII B57_2_EII

>     BIND IP BASP_1_V100_EII ADDR=172.16.210.1 MASK=255.255.0.0
>     BIND IP BASP_1_V200_EII ADDR=172.17.210.1 MASK=255.255.0.0
>     BIND IP BASP_1_V300_EII ADDR=172.18.210.1 MASK=255.255.0.0

> NOTES:

> 5. When BASP BIND BASP_1_V100_EII B57_1_EII is executed, the adapter B57_1_EII is bound to all three VLANs.
> 6. If you are unable to log on to the system after configuring BASP, add the following command lines before loading BASP:

>     UNLOAD SLPTCP

>     LOAD SLPTCP

> ##### Jumbo Frames

> Jumbo Frames are supported in all load balancing types of teams. The maximum frame size is automatically set to the smallest maximum frame size of all adapters in the team. Use appropriate keywords to enable Jumbo Frames when loading the adapter drivers.

> Example:

>     startup.ncf
>     SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=18000

>     autoexec.ncf
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 JUMBO=9000
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 JUMBO=9000
>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII

> #### Additional Command Line Keywords

> CHECKSUM = ON

> Enables BASP.LAN to offload TCP/UDP and IP checksums to the bound adapters (if supported by the operating system). This setting improves performance if some or all adapters in the team support hardware checksums. Be sure to load the adapter drivers with hardware checksums enabled.

> Example:

> A team of two BCM5700 NICs with hardware checksums enabled.

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII CHECKSUM=ON VSLOT=1
>     LOAD ODINEB.NLM
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII CHECKSUM=ON SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII CHECKSUM=ON SLOT=2
>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII

> NOSCREEN

> Disables the menu-driven screen when BASP.LAN is loaded for the first time.

> Example:

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 NOSCREEN

> GVRP

> Enables GVRP (GARP VLAN Registration Protocol) for the VLAN that is loaded. An untagged IEEE 802.2 frame type must be loaded in the virtual adapter and all bound physical adapters for GVRP to take effect. This is necessary because GVRP uses untagged 802.2 frames to advertise VLAN memberships. Use VLAN=0 FRAME=ETHERNET_802.2 in the load command to specify untagged IEEE 802.2 frame type.

> Example:

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V2_EII VSLOT=1 VLAN=2 GVRP
>     LOAD BASP.LAN FRAME=ETHERNET_802.2 NAME=BASP_1_E82 VSLOT=1 VLAN=0

> #### Editing the Autoexec.ncf File

> When an adapter configuration is saved, the NetWare install program adds load and bind statements to the Autoexec.ncf file. By accessing this file, you can verify the parameters configured for each adapter, add or delete parameters, or modify parameters.

> A valid autoexec.ncf file is shown below with various VLAN and teaming examples.

> Example:

>     # Team of 2 NIC adapters with frame type Ethernet_II and one VLAN, number 2

>     # Load BASP.LAN with the frame types and VLAN ID(s) specified.

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V2_EII VSLOT=1 VLAN=2

>     # Load the network drivers for the NIC adapters in the team with the same
>     # frames types.

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

>     # Bind BASP.LAN to the NIC adapters in the team for each protocol.

>     BASP BIND BASP_1_V2_EII B57_1_EII
>     BASP BIND BASP_1_V2_EII B57_2_EII

>     #Bind protocols to BASP.LAN.

>     BIND IP BASP_1_V2_EII ADDR=192.168.2.200 MASK=255.255.255.0

> Example:

>     # Team of 2 NIC adapters with frame type Ethernet_II and three VLANs, number 2,3,4

>     #Load BASP.LAN with the frame types and VLAN ID(s) specified.

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V2_EII VSLOT=1 VLAN=2
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V3_EII VSLOT=1 VLAN=3
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V4_EII VSLOT=1 VLAN=4

>     # Load the network drivers for the NIC adapters in the team with the same
>     # frame types and VLANs specified.

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

>     # Bind BASP.LAN to the NIC adapters in the team for each protocol
>     # NOTE: BASP BIND is only used for the first VLAN all other VLANs are automatically
>     # bound to the virtual adapter (VSLOT=1).

>     BASP BIND BASP_1_V2_EII B57_1_EII
>     BASP BIND BASP_1_V2_EII B57_2_EII

>     # Bind protocols to BASP.LAN.

>     BIND IP BASP_1_V2_EII ADDR=192.168.2.200 MASK=255.255.255.0
>     BIND IP BASP_1_V3_EII ADDR=192.168.3.200 MASK=255.255.255.0
>     BIND IP BASP_1_V4_EII ADDR=192.168.4.200 MASK=255.255.255.0

>     mount all

> NOTE: If you modify any adapter parameters, you must reboot the system before the changes takes effect. If you make changes and do not reboot, you may experience configuration problems.

> Example of Multiple SLB TEAMs with Multiple Frame Types

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1
>     LOAD BASP.LAN FRAME=ETHERNET_802.2 NAME=BASP_1_E82 VSLOT=1

>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_2_EII VSLOT=2
>     LOAD BASP.LAN FRAME=ETHERNET_802.3 NAME=BASP_2_E83 VSLOT=2

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_1_E82 SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_2_E82 SLOT=2

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_3_EII SLOT=3
>     LOAD B57.LAN FRAME=ETHERNET_802.3 NAME=B57_3_E83 SLOT=3
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_4_EII SLOT=4
>     LOAD B57.LAN FRAME=ETHERNET_802.3 NAME=B57_4_E83 SLOT=4

>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII
>     BASP BIND BASP_2_EII B57_3_EII
>     BASP BIND BASP_2_EII B57_4_EII

>     BIND IP BASP_1_EII ADDR=172.16.1.100 MASK=255.255.0.0
>     BIND IPX BASP_1_E82 NET=ABAB
>     BIND IP BASP_2_EII ADDR=172.18.1.100 MASK=255.255.0.0
>     BIND IPX BASP_2_E83 NET=BEEF

> NOTE: When B57_1_EII is bound to BASP_1_EII, B57_1_E82 is also bound to BASP_1_E82. IPX load balance works only with an all-Broadcom adapter or an all-Alteon® adapter configuration. Values for VLSOT range from 1 to 4 (only four teams can be configured).

> Example of VLAN with BASP

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=100
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V200_EII VSLOT=1 VLAN=200
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_V300_EII VSLOT=1 VLAN=300

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

>     BASP BIND BASP_1_V100_EII B57_1_EII
>     BASP BIND BASP_1_V100_EII B57_2_EII

>     BIND IP BASP_1_V100_EII ADDR=172.16.210.1 MASK=255.255.0.0
>     BIND IP BASP_1_V200_EII ADDR=172.17.220.1 MASK=255.255.0.0
>     BIND IP BASP_1_V200_EII ADDR=172.18.230.1 MASK=255.255.0.0

> NOTE: When B57_1_V100_EII is bound to B57_1_EII, B57_1_EII is also bound to the other VLANs on the same VSLOT. VLAN refers to the VLAN ID, and valid value for VLAN ID ranges from 1 to 4094.

> Example of TRUNKING with BASP

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 MODE=TRUNK

>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2

>     BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII

>     BIND IP BASP_1_EII ADDR=172.16.210.1 MASK=255.255.0.0

> NOTE: Switch ports must be configured for trunking (for example: FEC or GEC for Cisco switches)

> Example of GVRP with BASP

>     LOAD ODINEB.NLM
>     LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 VLAN=100 GVRP
>     LOAD BASP.LAN FRAME=ETHERNET_802.2 NAME=BASP_1_E82 VSLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_1_E82 SLOT=1
>     LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2
>     LOAD B57.LAN FRAME=ETHERNET_802.2 NAME=B57_2_E82 SLOT=2 BASP BIND BASP_1_EII B57_1_EII
>     BASP BIND BASP_1_EII B57_2_EII BIND IP BASP_1_EII ADDR=172.16.210.1 MASK=255.255.0.0

> NOTES:

> - In this example, VLAN 100 is advertised to the switch using GVRP.
> - The untagged 802.2 frame must be loaded to allow sending and receiving GVRP frames. Switch ports must be configured with GVRP enabled.

> #### Using INETCFG

> When INETCFG is used to set up teaming, the physical adapters being added to the team must not have any protocols bound to them before they are added to the team. To ensure the proper operation of the team, the physical adapters in a team should have only the BASP protocol bound to them.

> Load inetcfg.nlm. When you are prompted, accept the configuration. On the Internetworking Configuration console:

> 1. Select Board, and then press ENTER.
> 2. Press INSERT.
> 3. Select a physical device driver, such as B57.
> 4. Press ENTER, and then type a name, such as B57_1.
> 5. Press ESC, and then select Yes to save the configuration. Repeat steps 2 through 5 to configure another adapter. Name subsequent adapters B57_2, B57_3, and so on.
> 6. Press INSERT.
> 7. Select a virtual device driver, such as BASP.
> 8. Press ENTER, and then type a name, such as BASP_1. In this console, virtual slot number, Balance Mode, and VLAN ID can be selected.

> NOTES:

> 9. The first virtual adapter (TEAM) should have a virtual slot of 1.
> 10. VLAN 0 (zero) is a default, and this VLAN is untagged.
> 11. Press ESC, and then select Yes to save the configuration.
> 12. Scroll down to Protocols, and then press ENTER to select.
> 13. Scroll down to User-specified Protocol, and then press ENTER to select.
> 14. Press INSERT.
> 15. Type the name for the protocol, such as `BASP1` for TEAM 1, `BASP2` for TEAM 2, `BASP3` for TEAM 3, or `BASP4` for TEAM 4.
> 16. Press ESC to return to the Internetworking Configuration console.
> 17. Select Bindings.
> 18. Press INSERT to configure the protocol.
> 19. Select TCP/IP, then press ENTER.
> 20. Select A Network Interface, then press ENTER.
> 21. Select a virtual adapter (BASP, for example).
> 22. Define the IP address.
> 23. Press ESC, and then select Yes to save.

> Repeat steps 16 through 21 to configure IPX and multiple frame types.

> NOTE: The physical adapters must be configured with the same frame types as the virtual team

> 1. Press INSERT to bind the physical adapter to a virtual team.
> 2. Select User-specified Protocol.
> 3. Select A Network Interface, and then press ENTER.
> 4. Select a physical adapter (B57, for example).
> 5. Type BASP1 for Protocol.
> 6. Select a frame type, type any special parameters (refer to B57.LAN readme.txt for parameters), press ESC, then select Yes to save.

> NOTES:

> 7. Use names such as `BASP1` for TEAM 1, `BASP2` for TEAM 2, `BASP3` for TEAM 3 and `BASP4` for TEAM 4.
> 8. When you modify a team, you may need to reboot after reinitialization for the changes to take effect.

> Repeat steps 22 through 27 to configure an additional physical driver and to configure additional frame types. The configuration can be viewed in the View Configuration - All INETCFG Commands console.

> #### SNMP Agent

> This SNMP agent is designed to support the configuration information pertaining to the Broadcom BASP driver for NetWare.

> ##### Installation

> When the BASP.LDI driver is installed using nwconfig or nwinstall, the driver automatically copies the BASP.LAN, bmapi.nlm, and bsnmp.nlm files to the system.

> After you configure and run the BASP and bind the BASP to network adapters, load the Broadcom SNMP Instrumentation Agent (BSNMP) as follows:

> From the NetWare Server console command line interface, type:

>     load bmapi.nlm
>     load bsnmp.nlm

> ##### SNMP Objects

> BASP SNMP objects are provided in the BASP-Config.MIB file, which is on your installation CD. The snmpget and snmpgetnext commands can be used to receive the BASP SNMP objects such as:

>     snmpget localhost public BASP-Config-MIB::btTeamNumber
>     snmpgetnext localhost public BASP-Config-MIB::btTeamNumber

> NOTE: Only BASP configuration information is available through SNMP in NetWare. Statistical events are only available for the base adapters

> ##### Files

> BASP.LAN
> bmapi.nlm
> bsnmp.nlm
> BASP-CONFIG.MIB

> Back to Contents Page