ipng/vppcfg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add caveat on bridgedomain configurability

Browse Source
This commit is contained in:
Pim van Pelt
2022-04-03 14:29:35 +00:00
parent dc0d785818
commit 79f41d447d
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/config-guide.md
View File

@ -111,6 +111,11 @@ number of tags they have, so a simple dot1q sub-interface will be configured as
a QinQ or QinAD sub-interface will be configured as `pop 2`. Conversely, when interfaces are a QinQ or QinAD sub-interface will be configured as `pop 2`. Conversely, when interfaces are
removed from the bridge, their tag-rewriting will be disabled. removed from the bridge, their tag-rewriting will be disabled.
*Caveat*: Currently, bridgedomains are always created with their default attributes in VPP, that
is to say with learning and unicast forwarding turned on, unknown-unicast flooding enabled,
and ARP terminating and aging turned off. In a future release, `vppcfg` will give more
configuration options.
Examples: Examples:
``` ```
bridgedomains: bridgedomains:
@ -138,7 +143,7 @@ Note that the configuration object here only specifies the link aggregation and
BondEthernets are expected to occur as well in the `interfaces` section, where their sub-interfaces BondEthernets are expected to occur as well in the `interfaces` section, where their sub-interfaces
and IP addresses and so on are specified. and IP addresses and so on are specified.
Caveat: Currently, BondEthernets are always created as `LACP` typed devices with a loadbalance *Caveat*: Currently, BondEthernets are always created as `LACP` typed devices with a loadbalance
strategy of `l34`. In a future release of `vppcfg`, the type and strategy will be configurable. strategy of `l34`. In a future release of `vppcfg`, the type and strategy will be configurable.
Examples: Examples: