Thank you for attending as well as the nice feedback, much appreciated. There are not any requirements and/or dependencies on the compute / hypervisor / service-node(s) attaching to the VXLAN EVPN fabric. We can leverage the existing port-groups in vCenter that are VLAN-based today and map those VLAN at the ToR to the appropriate VXLAN VNI.
- VLAN to VNI configuration on a per-switch basis
- VLAN is the “Switch/Leaf Local Identifier”
- VNI is the “Network Global Identifier”
- Results in the 4k VLAN limitation has been removed network-wide.
Does this help?
Please let me know.
Yes, to the 4k VLAN limit per-switch as 802.1q has 12-bits and yields 4k VLANs; the VXLAN VNI is 24-bits and yields 16M segments.
There is work going on for a CVD, Lukas has done a great job with VXLAN Configuration Best Practices; can be found here:
Also, keep in mind the VXLAN EVPN Live Lessons has a tremendous amount of details as well, that can be found here:
Please let me know if you have any questions, happy to help.
Have a great weekend.
Folks! How are you doing?
Thank you for the valuable information!
I had some problems and lost the first part of the seminar.
I am very new to these issues of Multi-tennant, VXLAN, OTV, ACI, DC in general.
I am learning and trying to join the peaces, so many information.
I am waiting to see the material again and will post some questions, ok?
Videos are now live and linked to from this page: Cisco Press Authors Webinars
Here is the link to Lesson 1: Fundamentals of Multi-Tenancy in VXLAN: Lesson 1: Introduction
The slides are attached to the original post of this thread.