![]() The intense interest reflects the demand for ever-lower latency, plus it distributes the workload, providing better total performance. This reflects the current trend, pushing L2 and 元 forwarding to be on the Top of Rack (ToR) or Leaf switch, then further down to the hypervisor or chassis where possible. Although later we will slightly qualify the “no surprises” statement for DFA and ACI. Two physical servers on the same Leaf (edge) switch are locally switched. ![]() Two VM’s on the same hypervisor host attached to the same VLAN / portgroup / VXLAN are locally switched by the hypervisor code. Local forwarding (same Leaf switch or same hypervisor host) is done locally. Little do they know what’s really going on under the hood! Bare metal servers and VMs are unaware of any changes, they think they’re doing normal L2 forwarding via a switch. There’s a key element to all these SDN technologies, really a requirement. Creative Commons license) (Gratuitious blog graphic based on the slight relevancy of bridges.) Common Elements (NSX, DFA, ACI) I’ve got an ambitious list but am not posting it, since it may not all happen. Practical SDN: NSX, DFA, and ACI, The All-Seeing Eye. See this first blog for a general disclaimer.We’ll look at L2 forwarding (bridging) and some scenarios where the behavior might not be what you expect. The series attempts to contrast the various behaviors of NSX, DFA, and ACI. ![]() How does L2 forwarding work in NSX, DFA, and ACI? That’s the topic for this blog, blog #2 in a series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |