Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme II Network Adapt - Page 26

Configuring the Driver Software, ENTER, Receive Buffers, BusNum, DevNum, FuncNum, LineSpeed, Duplex

Page 26 highlights

ODI Driver Software: Broadcom NetXtreme II Network Adapter User Guide 14. Press ENTER. 15. 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. 16. Press F10 to save and continue. The Bx2.LAN and Bx2.LDI files are copied to the directory. 17. Restart the system to complete the install. 18. 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. 19. 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 (see Viewing Resource Information) 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 BIND BX2 BIND BX2 LINK DRIVER BX2 BUSNUM 1 DEVNUM 9 FRAME LINK DRIVER BX2 BUSNUM 1 DEVNUM A FRAME 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: file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/dosodi.htm[9/26/2012 3:28:43 PM]

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

ODI Driver Software: Broadcom NetXtreme II Network Adapter User Guide
file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/dosodi.htm[9/26/2012 3:28:43 PM]
14. Press
ENTER
.
15. 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.
16. Press
F10
to save and continue. The Bx2.LAN and Bx2.LDI files are copied to the directory.
17. Restart the system to complete the install.
18. 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.
19. 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 (see
Viewing Resource Information
) 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 BX2
BIND BX2
LINK DRIVER BX2
BUSNUM 1
DEVNUM 9
FRAME <frame #1 name>
LINK DRIVER BX2
BUSNUM 1
DEVNUM A
FRAME <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: