• Author : Vincent Lam



Description In conventional VXLAN deployments, each MLAG pair of switches are represented as a common virtual VTEP. VXLAN traffic can be decapsulated on either switch. In some networks, there are hosts that are singly connected to one of the MLAG pair. VXLAN packets destined for the singly connected host could land on the other MLAG peer and subsequently be forwarded over the MLAG peer-link to reach the destination host. This path is undesirable since it would use up some bandwidth on the peer-link. Figure 1 : Suboptimal Packet Path to Singly Connected Host The Multi-VTEP MLAG feature prevents unicast VXLAN...
Continue reading →

Hardware switch controller MLAG integration

The Hardware Switch Controller (HSC) provides an integration point between the SDN controllers (NSX or Nuage) and VXLAN Controller Service (VCS).  The SDN controller will interact with the HSC agent through OVSDB (Open vSwitch Database). The HSC agent, in turn, will translate information between OVSDB and VCS. The HSC agent publishes the inventory of physical switches and physical ports to the SDN controller. The SDN controller in turn would read this inventory and update the physical ports’ VLAN bindings in order to bind a VLAN to a logical switch. In a MLAG deployment where two physical switches publish MLAG ports....
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: