Hello Luke,
You are not doing something wrong. The configuration is fine.
The Problem is with the vLabs. The devices are most probably connected through some VMs, and they don't allow you to send tagged traffic.
I've observed the same problem on the vMX. And I just cannot ping a directly connected neighbor.
The config from R1:
set interfaces ge-0/0/0 per-unit-scheduler
set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 unit 10 vlan-id 10
set interfaces ge-0/0/0 unit 10 family inet address 172.16.10.1/24
set interfaces ge-0/0/0 unit 20 vlan-id 20
set interfaces ge-0/0/0 unit 20 family inet address 172.16.20.1/24
The config from R2:
set interfaces ge-0/0/0 per-unit-scheduler
set interfaces ge-0/0/0 flexible-vlan-tagging
set interfaces ge-0/0/0 unit 10 vlan-id 10
set interfaces ge-0/0/0 unit 10 family inet address 172.16.10.2/24
set interfaces ge-0/0/0 unit 20 vlan-id 20
set interfaces ge-0/0/0 unit 20 family inet address 172.16.20.2/24
This config works perfectly in GNS3 and on real devices, but not on the vLabs devices. I used the "
vLab Sandbox: JET for Junos - Automation and Programmability".
Original Message:
Sent: 03-18-2020 19:38
From: Unknown User
Subject: vMX in vLabs and VLANs
FYI, I've now also tried this with vSRX.
I have two vSRX connected directly together on ge-0/0/1.
I've then added this config to make two subinterfaces:
jcluser@vSRX1# show interfaces ge-0/0/1 vlan-tagging;unit 100 { vlan-id 100; family inet { address 192.168.100.1/24; }}unit 200 { vlan-id 200; family inet { address 192.168.200.1/24; }}
Each srx can ping their own IP's, but not the neighbour IP's.
Any ideas where I'm going wrong?