Data Center

Using  vJunos-Router, 23.4 , I cannot get DCI Stitching working , seem like the packets will not go from VTEP <> VTEP, I've setup  a bridged overlay between DCs 
The control plane looks good, and proxy arp is working. A device in one DC can ARP and get IP and MAC for the other DC; however, packets just seem to get blackholed at the GW device  as verified with Wireshark. 

Also been referring to Day One: Seamless EVPN-VXLAN Tunnel Stitching for DC and DCI Network Overlay

[edit routing-instances]
root@dc2-gw1# show                           
macvrf-v100-1 {
    instance-type mac-vrf;
    protocols {
        evpn {
            encapsulation vxlan;
            default-gateway no-gateway-community;
            extended-vni-list 10100;
            interconnect {
                vrf-target target:1:2;
                route-distinguisher 192.0.2.24:12;
                esi {
                    00:00:00:00:00:00:00:22:22:22;
                    all-active;
                }
                interconnected-vni-list 10100;
                encapsulation vxlan;
            }
        }
    }
    vtep-source-interface lo0.0;
    bridge-domains {
        bd100 {
            vlan-id 100;
            vxlan {                     
                vni 10100;
            }
        }
    }
    service-type vlan-aware;
    interface ge-0/0/5.0;
    route-distinguisher 192.0.2.24:100;
    vrf-target target:2:2;
}

[edit routing-instances]

Hi Simon Bingham

Your config looks correct, but there is one unnecessary line.

Try to do this.

--

delete routing-instances macvrf-v100-1 protocols evpn interconnect encapsulation vxlan

--

DCI sometimes doesn't work, but rebooting GW sometimes fixes it, so it's worth trying.

------------------------------
RYOTA KOSAKA
------------------------------

Hi Simon,

Just wondering if you managed to solve this? I am seeing the exact same behaviour, with both vjunos-router images and MX204 hardware. The VTEPs between the MXs are showing 0 packets sent/received - they seem to be the sticking point. I can see local VXLAN traffic getting to them from downstream EX switches, but nothing gets sent over the interconnect.

Kind regards

Dan

No, I never got this working.  I never had the luxury of hardware. Just Virtual. What version of vMX out of curiosity?  please do check back here and update if you have any success.

Initially I was using 23.1R1 on the vRouters, but found that it didn't accept the vxlan encapsulation for the interconnect (MPLS only). So I moved to 23.4R2, which is the current recommended firmware for the MX204, which accepts the vxlan encapsulation but results in the issue we've both seen. I was also using this release on the physical hardware with the same results. I then tried 25.2 (the most recent release) on the vRouters but no luck.

I'll definitely post back here if I get somewhere!

I am stucking for this DCI stiching for more than one week, it is the exact same result, tried on vEX, vMX, and the real MX routers. the leaf can learn remote DC host MAC, but ping between hosts are not working.

Someone said try to use vEVO, but I do not want to put more time on it as looks can not be boot up the vEVO-24.x on EVE-NG.

In all Juniper EVPN-VXLAN related documents are using QFX, do not get the point why Juniper stop to release newer version vQFX VM.

Regards

Marco