Labs

Hi all,

Running into something odd with EVPN on vMX in the open labs and wondering if anyone's seen this before.

I've got a simple EVPN L2 service (instance-type evpn, vlan-id 90) between two PEs. Control plane looks fine - Type 3 IM routes are there between PEs.

If I use an untagged AC (encapsulation ethernet-bridge, unit 0), everything works as expected -MAC learning happens, Type 2 (MAC/IP) routes show up, end-to-end traffic is fine

But when I switch to a tagged AC:

set interfaces ge-0/0/3 flexible-vlan-tagging

set interfaces ge-0/0/3 encapsulation flexible-ethernet-services

set interfaces ge-0/0/3 unit 90 encapsulation vlan-bridge

set interfaces ge-0/0/3 unit 90 vlan-id 90

set interfaces ge-0/0/3 unit 90 family bridge

I get no packets on ge-0/0/3.90, no MAC learning, and only Type 3 routes (no Type 2)

The physical interface shows traffic, but VLAN tagged frames stay at 0, so it looks like the PE never actually sees tagged frames.

CEs are configured with VLAN 90 subinterfaces and are sending traffic.

Feels like something in JCL / ESXi is stripping or not passing 802.1Q tags properly. Has anyone hit this with vMX in JCL or similar setups?

Anything specific needed on the hypervisor side (trunk mode, VLAN 4095, TPID quirks, etc.) to make tagged EVPN ACs work?

Cheers