ODI Driver Software: Broadcom NetXtreme II™ Network Adapter User Guide
ODI Client32
The Open Data-Link Interface (ODI) driver software allows LAN drivers to work together irrespective of differences between the hardware and/or the protocol stacks of communicating systems. An intervening layer, called the link support layer (LSL), is responsible for routing different packet types between local area network (LAN) drivers and protocol stacks.
Installing the Driver Software
The ODI Driver software must be installed on a system having an MS-DOS operating system. MS-DOS 6.22 is recommended.
Preinstallation Requirements
- Copy the Broadcom ODI driver files to a floppy disk. Copy the BX2.LAN and BX2.LDI files for the Client32 driver.
- Go to the Novell web site http://www.novell.com/coolsolutions/tools/1066.html and download the NetWare DOS Client files to the hard disk: download the dw271e.zip file for the Client32 installation.
Installing the Novell NetWare Client32 Driver for MS-DOS
- Extract the dw271.zip file to a temporary directory on the hard disk.
- Double-click the dw271e.exe file.
- Type
y
and then press ENTER when you are prompted for a response.- Restart your system in MS-DOS mode.
- Change to the directory where the extracted files are located.
- Type
install
, and then press ENTER.- Read the agreement, and then press ENTER to accept the agreement.
- Using the UP ARROW or DOWN ARROW key as necessary, highlight Novell Client for DOS (required), and then press F10 to save and continue.
- Highlight 32-bit LAN Drivers, and then press F10 to save and continue.
- Insert the floppy disk containing the Broadcom 32-bit LAN driver files into the floppy disk drive.
- Highlight USER SPECIFIED 32-BIT DRIVER, and then press ENTER.
- Press ENTER.
- Highlight NetXtreme II Gigabit Ethernet Driver, and then press ENTER.
- Press ENTER.
- Select Receive Buffers, type
32
for the value, and then press F10 to save and continue.
NOTE: Do not change the default settings for any of the other items in the Installation Configuration Summary.
- Press F10 to save and continue. The Bx2.LAN and Bx2.LDI files are copied to the directory.
- Restart the system to complete the install.
- As the files are being loaded, the system attempts to attach to a NetWare server using the frame types specified in Net.cfg. If the connection is successful, a dialog box is displayed.
- Change to drive F and log on to the NetWare server.
NOTE: The driver loads during system configuration, and the Broadcom banner, the adapter name, the MAC address, the IRQ number, the detected line speed, and the bus number (BusNum) and device number (DevNum) of the adapter are displayed. If the driver fails to load, an initialization fail message appears.
Configuring the Driver Software
The ODI driver software can be configured by adding specific optional keywords to the Net.cfg file.
If multiple (or multiport) Broadcom NetXtreme II adapters are installed in a system, the ODI driver software loads by default on the adapter/port that has a good link. If two or more adapters have a good link, the ODI driver software loads on the adapter having the latest Device ID. If two or more adapters that have a good link have the same Device ID, the ODI driver software loads on the adapter that is located in the slot having the lowest bus number.
If it is necessary to have the ODI driver load on certain adapters in a certain order, the BusNum, DevNum, and FuncNum keywords can be used. Do not use these keywords unless you know how to configure PCI devices.
The BusNum keyword value, which represents the PCI bus number in which the adapter is located, is a hexadecimal number ranging from 0 to FF.
The FuncNum keyword value, which represents the function (port) number of a multiport adapter, is a hexadecimal number with 0 representing the first port and 1 representing the second port.
The DevNum keyword value, which represents the assigned device number, is a hexadecimal number ranging from 0 to 1F.
NOTES:
- At the end of the ODI driver software installation process, note the BusNum and DevNum values that are displayed. Alternatively, use Broadcom Advanced Control Suite 2 (see Using Broadcom Advanced Control Suite 2) to view the bus number, function (port) number, and device number assigned to each adapter (Windows users only).
- The values for the BusNum, DevNum, and FuncNum keywords are displayed in hexadecimal notation when the driver loads on the adapter.
Example BusNum, DevNum, and FuncNum keyword entries for loading the ODI driver on multiple adapters in a certain order are shown below:
PROTOCOL <protocol name>BIND BX2BIND BX2LINK DRIVER BX2BUSNUM 1DEVNUM 9FRAME <frame #1 name>LINK DRIVER BX2BUSNUM 1DEVNUM AFRAME <frame #2 name>The LineSpeed keyword is used to force the speed of the network connection. The LineSpeed keyword requires a decimal number and of either 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and can be achieved only through auto-negotiation. For the sake of simplicity, the driver performs auto-negotiation when the line speed is set to a value of 1000.
The Duplex keyword is used to force the duplex mode of the adapter. The Duplex keyword requires a text string of either HALF or FULL. When the Duplex keyword is used, the LineSpeed keyword must also be used. If neither keyword is used, the network adapter defaults to auto-negotiation mode.
Example keyword entries for the LineSpeed, and Duplex keywords are shown below:
LINK DRIVER BX2LINESPEED 100DUPLEX FULLDOS ODI
The Open Data-Link Interface (ODI) driver software allows LAN drivers to work together irrespective of differences between the hardware and/or the protocol stacks of communicating computers. An intervening layer, called the link support layer (LSL), is responsible for routing different packet types between LAN drivers and protocol stacks.
Installing the Driver Software
Installing the DOS/ODI driver software involves the following steps:
Preinstallation Requirements
- Verify that the Broadcom Ethernet controller driver software has been installed on your computer and install it if it has not (see Installing the Driver Software). Otherwise, you cannot use a Broadcom Ethernet controller in the DOS environment.
NOTE: To successfully install the controller driver for DOS, the controller must be installed in the computer before you install the driver.
- Install the DOS 6.22 files on your computer hard disk or have them available on a removable storage device.
Installing the DOS ODI Driver on DOS 6.22
- Copy the DOS ODI driver file to the root directory of the hard disk.
- Copy Lsl.com, Ipxodi.com, and Vlm.com to the same directory (these files are provided by Novell).
- Edit the Autoexec.bat file by adding the following lines:
C:\LSL
C:\BX2
C:\IPXODI
C:\VLM- Edit the Net.cfg file and place the file in the same location as the Autoexec.bat file (located in drive C) to configure the driver to bind with different frame types.
Example:
LINK DRIVER BX2
FRAME ETHERNET_802.2
FRAME ETHERNET_802.3
FRAME ETHERNET_II
FRAME ETHERNET_SNAP
NetWare DOS Requester
FIRST NETWORK DRIVE=F
NETWARE PROTOCOL=NDS BIND
PROTOCOL IPXODI- Restart the computer to complete the installation.
- As the files are being loaded, the computer attempts to attach to a NetWare server using the frame types specified in Net.cfg. If the connection is successful, a dialog box appears.
- Change to drive F and log onto the NetWare server.
F: <enter>F:\login admin <enter>
NOTE: The driver loads during system configuration, and the Broadcom banner, the controller name, the MAC address, the IRQ number, the detected line speed, and the BUSNUM and DEVNUM of the controller are displayed. If the driver fails to load, an initialization fail message appears.
Configuring Parameters for the BX2.com Driver (in the Net.cfg file)
The following are optional custom keywords used in the Net.cfg file:
BUSNUM
DEVNUM
FUNNUM
SUBVID
MODELThe first two keywords (BUSNUM and DEVNUM) are used together and have been included for manufacturing purposes. Do not use them unless you are familiar with PCI device configuration. These two keywords are needed if multiple Broadcom NetXtreme II controllers are installed on a system, and each controller must be loaded in a specific order.
BUSNUM specifies the PCI bus number and DEVNUM specifies the device number that is assigned to the board when it is configured by the PCI BIOS.
The values for these adapter parameters are displayed in hexadecimal notation when the driver loads (the Net.cfg file expects hexadecimal values). A PCI device scan utility can also be used to find this information. If the driver loads on a single controller, the displayed values can be used in the Net.cfg file.
If a PCI scan utility displays card 1 at bus 4 and device 11 (hexadecimal), and card 3 at bus 3 and device 13 (hexadecimal), the following load instructions are written to the Net.cfg file (load card 3 first, and optionally load card 1 second):
LINK DRIVER BX2BUSNUM 3DEVNUM 13 (13 hex = 19 decimal)LINK DRIVER BX2BUSNUM 4DEVNUM 11 (11 hex = 17 decimal)The FUNNUM keyword is used to determine which function/port the driver is to load on when using a multifunction (multiport) controller. Function number values are limited to 0 and 1, for the first and second function of the controller.
The SUBVID keyword is used to for load the driver only on the first network interface card found that has a subvendor ID (SVID) that matches the one set in Net.cfg. The driver ignores all other network interface cards that do not have a matching SVID. SUBVID expects a hexadecimal number.
Example:
LINK DRIVER BX2
SUBVID 14E4SUBVID cannot be used with BUSNUM, DEVNUM or FUNNUM.
The MODEL keyword is for loading the driver only on the first network interface card found that has a subvendor ID (SVID) that matches the one set in MODEL. The driver ignores all other NICs that do not have a matching SVID. MODEL expects a decimal number.
Example:
LINK DRIVER B44MODEL 5348