A network device driver must be installed before the Broadcom NetXtreme 57XX
Gigabit Ethernet Controller can be used with your Novell NetWare system.
Before you can successfully install the adapter driver for Novell NetWare,
the adapter card must be physically installed in the server and, typically,
NetWare operating system software must already be running on the server. Make
sure that your server meets the hardware and operating system software requirements
described in Installing the Hardware.
To enable the Gigabit Ethernet Adapter to function correctly, you need to install
the latest Novell NetWare support pack files. The NetWare support pack or patch
file(s) needed for the operating system running on your server are indicated
below:
The latest support pack can be found at: http://support.novell.com/misc/patlst.htm
NetWare 5.1
NetWare 6.0
NetWare 6.5
NOTES:
PCI-X Systems. For systems with PCI-X you must install
driver version v2.10 or later. For new installs of NetWare with the
latest drivers, you must create a C:\nwupdate directory and copy the
latest B57.lan and B57.ldi files into this directory before installing
the operating system.
NetWare 4.2/5.1/6.0. If you are installing NetWare
4.2/5.1/6.0 for the first time on a server, the driver is installed
during the operating system installation process. Install the NetWare
5.1 support pack after you have successfully installed the operating
system on the server.
Installing
NetWare Server 4.2/5.1/6.0 Driver Software
NOTE: The following instructions are for installing Novell NetWare Server
4.2, 5.1, or 6.0 driver software. For instructions on installing Novell
NetWare Server 6.5 driver software, go to Installing
NetWare Server 6.5 Driver Software.
Verify that the server has the latest support pack available installed. The
latest support packs can be found at: http://support.novell.com/misc/patlst.htm.
You may want to create an archive disk (see Creating a
Driver Disk) by copying all the files from the CDROM\NetWare\Driver directory
onto a floppy disk. If you choose to use the CD directly, ensure that the CDROM.NLM
file is loaded and that you know the NetWare volume name for the CD.
From the NetWare Server console, type LOAD NWCONFIG
and press ENTER.
From the Configuration Options menu, select Driver options
and press ENTER.
Select Configure network drivers and press ENTER.
Select Select an additional driver and press ENTER.
Insert the Dell Resource CD or the archive floppy disk, and then select
Install an unlisted driver by pressing INSERT.
If you inserted the archive floppy disk, press ENTER. If you have the Dell
Resource CD mounted as a NetWare volume, press F3 and type Volume
Name: NetWare\Driver as the source path, where Volume
Name is the name of the NetWare volume for the Dell Resource CD,
and NetWare\Driver is the directory containing
the specific files on the Dell Resource CD needed for this installation.
Press ENTER to select the highlighted driver.
Select Yes and press ENTER.
Select Yes and press ENTER to copy the .ldi file. This is the installation
script for the driver.
Select Save parameters and load driver to continue.
Select Exit to return to the server console prompt.
NOTE: If you are performing an initial installation of NetWare 4.2/5.1/6.0
and have more than 2 network adapters installed, the install program allows
you to allocate the actual number of packet receive buffers needed by the
adapter. During installation, the RxBuffers value is set to 32, the minimum
number of buffers the driver requires for each adapter. Although this setting
affects adapter performance, it allows the installation of the operating
system and up to 8 adapters during initial installation process. After you
complete the installation, increase the number of buffers allocated to the
driver, as described in Viewing
or Modifying Adapter Properties.
After NetWare 4.2/5.1/6.0 has been successfully installed, set
the minimum packet Receive Buffers property in the Startup.ncf file to 1500
for each adapter in the server. Set the maximum packet receive buffers to
three times the minimum packet receive buffers. Typically, 4 MB of RAM are
required per 1000 receive buffers. For more information, see Viewing
or Modifying Adapter Properties.
In the Autoexec.ncf file, delete the packet Receive Buffers property (RxBuffers
= 32) in the load statement for this adapter. Deleting the Receive Buffers
phrase from the load statement resets the Receive Buffers property to the
default value of 200.
NOTE: The server must be restarted for the new configuration to take effect.
Example: The default maximum number of receive buffers for the system
is 500, and the default minimum is 128. Edit the Startup.ncf file to have the
following entries. The actual number of receive buffers is a function of the
number of ports in the server. The following is an example for a server with
8 ports installed:
set maximum packet receive buffers = 36000
set minimum packet receive buffers = 12000
Installing
NetWare Server 6.5 Driver Software
NOTE: The following instructions are for installing the NetWare Server
6.5 driver software. For instructions on installing NetWare Server 4.2,
5.1, or 6.0 driver software, go to Installing
NetWare Server 4.2/5.1/6.0 Driver Software.
You may want to create an archive disk (see Creating
a Driver Disk) by copying all the files from the CDROM\NetWare\Driver directory
onto a floppy disk. If you choose to use the CD directly, ensure that the CDROM.NLM
file is loaded and that you know the NetWare volume name for the CD.
From the NetWare Server console, type HDETECT and press
ENTER.
From Options, press ENTER to accept Platform Support
Module and Hot-Plug Support Module and continue
detecting devices.
From Options, scroll down to select Modify
and press ENTER to change focus to detected devices.
Scroll down to Network boards and press ENTER.
From Additional Driver Options, scroll down to Modify
and press ENTER.
Insert the CD or archive floppy disk you created, and then select the Add
option by pressing INSERT.
Select the Install an unlisted driver option, by pressing INSERT.
If you inserted the archive floppy disk, press ENTER. If you have the CD
mounted as a NetWare volume, press F3 and type Volume Name: NetWare\Driver
as the source path, where Volume Name is the name of the NetWare
volume for the CD, and NetWare\Driver is the directory of the specific
files on the CD needed for this installation.
Press DOWN ARROWorTABto switch back to Additional
Driver Options.
Choose Return to driver summary and press ENTER.
Choose Continue in Options .
Choose Continue from Protocol Options
unless you want to configure and bind protocols before continuing. Installation
is now complete.
When an adapter configuration is saved, the NetWare installation program adds
load and bind statements to the Autoexec.ncf
file. By accessing this file, you can view and modify properties or add properties
for each network adapter.
NOTE: The Novell monitor program and the config command
are also useful for viewing driver configuration properties. For information
on how to use these programs, see the Utilities Reference in your Novell
NetWare online documentation.
The properties that can be defined in the load statements are described below:
Configuration Properties for B57.lan driver:
TxDescriptors=
Initializes Descriptor resources on the adapter for transmits.
Min = 100
Max = 512
Default = 120
RxBuffers=
This is to pre-allocate receive ECBs & Receive adapter
resources. This setting may be affected by the the NetWare Server maximum/minimum
packet receive buffer settings.
Min = 32
Max = 1000
Default = 200
Speed=
This keyword forces the line speed of the adapter. When this
keyword is used, the switch to which the adapter cable is connected must be
forced. Otherwise, the adapter and switch may run at different duplex modes.
It is important to have the switch and adapter set properly. The best way to
ensure good connectivity is to not set the speed keyword and allow for automatic
link setup (auto-negotiation).
AUTO
10FD
10HD
100FD
100HD
The default setting is AUTO. Note that 1000 Mbit/s speed is
auto-detected and cannot be forced.
Link=
This keyword is set to AUTO to allow the adapter to auto-negotiate
with a switch using the Speed keyword as an advertised speed
upper limit. It is best to allow for auto-negotiation of the adapter and switch
by not setting this keyword or the Speed keyword.
AUTO
FORCE
The default is Auto. When set to FORCE, auto-negotiation is
disabled and the link speed is forced to a specific value.
RxTicks=
Enables the use of batching receives within a specific time
period.
Min = 0 (Disabled)
Max = 5000000 (5 seconds)
Units are in microseconds, The default value is 300.
TxTicks=
Enables the use of a transmit tick threshold interrupt within
a specific time period.
Min = 0 (Disabled)
Max = 5000000 (5 seconds)
Units are in microseconds. The default value is 200.
TxPacketsPer=
Enables allowing an interrupt to occur after a specific amount
of packets is transmitted.
Min = 0 (Disabled)
Max = 100
The default value is 20.
RxPacketsPer=
Enables allowing an interrupt to occur after a specific amount
of packets is received.
Min = 0 (Disabled)
Max = 100
The default value is 75.
CheckSum=
Enables or disables the transmit and receive checksum offload
feature. Checksum offload support is only for TCP/IP packets; therefore, the
default setting for checksum offload is OFF.
OFF
ON
TX
RX
TxFlow=
This keyword allows enabling/disabling of transmit flow control.
ON
OFF
The default setting is OFF.
RxFlow=
This keyword allows enabling/disabling of receive flow control.
ON
OFF
The default setting is OFF.
PDriver=
Enables the driver to operate in persistent driver mode. Use
only if the adapter is placed in a hot-plug slot and only if you must swap with
an adapter that is exactly the same.
OFF
ON
The default setting is OFF.
NODE=
A Novell NetWare keyword that allows an input Ethernet node
address to replace the adapter factory-programmed Ethernet node address until
a subsequent reboot.
NODE=nnnnnnnnnnnn
FRAME=
A Novell NetWare keyword for specifying the frame type.
A Novell NetWare keyword used to set a system-wide unique hardware
instance number (HIN) that may be the physical slot number on a slot-based bus
such as PCI.
SLOT=n
Jumbo=
Enables Jumbo frame support. When enabled, jumbo packets of
up to 9000 bytes are supported.
Jumbo=1536–9100
The default setting is no jumbo packets.
NOTES:
Jumbo frames are supported only on NetWare 6.0 and later. Also, the
first frame loaded must be ETHERNET_II.
Jumbo frame support must have the following text in the Startup.ncf
file: "Set maximum physical receive packet size = 18000."
P3=
This keyword is used when running Perform3.exe tests and may
be used to increase performance on networks running with many IPX clients.
Set P3=1 when running the Perform3 test back to back to a single
client.
Set P3=2 when running the Perform3 test with many clients.
The default setting is P3=0.
Spuriousfix=
When this keyword is set to 1 (Spurious Fix is ON), the spurious
interrupts count that is sometimes displayed on the NetWare console may be reduced.
Setting this keyword to 0 (Spurious Fix is OFF) may enhance performance.
0
Spurious Fix is OFF
1
Spurious Fix is ON
The default value is 1 (Spurious Fix is ON).
Poll=
Disables the interrupt driven mode. When set to Poll=1, the
driver does not use interrupts, but is polled by the NetWare operating system.
This is a common feature supported in NetWare. The poll mode may increase driver
performance in some environments.
1
ON
0
OFF
The default value is 0 (Poll mode is OFF).
Wirespeed=
This feature provides adapter link and data integrity even if
the adapter is attached to a questionable cable and/or switch. For example,
an adapter that is trying to connect at 1000 Mbit/s on a Category 3 cable ordinarily
would not link. With Wirespeed set to 1, the link is made at 100 Mbit/s.
1
ON
0
OFF
The default value is 1 (wirespeed is ON).
Model=
This keyword allows the addition of a subsystem ID of a specific
NIC so that the driver loads only on the first NIC found with a matching subsystem
ID. For example, MODEl= 0x14e4. The default value is 0
MagicP=
When MagicP=1, the driver enables the adapter to wake up the
system when a Magic Packet™ frame is received after the system is shut
down. MagicP=0 is the default setting with the adapter having no wake-up ability.
1
ON
0
OFF
The default value is 0 (No wake-up capability).
Fiber=
The driver has support for the 1000FD fiber adapter. The fiber
auto-negotiates link with a fiber switch even though it only supports 1000FD.
In some cases, the user may want to force the adapter to 1000FD.
AUTO (default)
FORCE
NOTE: If you modify any of the adapter properties, you must reboot the
system before the changes take effect. If you make changes and do not reboot,
you may experience problems.
A valid Autoexec.ncf file is shown below. One set of load
and bind commands (in bold) is added for each frame
type the adapter is configured to support.
SET Daylight Savings Time Offset = 1:00:00
SET Start Of Daylight Savings Time = (MARCH SUNDAY LAST 2:00:00 AM)
SET End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
SET Time Zone = TPST8TPDT
# Note: The Time zone information mentioned above
# should always precede the SERVER name.
# WARNING!!
FILE SERVER NAME DL760
# WARNING!!
# If you change the name of this server, you must update
# the server name in all the licenses that are assigned
# to it using iManager.
SERVERID 487B10D
LOAD ODINEB.NLM
LOAD IPXRTR
LOAD B57.LAN SLOT=5 FRAME=ETHERNET_802.2 NAME=B57_1_E82
BIND IPX B57_1_E82 NET=BF857E4F
LOAD IPXRTRNM
LOAD TCPIP
To remove the drivers from the Autoexec.ncf file, locate the load
and bind command lines associated with the Broadcom driver
and remark them out by inserting the # symbol at the beginning of each command
line, or by deleting the statement.
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-Balancing mode (see below).
**In IEEE 802.3ad mode, the number of NIC interfaces aggregated is automatically
determined through LACP (see below).
Smart Load-balance (SLB) is a protocol-specific scheme and the level of support
for IP, IPX, and other protocols are listed below.
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.
For optimum fault tolerance and recovery operations, BASP.LAN relies on the
NIC 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 BASP.LAN, ODINEB.NLM must be loaded before the NESL-compliant ODI
drivers are loaded.
Do the following to check if a NIC driver supports NESL events: Load BASP.LAN
and create a team by binding the NIC adapter to the virtual slot (see instructions
and examples below). In the Virtual Adapter X Team Members console,
the link status of all bound NIC adapters is shown. Disconnect or connect the
NIC adapter cable. If the NIC driver supports NESL events, the link status should
change immediately.
Load BASP.LAN just like a standard LAN driver with all necessary frame
types for the team. BASP.LAN 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:
Be sure to load BASP.LAN before loading your standard LAN driver.
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
Load the network drivers for the NIC adapters that will be part of the team.
The frame types loaded should be the same for all adapters in the team and
same as those loaded for BASP.LAN in step 1. Do not bind protocols directly
to these adapters. Be sure to load ODINEB.NLM (a Novell supplied NLM) before
all network drivers.
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.
Bind BASP.LAN to the NIC adapters in the team by using a custom BASP BIND
command at the console.
NOTE: if there are multiple frame types loaded on the virtual and the
physical adapters, it is only necessary to bind one frame type on the virtual
adapter to the same frame type on the physical adapter. The other frame
types will be automatically bound.
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.
In SLB mode, IPX traffic is only load-balanced on the send side, but
not on the receive side.
For optimum fault tolerance and recovery operations, BASP.LAN 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.
Do the following to check if an adapter driver supports
NESL events. Load BASP.LAN 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 Membersscreen 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
NICs in the team. Use the parameter LACP=PASSIVE to change LACP to passive mode
for all NICs in the team. Note that at least one side (server or switch) must
be in LACP active mode for it to work.
After one or more NIC 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.
In Smart Load Balancing™ (SLB) mode, only one adapter can be designated
as a hot standby. Use the keyword STANDBY in the BASP BIND
command to bind an adapter as a hot standby.
In the above example, B57_1_EII and B57_2_EII are bound as primary and hot
standby adapters respectively. Note that standby is only valid for Smart Load
Balancing mode.
NOTE: No traffic is passed to the standby adapter until the primary adapter
fails.
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:
Load BASP.LAN 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 4 times with 4 different frame types.
NOTE: When adding 64 VLANs, the 64th VLAN must have
a VLAN ID of 0 (63 VLANs are tagged and 1 VLAN is untagged).
Load the network drivers for the NIC adapters in 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. And each
frame type loaded in step 1 only needs to be loaded 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. ALT.LAN
must be version 2.05b or newer released by Broadcom and must include the keyword
FORVLANS.
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.
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 2 adapters using VLAN ID 2. Outbound packets
will be tagged with VLAN ID 2 and only similarly tagged packets will be received
by the NIC adapters in the team. Additional VLANs with different VLAN IDs
can be created in the same team. The Maximum number of VLANs per virtual slot
is 64. The valid range of 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:
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:
When BASP BIND BASP_1_V100_EII B57_1_EII is executed, the adapter
B57_1_EII is bound to all three VLANs.
If you are unable to log in to the server after configuring BASP,
add the following command lines before loading BASP.
Jumbo Frames are supported in all balance modes. The maximum frame size will
be automatically set to the smallest maximum frame size of all NICs in the team.
Use appropriate keywords to enable jumbo frames when loading the NIC drivers.
Example
startup.ncf
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=18000
Enables BASP.LAN to offload TCP/UDP and IP checksums to the bound NIC adapters
if supported by the operating system. This improves performance if some or all
NIC adapters in the team support hardware checksums. Be sure to load the NIC
drivers with hardware checksums enabled.
Example
A team of two BCM5700 NICs with hardware checksums enabled.
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.
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 1
# 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.
# 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).
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
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. VLSOT range is from 1 to 4 (only
four teams can be configured).
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 bind B57_1_V100_EII to B57_1_EII,
B57_1_EII are also bound to the other VLANs on the same VSLOT. VLAN refer
to VLAN ID, and valid VLAN ID ranges from 1 to 4094.
When INETCFG is used to set up teaming, the physical NICs (boards) 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 NICs 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
Configurationconsole:
Select Board, and then press ENTER.
Press INSERT.
Select a physical device driver, such as B57.
Press ENTER, and then type a name, such as B57_1.
Press ESC, and then select Yes to save the configuration. Repeat
steps 2 through 5 to configure another board. Name subsequent boards B57_2,
B57_3, and so on.
Press INSERT.
Select a virtual device driver, such as BASP.
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:
The first Virtual adapter (TEAM) should have virtual slot of 1.
VLAN 0 (zero) is a default and this VLAN is untagged.
Press ESC, and then select Yes to save the configuration.
Scroll down to Protocols, and then press ENTER to select.
Scroll down to User-specified Protocol, and then press
ENTER to select.
Press INSERT.
Type the name for the protocol, such as BASP1 for TEAM
1, BASP2 for TEAM 2, BASP3 for TEAM 3 and
BASP4 for TEAM 4.
Press ESC to return to the Internetworking Configuration
console.
Select Bindings.
Press INSERT to configure the protocol.
Select TCP/IP, then press ENTER.
Select A Network Interface, then press ENTER.
Select a virtual adapter, for example BASP.
Define the IP address.
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.
Press INSERT to bind the physical adapter to a virtual team.
Select User-specified Protocol.
Select A Network Interface, then press ENTER.
Select a physical adapter, for example B57.
Type BASP1 for Protocol.
Select a frame type, type any special parameters (refer to B57.LAN readme.txt
for parameters), press ESC, then select Yes to save.
NOTES:
Use names such as BASP1 for TEAM 1, BASP2
for TEAM 2, BASP3 for TEAM 3 and BASP4
for TEAM 4.
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.
This SNMP agent is designed to support the configuration information pertaining
to the Broadcom BASP driver for NetWare.
Installation
When installed from NWCONFIG or NWINSTALL,
the BASP.LDI automatically copies the BASP.LAN, bmapi.nlm, and bsnmp.nlm files
to the server.
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
Dell Resource 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.
