Broadcom Advanced Server Program Driver Software (NetWare)
Installing NetWare Server 5.1/6.0 Driver Software
Installing NetWare Server 6.5 Driver Software
Configuration Properties for the B57.lan driver
Removing Drivers from Autoexec.ncf
A network device driver must be installed before the Broadcom NetXtreme Gigabit Ethernet adapter 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 system and, typically, NetWare operating system software must already be running on the system. Make sure that your system meets the hardware and operating system software requirements described in Installing the Hardware.
To enable the Broadcom NetXtreme adapter to function correctly, you must 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:
NetWare Version
|
Support Pack
|
Files to be Installed
|
---|---|---|
NetWare 5.1
|
Latest support pack
|
The latest support pack can be found at: http://download.novell.com/index.jsp?product_id=&search=Search&families=2639&version=8130&date_range=&keywords=&sort_by=&x=25&y=8
|
NetWare 6.0
|
Latest support pack
|
The latest support pack can be found at: http://download.novell.com/index.jsp?product_id=&search=Search&families=2639&version=7486&date_range=&keywords=&sort_by=&x=17&y=7
|
NetWare 6.5
|
Latest support pack
|
The latest support pack can be found at: http://download.novell.com/index.jsp?product_id=&search=Search&families=2639&version=12127&date_range=&keywords=&sort_by=&x=32&y=4
|
NOTES:
NOTE: The following instructions are for installing Novell NetWare Server 5.1 or 6.0 driver software. For instructions on installing Novell NetWare Server 6.5 driver software, see Installing NetWare Server 6.5 Driver Software.
Verify that the system has the latest support pack available installed. See Table 1 for information on obtaining the latest support pack for your version. 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 elect to use the CD directly, ensure that the CDROM.NLM file is loaded and that you know the NetWare volume name for the CD.
NOTE: If you are performing an initial installation of NetWare 5.1/6.0 and have more than two 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.
NOTE: The system 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 system. The following is an example for a system with 8 ports installed:
set maximum packet receive buffers = 36000
set minimum packet receive buffers = 12000
NOTE: The following instructions are for installing the NetWare Server 6.5 driver software. For instructions on installing NetWare Server 5.1 or 6.0 driver software, see Installing NetWare Server 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 disk. If you elect to use the CD directly, ensure that the CDROM.NLM file is loaded and that you know the NetWare volume name for the CD.
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:
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 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. Forced 1000 Mbit/s speed is not needed for copper links. Auto-negotiation is the proper supported configuration under the IEEE specification.
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 and 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 (default)
RxFlow=
This keyword allows enabling/disabling of receive flow control.
ON
OFF (default)
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 (default)
ON
NODE=
Allows an input Ethernet node address to replace the adapter factory-programmed Ethernet node address until a subsequent reboot.
NODE=nnnnnnnnnnnn
FRAME=
Specifies the frame type. The default value is ETHERNET_802.2.
ETHERNET_II
ETHERNET_802.3
ETHERNET_802.2
ETHERNET_SNAP
SLOT=
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=15369100
The default setting is no jumbo packets.
Notes:
P3=
This keyword is used when running Perform3.exe tests and may be used to increase performance on networks running with many IPX clients.
P3=1 when running the Perform3 test back to back to a single client
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.
Spuriousfix=0 (Spurious Fix is OFF)
Spuriousfix=1 = (Spurious Fix is ON) (default)
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.
0 = OFF (default)
1 = ON
Wirespeed=
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.
0 = OFF
1 = ON (default)
Model=
Allows the addition of a subsystem ID of a specific adapter so that the driver loads only on the first adapter 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.
0 = OFF (default)
1 = ON
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 IPXRTRNM
LOAD TCPIP
LOAD B57 SLOT=2 FRAME=Ethernet_802.2 NAME=B57_1_E82
BIND IPX B57_1_E82 NET=FAFD3D25
LOAD B57 SLOT=2 FRAME=Ethernet_802.3 NAME=B57_1_E83
BIND IPX B57_1_E83 NET=5A2D8D6D
LOAD B57 SLOT=2 FRAME=Ethernet_SNAP NAME=B57_1_ESP
BIND IPX B57_1_ESP NET=477A35BD
LOAD B57 SLOT=2 FRAME=Ethernet_II NAME=B57_1_EII
BIND IPX B57_1_EII NET=C3C8F2E4
BIND IP B57_1_EII ADDR=172.16.1.1 MASK=ff.ff.ff.0
mount all
SEARCH ADD SYS:\JAVA\BIN
SEARCH ADD SYS:\JAVA\NWGFX
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.
Example:
# LOAD B57 SLOT=2 FRAME=Ethernet_802.2 NAME=B57_1_E82
# BIND IPX B57_1_E82 NET=FAFD3D25
# LOAD B57 SLOT=2 FRAME=Ethernet_802.3 NAME=B57_1_E83
# BIND IPX B57_1_E83 NET=5A2D8D6D
# LOAD B57 SLOT=2 FRAME=Ethernet_SNAP NAME=B57_1_ESP
# BIND IPX B57_1_ESP NET=477A35BD
# LOAD B57 SLOT=2 FRAME=Ethernet_II NAME=B57_1_EII
# BIND IPX B57_1_EII NET=C3C8F2E4
# BIND IP B57_1_EII ADDR=172.16.1.1 MASK=ff.ff.ff.0
NOTE: If you modify the Autoexec.ncf file, you must reboot the server before the changes take effect.