Missing vlan to vxlan vni mapping in the network-instance hierarchy
Closed this issue · 1 comments
vsrx commented
Looks like OC paths are missing for the vlan to vni (VXLAN network identifier) mapping within the EVPN routing instance. Below are the equivalent vendor config for Arista and Juniper.
Arista:
interface Vxlan1
vxlan source-interface Loopback0
vxlan udp-port 4789
vxlan vlan 100 vni 100000
vxlan vlan 200 vni 200000
https://www.arista.com/en/um-eos/eos-vxlan-commands#xx1152892
Juniper:
routing-instances {
TEST_EVI {
instance-type mac-vrf;
vtep-source-interface lo0.0;
service-type vlan-aware;
vlans {
VLAN_100 {
description "TEST VLAN 1";
vlan-id 100;
vxlan {
vni 100000;
}
}
VLAN_200 {
description "TEST VLAN 2";
vlan-id 200;
vxlan {
vni 200000;
}
}
}
}
}
github-actions commented
This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.