Editing The Autoexec.ncf File - Dell Broadcom NetXtreme Family of Adapters User Manual

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