Dell Broadcom NetXtreme Family of Adapters Broadcom NetXtreme 57XX User Guide - Page 170

NESL Compliance, Loading Broadcom Advanced Server Program

Get Dell Broadcom NetXtreme Family of Adapters PDF manuals and user guides View all Dell Broadcom NetXtreme Family of Adapters manuals
Add to My Manuals
Save this manual to your list of manuals

Page 170 highlights

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. NESL Compliance For optimum fault tolerance and recovery operations, the BASP.LAN driver relies on the adapter 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 the BASP.LAN driver, the ODINEB.NLM driver must be loaded before the NESL-compliant ODI drivers are loaded. Do the following to check if an adapter driver supports NESL events: Load the BASP.LAN driver and create a team by binding the adapter to the virtual slot (see the following instructions and examples). In the Virtual Adapter X Team Members console, the link status of all bound adapters is shown. Disconnect or connect the adapter cable. If the adapter driver supports NESL events, the link status should change immediately. Loading Broadcom Advanced Server Program 1. Load the BASP.LAN driver just as you would a standard LAN driver with all necessary frame types for the team. The BASP.LAN driver 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 2. Load the network drivers for the adapters that are to be on the team. The frame types loaded should be the same for all adapters on the team and the same as those loaded for BASP.LAN in step 1. Do not bind protocols directly to these adapters. Be sure to load ODINEB.NLM (supplied by Novell) before all network drivers are loaded. Example: LOAD ODINEB.NLM LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 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.

  • 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
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.
NESL Compliance
For optimum fault tolerance and recovery operations, the BASP.LAN driver relies on the adapter 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 the BASP.LAN driver, the ODINEB.NLM
driver must be loaded before the NESL-compliant ODI drivers are loaded.
Do the following to check if an adapter driver supports NESL events: Load the BASP.LAN driver and create a team by binding
the adapter to the virtual slot (see the following instructions and examples). In the Virtual Adapter
X
Team Members console,
the link status of all bound adapters is shown. Disconnect or connect the adapter cable. If the adapter driver supports NESL
events, the link status should change immediately.
Loading Broadcom Advanced Server Program
1. Load the BASP.LAN driver just as you would a standard LAN driver with all necessary frame types for the team. The
BASP.LAN driver 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
2. Load the network drivers for the adapters that are to be on the team. The frame types loaded should be the same for
all adapters on the team and the same as those loaded for BASP.LAN in step 1. Do not bind protocols directly to these
adapters. Be sure to load ODINEB.NLM (supplied by Novell) before all network drivers are loaded.
Example:
LOAD ODINEB.NLM
LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2
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.