Jason, I don't think vlan sub-interfaces are supported. We used multiple interfaces mapped to different vlans via the Hypervisor. You can map em0 to vlan 14 and em1 to vlan 45, ...
-- Clinton Work On Mon, Nov 4, 2019, at 9:02 AM, Jason Lixfeld wrote: > Hey, > > Running the JunOS VRR image on EVE-NG trying to get a vlan > sub-interface working on em0: > > root@R4# show interfaces em0 > traps; > vlan-tagging; > mtu 1614; > hold-time up 10000 down 0; > unit 14 { > vlan-id 14; > family inet { > address 100.1.4.4/24; > } > family iso; > family inet6 { > address 2607:f0c8::100:1:4:4/112; > } > family mpls; > } > unit 45 { > vlan-id 45; > family inet { > address 100.4.5.4/24; > } > family iso; > family inet6 { > address 2607:f0c8::100:4:5:4/112; > } > family mpls; > } > > [edit] > root@R4# > > R4 can ping itself at 100.1.4.4. While capturing on em0 and tying to > ping 100.1.4.1 from R4, I see correctly tagged ARP request/reply, but > the ARP table is empty, so no pingy. > > Is this not supported, or am I missing something? > > Thanks in advance! > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp