Etherchannel load-balance
This is an interesting question!
I do not think that Joseph’s solution answers the question. This is because:
For this particular example, as VLAN A is behind R1, SW2 only sees a single MAC of R1–Fa0/1, and not all MAC of PC in VLAN A. Therefore, it can not (effectively) do load-balancing based on destination MAC, nor can it do load-balancing based on source IP (traffic from server in VLAN C only have one single source IP). Note that switches can only influence (load-balance) traffic going out, and not traffic coming back.
Similarly, SW1 can not do load-balance based on source MAC, although it can do load-blance based on source IP.
So my solution is:
SW1: load-balance based on source IP (or source-destination IP) SW2: load-balance based on destination IP (or source-destination IP)
BTW, Joseph, how do you configure SW1 with both source Mac and Source IP (assuming you only have IP traffic)?
Regards,
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Joseph Saad Sent: Monday, 7 July 2008 2:24 AM To: Cisco certification Subject: Re: Etherchannel load-balance
in this particular scenario I’d configure
SW1 with source Mac (or Source IP or both) SW2 with destination Mac (or Source IP or both)
The simple rule is: You configure the switch “sending out the traffic to the etherchannel” in a way to suit the destination SW connected hosts.
HTH, Joseph.
On Fri, Jul 4, 2008 at 7:49 PM, Cisco Addicted wrote:
> Dears, > > I want to know what is to consider when deciding the ether channel > load balancing if I may have the following scenario: > > > > > > VLANA-(Fa0/0–R1–Fa0/1)—— SW1 (3560)=== ===SW2 (3560) > ——(fa0/1-R2—-fa0/0) —– VLAN C > > > > And considering there is a many users in VLAN-A accessing server on > VLAN-C, and there is etherchannel trunk configured between SW1 & SW2. > > > > Thanks in advance. > > > ______________________________________________________________________ > _ Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
























