Posted on March 12, 2015 2:24 pm
 |  Asked by Brandon Ewing
Print Friendly, PDF & Email


Reviewing the Internet Draft for VXLAN, it is recommended that each VNI be mapped to a different multicast address for BUM distribution.  However, in the EOS documentation, it appears that you can only assign a single multicast address to the vxlan1 interface.  How can you specify per-VNI mappings for interop with other, non-Arista implementations, like VMWare’s dvSwitch, which allows mapping VNIs to separate multicast group addresses?  Are we forced to map all VNI’s to a single multicast address, everywhere, to support standards-based VXLAN?

Can the unicast flood list interop with any other vendor’s VXLAN architectures?

Posted by Alex
Answered on March 16, 2015 9:47 pm

Hi, in the current implementation to reduce the amount of multicast state in the underlay network, VNI’s are map to a single multicast group. Thus to interoperate with VMware’s dvSwitch you would need to map the VNI’s created on the dvSwitch to a single multicast group.

Due to the scaling issues presented by a multicast control plane and the requirements it places on the underlay network, the unicast flood list model is used in the majority of cases for interoperating with our partners such as VMware’s NSX solution.


Post your Answer

You must be logged in to post an answer.