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

Additional Command Line Keywords

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 174 highlights

LOAD ODINEB.NLM LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_1_EII SLOT=1 FORVLANS LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_2_EII SLOT=2 FORVLANS 3. Bind BASP.LAN to the NIC adapters in the team for each protocol. Example: BASP BIND BASP_1_V2_EII B57_1_EII BASP BIND BASP_1_V2_EII B57_2_EII If there are multiple VLANs (each with one or more frame types) loaded on the virtual adapter, it is only necessary to bind one frame type on one VLAN on the virtual adapter to the same frame type on the physical adapter. The other VLANs are automatically bound. 4. Bind protocols to BASP.LAN. Example: BIND IP BASP_1_V2_EII ADDR=x.x.x.x MASK=x.x.x.x This example creates a team with two adapters using VLAN ID 2. Outbound packets are tagged with VLAN ID 2, and only similarly-tagged packets can be received by the adapters on the team. Additional VLANs with different VLAN IDs can be created on the same team. The maximum number of VLANs per virtual slot is 64. The valid range of values for VLAN IDs is from 1 to 4094. VLAN=0 indicates the VLAN is untagged and is the default. Use decimal numbers to specify the VLAN ID. The following are examples of multiple VLAN configurations: LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=100 LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V200_EII VSLOT=1 VLAN=200 LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V300_EII VSLOT=1 VLAN=300 LOAD ODINEB.NLM LOAD B57 FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 LOAD B57 FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 BASP BIND BASP_1_V100_EII B57_1_EII BASP BIND BASP_1_V100_EII B57_2_EII BIND IP BASP_1_V100_EII ADDR=172.16.210.1 MASK=255.255.0.0 BIND IP BASP_1_V200_EII ADDR=172.17.210.1 MASK=255.255.0.0 BIND IP BASP_1_V300_EII ADDR=172.18.210.1 MASK=255.255.0.0 NOTES: When BASP BIND BASP_1_V100_EII B57_1_EII is executed, the adapter B57_1_EII is bound to all three VLANs. If you are unable to log on to the system after configuring BASP, add the following command lines before loading BASP: UNLOAD SLPTCP LOAD SLPTCP Jumbo Frames Jumbo Frames are supported in all load balancing types of teams. The maximum frame size is automatically set to the smallest maximum frame size of all adapters in the team. Use appropriate keywords to enable Jumbo Frames when loading the adapter drivers. Example: startup.ncf SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=18000 autoexec.ncf LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 JUMBO=9000 LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 JUMBO=9000 BASP BIND BASP_1_EII B57_1_EII BASP BIND BASP_1_EII B57_2_EII Additional Command Line Keywords CHECKSUM = ON Enables BASP.LAN to offload TCP/UDP and IP checksums to the bound adapters (if supported by the operating system). This setting improves performance if some or all adapters in the team support hardware checksums. Be sure to load the adapter drivers with hardware checksums enabled. Example:

  • 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
LOAD ODINEB.NLM
LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_1_EII SLOT=1 FORVLANS
LOAD ALT.LAN FRAME=ETHERNET_II NAME=ALT_2_EII SLOT=2 FORVLANS
3. Bind BASP.LAN to the NIC adapters in the team for each protocol.
Example:
BASP BIND BASP_1_V2_EII B57_1_EII
BASP BIND BASP_1_V2_EII B57_2_EII
If there are multiple VLANs (each with one or more frame types) loaded on the virtual adapter, it is only necessary
to bind one frame type on one VLAN on the virtual adapter to the same frame type on the physical adapter. The
other VLANs are automatically bound.
4. Bind protocols to BASP.LAN.
Example:
BIND IP BASP_1_V2_EII ADDR=x.x.x.x MASK=x.x.x.x
This example creates a team with two adapters using VLAN ID 2. Outbound packets are tagged with VLAN ID 2, and
only similarly-tagged packets can be received by the adapters on the team. Additional VLANs with different VLAN
IDs can be created on the same team. The maximum number of VLANs per virtual slot is 64. The valid range of
values for VLAN IDs is from 1 to 4094. VLAN=0 indicates the VLAN is untagged and is the default. Use decimal
numbers to specify the VLAN ID.
The following are examples of multiple VLAN configurations:
LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V100_EII VSLOT=1 VLAN=100
LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V200_EII VSLOT=1 VLAN=200
LOAD BASP FRAME=ETHERNET_II NAME=BASP_1_V300_EII VSLOT=1 VLAN=300
LOAD ODINEB.NLM
LOAD B57 FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1
LOAD B57 FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2
BASP BIND BASP_1_V100_EII B57_1_EII
BASP BIND BASP_1_V100_EII B57_2_EII
BIND IP BASP_1_V100_EII ADDR=172.16.210.1 MASK=255.255.0.0
BIND IP BASP_1_V200_EII ADDR=172.17.210.1 MASK=255.255.0.0
BIND IP BASP_1_V300_EII ADDR=172.18.210.1 MASK=255.255.0.0
NOTES:
When BASP BIND BASP_1_V100_EII B57_1_EII is executed, the adapter B57_1_EII is bound to all three VLANs.
If you are unable to log on to the system after configuring BASP, add the following command lines before
loading BASP:
UNLOAD SLPTCP
LOAD SLPTCP
Jumbo Frames
Jumbo Frames are supported in all load balancing types of teams. The maximum frame size is automatically set to the
smallest maximum frame size of all adapters in the team. Use appropriate keywords to enable Jumbo Frames when loading
the adapter drivers.
Example:
startup.ncf
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=18000
autoexec.ncf
LOAD BASP.LAN FRAME=ETHERNET_II NAME=BASP_1_EII VSLOT=1
LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_1_EII SLOT=1 JUMBO=9000
LOAD B57.LAN FRAME=ETHERNET_II NAME=B57_2_EII SLOT=2 JUMBO=9000
BASP BIND BASP_1_EII B57_1_EII
BASP BIND BASP_1_EII B57_2_EII
Additional Command Line Keywords
CHECKSUM = ON
Enables BASP.LAN to offload TCP/UDP and IP checksums to the bound adapters (if supported by the operating system). This
setting improves performance if some or all adapters in the team support hardware checksums. Be sure to load the adapter
drivers with hardware checksums enabled.
Example: