Posted by: Anonymous
on May 08, 2008 11:30 AM
Couple of errors in this
' From your network's perspective, the simplest option is channel bonding or "port trunking"' - Channel Bonding is just what it says and stems from the old days of ISDN and dial up channels for the Cicso people it is called "EtherChannel". "Port Trunking" in Cisco land is a technology that means switches can tag and forward multiple VLANS across a single link, it also allows the switches to pass VTP traffic and other nice stuff.
Also I think it's been made to look easier than it really is as there are different channel bonding methods, each have pluses and minuses, and certain pieces of equipment can't handle some, which means if you do choose this you may not be able to use other things on your network.
802.3ad Dynamic - provides receive and transmit load balancing on a single switch. In this team type, the nic members negotiate with the switch to automatically form a port group, so no additional configuration is required on the switch. The switch must support the IEEE 802.3ad Link Aggregation Control Protocol (LACP).
Switch-assisted Load Balancing (SLB) - provides receive and transmit load balancing on a single switch and is functionally identical to 802.3ad Dynamic Teaming. SLB requires the switch itself to be configured to form a port group. The switch must support port aggregation, but it does not need to support the IEEE 802.3ad Link Aggregation Control Protocol.
Transmit Load Balancing (TLB) - balances the transmit traffic among the nic members, but does not require any special switch intelligence or switch configuration. In addition, TLB teams can be split across switches as long as all members are in the same layer 2 network. In TLB teams, receive traffic is not load balanced, but is received on a single nic member.
Network fault tolerance (NFT) - prevents network downtime by transferring the workload from a failed port to a working port. Clients on the network see no disruption of service, and the network can remain in use while the failed component is repaired. NFT teaming functions at any speed, on any media. It is switch-independent and can be split across Layer 2 switches but must be in the same Layer 2 domain.
Gotta be honest, I'm not a Linux boy so I've no idea whether it goes this in depth. Thought this may help anybody thinking about it thou.