I was trying to do this in eveNG vQFX and the NNI communication was not working, but on physical devices it worked like a charm.
Original Message:
Sent: 07-05-2023 08:22
From: Olivier Benghozi
Subject: Q-in-Q on QFX5120-48y-8c
Yes, on the «NNI» (the double tagged interface), what we have here (by example) would be (as adapted to your values):
xe-0/0/1 { mtu 9192; flexible-vlan-tagging; encapsulation flexible-ethernet-services; unit 999 { encapsulation vlan-bridge; vlan-id 999; } }
Additionally, on a Q-in-Q P2P vlan (only 2 interfaces), you have some interest to disable mac-learning (not useful at all in this case), and add a description as best practice :)
vlans { v999 { description "Q-in-Q Amazingly Complicated Stuff v999"; interface xe-0/0/0.999; interface xe-0/0/1.999; switch-options { no-mac-learning; } }}
------------------------------
Olivier Benghozi
Original Message:
Sent: 07-05-2023 03:17
From: TAMAS VARGA
Subject: Q-in-Q on QFX5120-48y-8c
Thank you, yes it worked that way. Although I would have one more question.
When I build up a connection like this CE1-----QFX------CE2 then Q-in-Q works as in the documentation.
However when I try to use 2 switches and the double tagged ethernet frames should travers from one switch to another, then it is not working:
CE1 e0/0-------xe-0/0/0 QFX1 xe-0/0/1-------xe-0/0/1 QFX2 xe-0/0/0------e0/0 CE2
CE1################interface Ethernet0/0 no ip address!interface Ethernet0/0.100 encapsulation dot1Q 100 ip address 10.0.0.1 255.255.255.0!interface Ethernet0/0.200 encapsulation dot1Q 200 ip address 20.0.0.1 255.255.255.0!interface Ethernet0/0.300 encapsulation dot1Q 300 ip address 30.0.0.1 255.255.255.0QFX1################interfaces { xe-0/0/0 { flexible-vlan-tagging; mtu 1522; encapsulation extended-vlan-bridge; unit 999 { vlan-id-list 100-800; input-vlan-map push; output-vlan-map pop; } } # This one seems to be wrong xe-0/0/1 { flexible-vlan-tagging; encapsulation extended-vlan-bridge; unit 999 { vlan-id 999; } }vlans { v999 { interface xe-0/0/0.999; interface xe-0/0/1.999; }}QFX2################interfaces { xe-0/0/0 { flexible-vlan-tagging; mtu 1522; encapsulation extended-vlan-bridge; unit 999 { vlan-id-list 100-800; input-vlan-map push; output-vlan-map pop; } } xe-0/0/1 { flexible-vlan-tagging; encapsulation extended-vlan-bridge; unit 999 { vlan-id 999; } }vlans { v999 { interface xe-0/0/0.999; interface xe-0/0/1.999; }}CE2################interface Ethernet0/0 no ip address!interface Ethernet0/0.100 encapsulation dot1Q 100 ip address 10.0.0.2 255.255.255.0!interface Ethernet0/0.200 encapsulation dot1Q 200 ip address 20.0.0.2 255.255.255.0!interface Ethernet0/0.300 encapsulation dot1Q 300 ip address 30.0.0.2 255.255.255.0
------------------------------
TAMAS VARGA
Original Message:
Sent: 07-04-2023 06:52
From: Olivier Benghozi
Subject: Q-in-Q on QFX5120-48y-8c
Rather use this documentation
------------------------------
Olivier Benghozi
Original Message:
Sent: 07-03-2023 10:57
From: TAMAS VARGA
Subject: Q-in-Q on QFX5120-48y-8c
Hi,
I would like to use dot1q tunneling on a QFX5120-48Y-8C switch (19.4R1.10) and I started based on this documentation.
Unfortunately the
set vlans MY-VLAN dot1q-tunneling
command is not available on my device. I checked the Feature Navigator and it seems that the function should be available since Junos OS 18.3R1.
What do I miss ?
------------------------------
TAMAS VARGA
------------------------------