VXLAN Part 2 | Deploying VXLAN on the Network

[@mutegekisolomon5796]

Very good content

[@12ragul12]

Thanks for this detail exp and looking for VXLAN multi-tenant setup

[@ChadEmery]

Excellent video and explanations!

[@TechFreak51]

Awesome !!!!

[@nicolasblazquez5485]

Hey, thx you for the video, its amazing, can we address our interfaces in a /31 rather than in a /30 as there is no need for broadcast or network addresses ?

[@RichTechGuy]

If the networking devices support RFC 3021, then yes, you can use a /31 subnet. All current Cisco switches do support RFC 3021.

[@rbattle2u]

For the Leaf and Spine BGP L2VPN EVPN configs, is there a reason the BGP neighbor definitions don't reference the remote-as or update-source statements?

[@RichTechGuy]

The remote-as and update-source statements are already in the config for each neighbor statement. Those statements the config for that neighbor and are not specific to ipv4 unicast or l2vpn evpn. If you did a 'show run' on the switch you would see something like this in the BGP config: router bgp 65001 neighbor 10.2.0.1 remote-as 65001 update-source loopback0 address-family ipv4 unicast send-community send-community extended route-reflector-client

[@marshallshelton6262]

Any way you could post your full configs on your website?

[@waisudinfarzam4056]

Quick Question, can we a normal switch and trunk it to the same Leaf and add the vlans and assign vlans based on the normal switch not to attach the end device to the leaf switches ?

[@RichTechGuy]

Yes you can add a switch downstream from the leaf switch and connect the end devices. Any VLANs on the downstream switch that are trunked to the VXLAN leaf and have an associated VNID, will have connectivity across the VXLAN network. Any VLANs on the downstream switch that are not trunked to the VXLAN leaf, or are trunked, but do not have an associated VXLAN VNID will be localized to just that switch and not have access to the VXLAN network.