> right, both trio and asr9k can do lag/ecmp balancing based on payload > inspection to some degree, but it's complicated and hacky.
getting offtopic, but wondering what you mean with complicated and hacky about the load balancing algo on Trio? Trio hash includes; - upto 5 labels - ipv4/v6 payload contents (and yes, it checks the packet' length to avoid the "4" or "6" DMAC issue) - for ethernet pw it can skip upto 2 vlans and still include its ipv4/v6 payload (if any) For our traffic mix (ymmv), this results in near-perfect load balancing for PWs, without FAT. My take on it is that FAT is a hack to cope with ASIC designs that can't do proper deep inspection. (granted, other JNPR platforms can't do the fancy Trio tricks). Daniel. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
