02-03-2013 12:52 AM - edited 03-07-2019 11:28 AM
Hi team,
I could not able to diffrenciate the significance between these below mentioned load balancing types in etherchannels even i have gone through few forums.
PLease clarify.
KAR-L3(config)#port-channel load-balance ?
dst-ip Dst IP Addr
dst-mac Dst Mac Addr
src-dst-ip Src XOR Dst IP Addr
src-dst-mac Src XOR Dst Mac Addr
src-ip Src IP Addr
src-mac Src Mac Addr
Thnaks ,
Naveen
02-03-2013 02:24 AM
You have to make sure that your switch sees *many* of the elements that you configure as the keyword. Lets asume the following topology:
many PCs in VLAN X - L3-Switch VLAN Y - Etherchannel - Switch - One Server in VLAN Y
If you configure the load balance on the L3-switch:
- src-mac: all traffic will flow over one channel-member as the channel only sees one source-mac.
- src-dst-mac same as before. The channel only sees one source and one destination mac address
- dst-mac or dst-ip: all traffic will flow over one channel-member as the channel only sees one destination (mac or ip)
- src-ip: if many PCs communicate to the server the traffic will be shared over many links as the channel sees many source-IPs.
- src-dest-ip: in this scenario would balance the same as src-ip
For the configuration of the right switch it has to be reversed:
- dst-ip or src-dst-ip can ballance the traffic over many links if more than one PC is part of the communication.
--
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni
02-03-2013 06:23 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Generally, you want to use the option that corresponds to which attribute or attributes are most likely to be be different across different flows egressing out the Etherchannel.
For example if you had a router gateway IP supporting many other subnet hosts, often from traffic going to/from off the subnet would have the gateway's MAC and a host MAC. So for traffic going from gateway to host, you might want to use dst-mac or src-dst-mac. For traffic going from host to gateway, you might want to use src-mac or src-dst-mac.
In addition to what attribute or attributes are likly to be different, you might want to account for traffic volume. Assume one host is really, really busy and has 90% of the traffic going off the local subnet. Instead of using for traffic from host to gateway src-mac or src-dst-mac, you might want to use dst-ip or src-dst-ip. The converse choice might be src-ip or src-dst-ip.
As you might have noticed, the combined attribute choices, e.g. src-dst-ip, allow the same choice in both directions because generally part of the selected attribute is changing regradless of traffic direction.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide