HP Proliant NIC Teaming - the Easy Way
Novell Cool Solutions: Trench
By Garry Goodwin
Digg This -
Posted: 8 Sep 2004
NIC Teaming in NetWare is not easy. The default documentation leads you to using complex post bind options or running your NIC drivers from an NCF or even directly from Autoexec.NCF. (See the default documentation from HP, and from Novell)
SOLUTION: Follow these instructions for a much better way. This uses INTCFG only. The trick is in the order you load the boards and protocol bindings.
This example uses the QASP HP Teaming Driver to team two gigabit (Q57) NICs running at 1000Mbit/sec in Load Balancing Mode.
The Q57 references can be swapped for N1000 for Intel-based NICs as required for other models.
I am using this procedure on NetWare 6.5 but the process applies to NetWare 5.1 and above.
- LOAD INETCFG.
- Note the physical slot numbers of your physical boards, your IP address, subnet mask and default route.
- Remove all Boards / Bindings and User specific protocols.
- Select Boards and add the following boards in the exact order shown below.
Driver Board Name Slot No. Speed/Mode QASP QASP_1 Virtual Slot 1 Mode = SLB Q57 Q57_1 Slot = xxxx Speed = Auto Q57 Q57_2 Slot = xxxx Speed = Auto
NOTE: The Q57 driver does not have a 1000 / Full duplex setting so must be set to "Auto". Ensure the switch is configured for Speed 1000 Duplex = Full to avoid any errors.
- Select Protocols
- Select "User Specified Protocols"
- Insert protocol name "QASP1"
- Select Bindings and add the following bindings in the exact order shown below.
Protocol Network Interface Protocol Frame Type User Specified Q57_1 QASP1 Ethernet_II User Specified Q57_2 QASP1 Ethernet_II
Protocol Network Interface Address Subnet Mask TCP/IP QASP_1 x.x.x.x xxx.xxx.xxx.xxx
- Select TCP/IP, LAN Static Routing and enter a "Default" route to your gateway router.
- Exit INETCFG and Restart the Server.
- Confirm the QASP Teaming driver loads within its own screen and shows both NICs under the Virtual driver.
If you have any questions you may contact Garry at firstname.lastname@example.org
After a call to HP on this issue I came across this on the HP Proliant Teaming Web Site. The whitepapers are Excellent.
A Multi Link Trunk (MLT) will need to be configured on the switch. The ians/qasp/cians drivers manage the card bindings but require an MLT on the switch for each port in your "team". If you don't have an MLT-capable switch, you use NetWare's native load balance option that manages each card individually, with no special hardware requirements on the switch.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com