could you please explain what is the function of {dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac} and how load is converting in each link based on load balancing ?
You should pick a load balancing method based on your traffic patterns. For example, if you have 200 hosts on one side and one server on the other side then you might want to pick āsrc-macā ( on the side with the hosts and ādst-macā on the server side. Otherwise you might end up sending traffic down only one of the physical interfaces.
When you use āonā then you donāt use any negotiation protocol at all (Lacp or Pagp), itās just a static Etherchannel.
If you configure this on both sides then your Etherchannel will work. I donāt really recommend doing this, when you use Lacp or Pagp, the Etherchannel will be torn down when you have a misconfiguration and physical interfaces will be removed when something is wrong.
When you build a static Etherchannel and have a misconfiguration between the two switches, you could get loops.
Let me give you an example. Letās say we have three switches, SW1, SW2 and SW3. These switches are connected in a triangle.
Without any Etherchannels, spanning-tree will work and blocks some interfaces to create a loop-free topologyā¦life is good.
Now we try to configure an Etherchannel between SW1 and SW2, we use a protocol like PaGP for negotiation. For some reason, thereās a misconfiguration on one of the physical interfaces. Since we use PaGP, itās able to detect this and this physical interface will be removed from the etherchannel or the etherchannel wonāt come upā¦life is good.
Now we want to configure a static Etherchannel between SW2 and SW3. First we configure the static etherchannel on SW2, but for some reasonā¦someone configures the wrong interfaces on SW3. Hereās what might happen:
SW2 has an Etherchannel and will only send one BPDU to SW3.
SW3 doesn't have an Etherchannel and will send two BPDUs (one of each physical interface).
SW3 expects to receive two BPDUs, one on each interface. It's only receiving one though.
Since SW3 doesn't receive a BPDU, it might put the interface in forwarding mode.
We now have a loop.
Ā
Spanning-tree can do its job but only when your interfaces are configured correctly. When using static Etherchannels, thereās nothing protecting you from misconfiguration.
how does ether-channel which has its primary purpose for link aggregation work if you later on configure load balancing which only uses one physical link as per your illustration above? or is that only when multiple computes are using the trunk at same time?
Ā
meaning if i am the only host using the trunk, i can take advantage of the link aggregation, otherwise its setup for load balancing?
The primary purpose for Etherchannel is to increase bandwidth and if you use L2 Etherchannel, making sure that STP doesnāt block all your interfaces. In certain scenarios you need to make sure you use the correct load balancing method otherwise youāll end up with one physical interface doing all the work.
An Etherchannel to a single host could be useful if you have multiple destinations as you can do load balancing based on destination MAC or IP address.
Unfortunately Etherchannels donāt support āround robinā load balancing so an Etherchannel between two hosts is no good, the source + destination MAC and IP addresses are always the same.
From what I understand all the traffic coming from MAC address AAA BBB CCC DDD will go out SW1. Do we configure the port-channel load-balance dst-mac on SW2 cause each of those devices connected to SW1 have different destination mac?
Having a hard time understanding this?
SW2(config)#<strong>port-channel load-balance dst-mac</strong>
If this is the case itās better to change the load balancing mechanism. If we switch it to destination MAC address on SW2 traffic from our router to the computer will be load-balanced amongst the different physical interfaces because we have multiple computers with different destination MAC addresses.
Behind SW1 we have four hosts with four different MAC addresses, they are all going to destination EEE (router).
In that case, using source address load balancing will work fine on SW1 since it will spread out over the available physical links that we have.
For the return traffic, the source address will always be EEE and the destination can be AAA, BBB, CCC or DDD. If you leave the load balancing on SW2 at the default setting then it will use the same physical link for all traffic. Itās better to change it to destination-based load balancing.
Hi Reneā¦I donāt quite get how if we have the option of on or of in both lacp and pagp how the switches know which we meanā¦probably me being stupid. Tx
From SW1ās perspective this is a great choice as each computer has a different MAC address. Traffic from the computers will be load balanced when it is sent from SW1 to SW2.
From SW2 to SW1, itās another story. The MAC address of the router remains the same so using src mac based load balancing is not a good idea. All traffic will be sent using the same physical interface. Itās better to change it to dst mac address load balancing since the destination MAC address will be one of the four computers.
The same principle applies to L3 yes.
When your etherchannel is overloaded, you will see drops yes.
Re.:When your etherchannel is overloaded, you will see drops yes.
What Iām getting at is that the bandwidth you create with an etherchannel is not really the bandwidth you get in practices based on your load-balancing setting and type of traffic.
Best regards,
Hans de Roode
shantel
(Shantel - Networklessons.com)
Split this topic
39
Thatās right. This sometimes surprises peopleā¦
For example, letās say you have a fileserver and 100 clients. The fileserver is connected to the switch with 8x Gbit Etherchannel, the clients are using regular Gigabit interfaces. This will work well since there are many different client MAC/IP addresses, we can use this for load balancing and you might be able to get close to 8 Gbit of bandwidth for your fileserver.
We also have a backup server connected to the switch with 8x Gbit Etherchannel. During the night we copy everything from the fileserver to the backup server. What happens is that you will only get ~ 1 Gbit of bandwidth since the source/destination MAC+IP are always the sameā¦Cisco doesnāt support round robin frame-by-frame load balancing for Etherchannel.
You will be better off upgrading the Gigabit Etherchannels to 10 Gigabit links on the fileserver and backup server in this case.
Long story short, building Etherchannels doesnāt really mean that 1+1 = 2 It depends on the trafficā¦