SHARIFUL's TECH BLOG

In part - 09  we have prepared our anycast border-gateways for underlay and overlay bgp configuration. But we have not done any l3vni/l2vni extension. In this blog we will configure ip-vrf (l3vni) extension in our border-gateways. Along the way we will troubleshoot something called rouge-vtep which is Cisco's proprietary always-on native data plane security. And solve that rouge-vtep problem with another proprietary solution called advertise-pip . What is multi-site ? When we connect two different dc-fabrics (different BGP ASN) together with eBGP l2vpn-evpn - we call it vxlan multi-site extension. What is l3vni extension ? If vlan - A, under vrf - X, from Site - 1 can communicate over the border-gateways with  vlan - B, under vrf - X  from Site - 2;  we call it l3vni/ip-vrf extension over multisite. The common thing in the extension is that communicating vlans belong to the same vrf (l3vni).  Our topology looks like below -  01 - Network Topology For Spin...

In this blog we will build another data center using vxlan which we will call Dc-02. This data center will use settings/configuration exactly same as our previous blog - part -07 . We need another Dc, because soon we will integrate/connect both data-centers using vxlan's multisite connectivity for seamless l3vni/l2vni handoff. Our topology looks like below for Dc-02 -  01 - Network Topology We have 2 spine switches as ibgp route-reflectors for l2vpn-evpn address family and 2 leaf switches. Bum traffic will use BGP's ingress replication (HER). Our addressing look like below -  BGP ASN - 4200000002 Loopback 0 - 10.82.0.X/32 where X is the switch number. Loopback 1 - 10.82.1.X/32 where X is the switch number. L3VNI - Vrf_Blue ( vlan 100 with l3vni 100000 ). L2VNI - vlan 101 with l2vni 100001, 10.91.101.0/24 in Vrf_Blue. L2VNI - vlan 103 with l2vni 100003, 10.91.103.0/24 in Vrf_Blue. Spine Switch Configuration Dc-02-Spine-01 Configuration hostname Dc-02-Spine-01 nv overlay evp...