4 ms·
They're probably learning that MLAG should be avoided unless absolutely necessary. But providing common L2 domains across cabinets is probably something they "n
by insaneirish 12y ago
They're probably learning that MLAG should be avoided unless absolutely necessary. But providing common L2 domains across cabinets is probably something they "need."
There's much less to go wrong with ECMP at L3. Stateful networking components frighten me.
- donavanm 12y agoNot knowing anything about their infrastructure Id guess that they're using vlan tags for customer isolation. They'd want customer instances spread among racks, based on instance type etc. Going to in house/vxlan/nvgre encap certainly looks better suited, but still has a high bar to entry.
- contingencies 12y agoYou guys sound like you know a lot about these types of networking protocols. Can you recommend a decent summary of currently available approaches to relatively dynamic private link layer network topology provision suitable for cross-cabinet (or even cross-site) virtualized infrastructures and their drawbacks? For instance, I've been seeing Open vSwitch gaining popularity.