The Docuarchive server is configured with multiple NICs to maximize potential network throughput. There are 3 NICs installed, two built-in and one PCI add-in. The two built-in NICs are configured as a Team (Team 1) and work in tandem as a single NIC with a single IP (10.0.0.107 as of this writing.) The third NIC (coincidentally the same brand and chipset) is setup with the server's primary IP, 10.0.0.7. This third NIC could be added to Team 1 if desired but is not likely necessary. The plan is to swap IP addesses, giving the primary IP better bandwith and potentially improving backup performance.
In our case the software for teaming NICs was bundled with the drivers for the NICs. The software is called “Broadcom Advanced Control Suite” (Start menu » All Programs » Broadcom » BACSS3). The team was configured using the built in wizard and is very straight forward. The only special choice needed was to pick the “Team Type”. For creating a simple paired team (to improve throughput) the choice is “FEC/GEC Generic Trunking”. This information was found with some online searching which also indicated that to best take advantage of teamed NICs LACP should be enabled on the switch, this makes the switch aware that two ports are being used together as a trunk. This is covered below.
First off, make sure your switch supports LACP. Not all of them do. If yours doesn't, or at least doesn't out of the box, check to see if there are any firmware updates on HP's site that enable LACP support, which you can find at http://www.hp.com/rnd/software/switches.htm. You also want to make sure that the device you're connecting to the switch supports LACP too, but hopefully you've already done that since you're looking how to set it up.
Ok, to enable LACP (link aggregation control protocol) is pretty easy. You have to have admin access to your switch, and also access to the CLI (command line interface) which you can get through with a simple telnet session to your switch's IP address. There is dynamic LACP, which is more of an automated configuration, but it limits your LACP link to running in the default VLAN only. I believe you can just plug the Ethernet cables into your switch and it will automatically recognize LACP is setup, as long as it is already configured on the device you are connecting. If you have multiple VLANs and need LACP to run in a VLAN other than the default, the only option is to manually set up static LACP, which is what this post is going to cover.
If you want to remove a port from your trunk at some point, you can use “no trunk 1” which would remove port 1 from the trunk. You can use port ranges too, so “no trunk 1-4” would completely remove the trunk that was setup in the example.
After doing the above
show lacp returned this on our HP2824 core switch:
PORT LACP TRUNK PORT LACP LACP NUMB ENABLED GROUP STATUS PARTNER STATUS ---- ------- ------- ------- ------- ------- 1 Passive 1 Down No Success 2 Passive 2 Down No Success 3 Passive 3 Up No Success 4 Passive 4 Up No Success 5 Passive 5 Up No Success 6 Passive 6 Up No Success 7 Passive 7 Up No Success 8 Passive 8 Up No Success 9 Active Trk1 Up No Success 10 Active Trk1 Up No Success 11 Passive 11 Down No Success 12 Passive 12 Down No Success 13 Passive 13 Up No Success 14 Passive 14 Up No Success 15 Passive 15 Down No Success 16 Passive 16 Up No Success 17 Passive 17 Up No Success 18 Passive 18 Up No Success 19 Passive 19 Up No Success 20 Passive 20 Up No Success 21 Passive 21 Up No Success 22 Passive 22 Up No Success 23 Passive 23 Up No Success 24 Passive 24 Up No Success