EtherChannel: This is a link aggregation (port trunking) method used to provide fault-tolerance and high-speed links between switches, routers, and servers by grouping two to eight physical Ethernet links to create a logical Ethernet link with additional failover links. For additional information on Cisco EtherChannel, see the EtherChannel Introduction by Cisco.
LACP or IEEE 802.3ad: The Link Aggregation Control Protocol (LACP) is included in IEEE specification as a method to control the bundling of several physical ports together to form a single logical channel. LACP allows a network device to negotiate an automatic bundling of links by sending LACP packets to the peer (directly connected device that also implements LACP).
EtherChannel vs. 802.ad: EtherChannel and IEEE 802.3ad standards are very similar and accomplish the same goal. There are a few differences between the two, other than EtherChannel is Cisco proprietary and 802.3ad is an open standard.
For additional information on EtherChannel implementation, see the Understanding EtherChannel Load Balancing and Redundancy on Catalyst Switches article from Cisco.
The following are EtherChannel supported scenarios:
One IP to many IP connections. (Host A making two connection sessions to Host B and C)
Many IP to many IP connections. (Host A and B multiple connection sessions to Host C, D and etc)
Note: One IP to one IP connections over multiple NIC is not supported. (Host A one connection session to Host B uses only one NIC).
Compatible with all ESX/ESXi VLAN configuration modes: VST, EST, and VGT. For more information on these modes, see VLAN Configuration on Virtual Switch, Physical Switch, and Virtual Machines (1003806).
Supported Cisco configuration: EtherChannel Mode ON – ( Enable Etherchannel only)
Supported HP configuration: Trunk Mode
Supported switch Aggregation algorithm: IP-SRC-DST short for (IP-Source-Destination)
Supported Virtual Switch NIC Teaming mode: IP HASH
Note: The only load balancing option for vSwitch or vDistributed Switch that can be used with EtherChannel is IP HASH.
Do not use beacon probing with IP HASH load balancing.
Do not configure standby or unused uplinks with IP HASH load balancing.
We only support one Etherchannel per vSwitch or vNetwork Distributed Switch (vDS).
页:
1
[2]