Hi,
Can you please advise on hardware and software in charge?
I tested the same on ACX7024 and PTX10001-36MR - and your config is commited without any issues.
I also found the follwing interesting link (was not aware about this - so thanks to your q. I learned something new :))
https://www.juniper.net/documentation/us/en/software/junos/evpn/topics/concept/overlapping-vlans.html
Pay attention to:
"In this situation, you can't use the same VLAN ID for two different tenants in separate MAC-VRF instances that share the same default forwarding instance. However, you can have a VLAN name with the same VLAN-ID (for example, vlan200 with VLAN ID 200) in two different MAC-VRF instances if they each have their own forwarding instances."
set routing-instances MAC-VRF1 forwarding-instance identifier 1
Hope you will find this useful.
BR,
Andrei
------------------------------
Andrei Cebotareanu
------------------------------
Original Message:
Sent: 07-05-2025 08:04
From: djadhav
Subject: Question on MAC-VRF
Hi.
I have to MAC-VRF routing instances configured to use the same vlan-id. Commit fails due to duplicate vlan-ids as follows:
{master:0}[edit]
lab@LEAF1# commit
[edit routing-instances tenant2 vlans]
'v101'
l2ald: MacVrf Duplicate vlan-id exists for vlan
[edit routing-instances tenant2 vlans]
Failed to parse vlan hierarchy completely
error: configuration check-out failed
My question is: Why is Junos complaining about duplicated VLAN IDs? Isn't the whole point of multiple MAC-VRF instances to reuse VLAN IDs?
Thanks,
Deepak
Configuration:
routing-instances {
tenant1 {
instance-type mac-vrf;
protocols {
evpn {
encapsulation vxlan;
extended-vni-list all;
}
}
vtep-source-interface lo0.0;
service-type vlan-based;
route-distinguisher 172.31.2.3:1;
vrf-target target:100:1;
vlans {
v101 {
vlan-id 101;
interface xe-0/0/2.101;
vxlan {
vni 10101;
}
}
}
}
tenant2 {
instance-type mac-vrf;
protocols {
evpn {
encapsulation vxlan;
extended-vni-list all;
}
}
vtep-source-interface lo0.0;
service-type vlan-based;
route-distinguisher 172.31.2.3:2;
vrf-target target:100:2;
vlans {
v101 {
vlan-id 101;
interface xe-0/0/3.101;
vxlan {
vni 10301;
}
}
}
}
}