diff options
| author | Christian Breunig <christian@breunig.cc> | 2023-09-09 07:13:31 +0200 |
|---|---|---|
| committer | Christian Breunig <christian@breunig.cc> | 2023-09-09 07:17:40 +0200 |
| commit | cfe1dbd7ab9c8ab55eeca04c0c2e01b0299cc558 (patch) | |
| tree | 75ddae16e0f0b525eb28f992fc547d6d4635f3a9 /interface-definitions/system-sflow.xml.in | |
| parent | 2a8a76c40c7017782cdfba722b6ac4057d013610 (diff) | |
| download | vyos-1x-cfe1dbd7ab9c8ab55eeca04c0c2e01b0299cc558.tar.gz vyos-1x-cfe1dbd7ab9c8ab55eeca04c0c2e01b0299cc558.zip | |
vxlan: T3700: support VLAN tunnel mapping of VLAN aware bridges
FRR supports a new way of configuring VLAN-to-VNI mappings for EVPN-VXLAN, when
working with the Linux kernel. In this new way, the mapping of a VLAN to a VNI
is configured against a container VXLAN interface which is referred to as a
'Single VXLAN device (SVD)'.
Multiple VLAN to VNI mappings can be configured against the same SVD. This
allows for a significant scaling of the number of VNIs since a separate VXLAN
interface is no longer required for each VNI.
Sample configuration of SVD with VLAN to VNI mappings is shown below.
set interfaces bridge br0 member interface vxlan0
set interfaces vxlan vxlan0 external
set interfaces vxlan vxlan0 source-interface 'dum0'
set interfaces vxlan vxlan0 vlan-to-vni 10 vni '10010'
set interfaces vxlan vxlan0 vlan-to-vni 11 vni '10011'
set interfaces vxlan vxlan0 vlan-to-vni 30 vni '10030'
set interfaces vxlan vxlan0 vlan-to-vni 31 vni '10031'
(cherry picked from commit 7f6624f5a6f8bd1749b54103ea5ec9f010adf778)
Diffstat (limited to 'interface-definitions/system-sflow.xml.in')
0 files changed, 0 insertions, 0 deletions