[vpp-dev] linux-cp: Setup loop on startup and netlink sync not working in specific circumstances

Fri, 24 Feb 2023 18:17:58 -0800 

Hi,
I was testing the LCP plugin with the Netlink listener and faced two major issues: 1. If the LCP interface is being created on startup and you create sub-interfaces directly afterwards, then linux-cp/router will flush the table, install all routes and addresses again and this goes endless. The peak was 400 netdev changes in a second. However, if I create the LCP interface after all sub-interfaces were created, then this issue does not occur but the sub-interfaces will not automatically be created. 


2. If the lcp-sync is being enabled via exec (e.g. bootstrap.vpp) and 
not in startup.conf, then it can happen that routes created in Linux 
will not be synced to the VPP FIB. Curiously, the first problem does not 
occur with this config.



I can reproduce both issues on two different systems (both are running 
Ubuntu 22.04 LTS with kernel 5.15.0-60-generic and VPP 23.02-release).



I've attached a sample config for both cases where I was able to 
reproduce the issues.


Any help or suggestion is appreciated!

Cheers,
Tom

#
# This configuration is managed by Ansible. Do not change anyting. Otherwise, 
changes may get overwritten.
#

set logging class linux-cp rate-limit 1000 level warn syslog-level notice
set interface mtu packet 1500 TenGigabitEthernet1/0/0
set interface state TenGigabitEthernet1/0/0 up
set interface mtu packet 1500 TenGigabitEthernet1/0/1
set interface state TenGigabitEthernet1/0/1 up
create bond mode lacp load-balance l34 id 0
bond add BondEthernet0 TenGigabitEthernet1/0/0
bond add BondEthernet0 TenGigabitEthernet1/0/1
lcp create BondEthernet0 host-if bond0
create sub BondEthernet0 1163 dot1q 1163 exact-match
set interface ip address BondEthernet0.1163 100.64.0.2/30
create sub BondEthernet0 1116 dot1q 1116 exact-match
set interface ip address BondEthernet0.1116 172.16.254.35/31
create sub BondEthernet0 3103 dot1q 3103 exact-match
set interface ip address BondEthernet0.3103 172.31.254.4/31
create sub BondEthernet0 3104 dot1q 3104 exact-match
set interface ip address BondEthernet0.3104 172.31.254.6/31
create sub BondEthernet0 3105 dot1q 3105 exact-match
set interface ip address BondEthernet0.3105 172.31.254.9/31
set interface state BondEthernet0 up
set interface state BondEthernet0.1163 up
set interface state BondEthernet0.1116 up
set interface state BondEthernet0.3103 up
set interface state BondEthernet0.3104 up
set interface state BondEthernet0.3105 up

Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 172.31.254.0/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.16.254.32/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 172.16.254.33/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:100.64.0.0/30 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 100.64.0.2/30
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.0/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 172.31.254.0/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.2/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 172.31.254.2/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.8/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 172.31.254.8/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 11, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 11, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3102, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 172.31.254.2/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 13, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 13, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3105, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 172.31.254.8/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 5, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 5, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.1162, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 100.64.0.2/30
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 7, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 7, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.1115, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 172.16.254.33/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 9, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 9, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3101, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 172.31.254.0/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.16.254.32/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 172.16.254.33/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:100.64.0.0/30 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 100.64.0.2/30
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.0/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 172.31.254.0/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.2/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 172.31.254.2/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:172.31.254.8/31 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route skip: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 up
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 172.31.254.8/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 11, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 11, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3102 (42) -> BondEthernet0.3102/tap3.3102 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3102, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3102 172.31.254.2/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 13, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 13, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3105 (43) -> BondEthernet0.3105/tap3.3105 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3105, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3105 172.31.254.8/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 5, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 5, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1162 (39) -> BondEthernet0.1162/tap3.1162 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.1162, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1162 100.64.0.2/30
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 7, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 7, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.1115 (40) -> BondEthernet0.1115/tap3.1115 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.1115, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.1115 172.16.254.33/31
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 9, source lcp-rt
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: proto ipv4, fib-index 0, max sw_if_index 9, source lcp-rt-dynamic
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: Flush table: entries number to delete 0
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link: bond0.3101 (41) -> BondEthernet0.3101/tap3.3101 down
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: route del: 254:fe80::/64 connected,attached,
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router:  path:[ip6 0.0.0.0, BondEthernet0.3101, []]
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 fe80::92e2:baff:fe46:2154/64
Feb 25 01:29:18 cr1 vnet[35701]: linux-cp/router: link-addr: BondEthernet0.3101 172.31.254.0/31
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1115: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1162: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3101: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3102: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1115: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1162: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3101: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3102: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1115: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1162: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3101: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3102: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1115: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1162: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3101: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3102: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1115: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.1162: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3101: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3102: link becomes ready
[Sat Feb 25 01:29:17 2023] IPv6: ADDRCONF(NETDEV_CHANGE): bond0.3105: link becomes ready


#
# This configuration is managed by Ansible. Do not change anyting. Otherwise, 
changes may get overwritten.
#

unix {
  log /var/log/vpp/vpp.log
  nodaemon
  full-coredump
  cli-listen /run/vpp/cli.sock
  gid vpp
  exec /etc/vpp/bootstrap.vpp
}

api-trace {
  on
}

api-segment {
  gid vpp
}

socksvr {
  default
}

memory {
  main-heap-size 1536M
  main-heap-page-size default-hugepage
}

cpu {
  main-core 0
  workers 3
}

buffers {
  buffers-per-numa 128000
  default data-size 2048
  page-size default-hugepage
}

dpdk {
  dev 0000:03:00.0 {
  }
  dev 0000:03:00.1 {
  }
}

statseg {
  size 1G
  page-size default-hugepage
  per-node-counters off
}

plugins {
  plugin linux_cp_plugin.so {
    enable
  }
  plugin linux_nl_plugin.so {
    enable
  }
}

logging {
  default-log-level info
  default-syslog-log-level info
}

linux-cp {
  default netns dataplane
  lcp-sync
  lcp-auto-subint
}

ethernet {
  default-mtu 1500
}

#
# This configuration is managed by Ansible. Do not change anyting. Otherwise, 
changes may get overwritten.
#

set logging class linux-cp rate-limit 1000 level warn syslog-level notice
lcp default netns dataplane
lcp lcp-sync on
lcp lcp-auto-subint on

set interface mtu packet 1500 TenGigabitEthernet1/0/0
set interface state TenGigabitEthernet1/0/0 up
set interface mtu packet 1500 TenGigabitEthernet1/0/1
set interface state TenGigabitEthernet1/0/1 up
create bond mode lacp load-balance l34 id 0
bond add BondEthernet0 TenGigabitEthernet1/0/0
bond add BondEthernet0 TenGigabitEthernet1/0/1
lcp create BondEthernet0 host-if bond0
create sub BondEthernet0 1163 dot1q 1163 exact-match
set interface ip address BondEthernet0.1163 100.64.0.2/30
create sub BondEthernet0 1116 dot1q 1116 exact-match
set interface ip address BondEthernet0.1116 172.16.254.35/31
create sub BondEthernet0 3103 dot1q 3103 exact-match
set interface ip address BondEthernet0.3103 172.31.254.4/31
create sub BondEthernet0 3104 dot1q 3104 exact-match
set interface ip address BondEthernet0.3104 172.31.254.6/31
create sub BondEthernet0 3105 dot1q 3105 exact-match
set interface ip address BondEthernet0.3105 172.31.254.9/31
set interface state BondEthernet0 up
set interface state BondEthernet0.1163 up
set interface state BondEthernet0.1116 up
set interface state BondEthernet0.3103 up
set interface state BondEthernet0.3104 up
set interface state BondEthernet0.3105 up

#
# This configuration is managed by Ansible. Do not change anyting. Otherwise, 
changes may get overwritten.
#

unix {
  log /var/log/vpp/vpp.log
  nodaemon
  full-coredump
  cli-listen /run/vpp/cli.sock
  gid vpp
  exec /etc/vpp/bootstrap.vpp
}

api-trace {
  on
}

api-segment {
  gid vpp
}

socksvr {
  default
}

memory {
  main-heap-size 1536M
  main-heap-page-size default-hugepage
}

cpu {
  main-core 0
  workers 3
}

buffers {
  buffers-per-numa 128000
  default data-size 2048
  page-size default-hugepage
}

dpdk {
  dev 0000:03:00.0 {
  }
  dev 0000:03:00.1 {
  }
}

statseg {
  size 1G
  page-size default-hugepage
  per-node-counters off
}

plugins {
  plugin linux_cp_plugin.so {
    enable
  }
  plugin linux_nl_plugin.so {
    enable
  }
}

logging {
  default-log-level info
  default-syslog-log-level info
}

ethernet {
  default-mtu 1500
}

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22625): https://lists.fd.io/g/vpp-dev/message/22625
Mute This Topic: https://lists.fd.io/mt/97220154/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-















    











					Reply via email to