Jan Danielsson <jan.m.danielsson%gmail.com@localhost> wrote:
> Where, technically, do packet orders get mixed up?
The place you'd see it is with poorly implemented Equal Cost Multi-Path (ECMP)
As Greg said, good design tries never to do this by dividing traffic
deterministically based upon the layer-3 5-tuple.
A good example of where this might not happen is if there was a layer-2
ECMP solution that did not look at the layer-3 traffic at all. Many early
optical transports did this.
A host with two (or more) "bonded" ethernets that had a *lot* of traffic on
the same 5-tuple, might want to turn off the hash mechanism so that it can
fill both pipes. If the wires were plugged into two different switch chassis
(not at all uncommon), then there might well be very different paths through
the l2 fabric. One path can be more congested than the other.
So in general, it doesn't happen that often... anymore. But it sure can happen.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr%sandelman.ca@localhost http://www.sandelman.ca/ | ruby on rails [
Attachment:
signature.asc
Description: PGP signature