Yes, that the reason. Ethernet guarantees in order delivery of a particular flow. If you provided two different paths for a given flow, you would lose this property. Peter just gave an example of UDP, but considering we're talking about a property of ethernet, many ohter protocols would potentially be impacted.

Regards,

Francois

"TCP does not like that - while it can recover, it also reacts with closing the window and slowing down the transfer."

Just to clarify Peter's comment, TCP doesn't always have a serious issue with packet resequencing. Actual impact depends on TCP variant and how "badly" received packets are resequenced. Worst case, sender slows transfer rate (as noted by Peter) and successfully already received packets are transmitted again. Best case, although generally not serious, sender and receiver buffers are held longer than truly necessary (necessary because of resequenced packets) and extra ACKs transmitted. I.e., although IP doesn't guarantee packet sequencing, resequencing packets is something to needlessly avoid.

If multiple links are to be combined between devices, when possible, some other technologies (e.g. MLPPP, IMA, etc.) can guarantee packet sequencing is maintained.

Francois, Joseph,

Thanks very much to both of you for extending my answer!

Best regards,

Peter

Hi Peter, Francois and Joseph,

Thank u very much for ur valuable responses.

Regards

Prado

Hi Friends,

Could you please explain how exactly the etherchannel load balancing work with src-ip|dst-ip|src-mac|dst-mac|src-prt|dst-prt.

Thank u

Prado

Hello Prado,

I suggest reading this document first:

http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml

It also says that the algorithm to achieve load balancing is proprietary. However, just for illustration, you can imagine that if you are using just a single value for the load balancing (source or destination MAC, IP or port), then the output port can be calculated as VALUE MOD N where N is the count of interfaces in the Etherchannel and VALUE is the respective value from the frame being transmitted. If you use multiple values, for example, source and destination MAC, then the output port for a particular frame can be calculated as (SRCMAC XOR DSTMAC) MOD N where N is again the count of interfaces in the Etherchannel.

Note again that this is just an illustration how it could be implemented, however, Cisco might use any other algorithm to map the values to output ports.

Best regards,

Peter

Hi Peter,

Thanks a lot for ur information, the working of etherchannel load balancing methods are realy easy to understand, provided one must be comfortable in hexadecimal to decimal conversion. Any ways i got to know the working of load balancing methods.

Best Regards

Prado

Hi folks...a question if this thread is active...connecting 2 classrooms with 2 wireless links. Using routers we are sending data from class A down link A to class B and class B is using the other link to send to class A. Could Etherchannel be a better solution? thx

If the links are routed, CEF equal cost load balancing might be better.

[edit]

BTW, for best results, you might post your question as its own.