BVI support

[jpaulovecchi]

Hello,
Please I would like to know if the standard BVI configuration works with SONiC VPP? I have made the same configuration with the VS image and it works.

• port configured as trunk (switchport)
• vlan created
• vlan allowed in the trunk port (vlan member)
• ip aassigned to the vlan
  The show logging |grep vpp includes the information that it is a BVI, but I cannot ping the other side of the connection. Same works with the VS image.
  Thanks for looking into this.
  Best regards,
  Joao.

[jpaulovecchi]

Please, which logs do you need to verify this issue? Thanks.

[bendrapubalareddy]

Yes, read at https://github.com/sonic-net/sonic-platform-vpp/blob/master/docs/README.8021q.routing.topo.md regards, Bala

…

On Mon, Sep 29, 2025 at 5:35 AM jpaulovecchi ***@***.***> wrote: *jpaulovecchi* created an issue (sonic-net/sonic-platform-vpp#199) <#199> Hello, Please I would like to know if the standard BVI configuration works with SONiC VPP? I have made the same configuration with the VS image and it works. - port configured as trunk (switchport) - vlan created - vlan allowed in the trunk port (vlan member) - ip aassigned to the vlan The show logging |grep vpp includes the information that it is a BVI, but I cannot ping the other side of the connection. Same works with the VS image. Thanks for looking into this. Best regards, Joao. — Reply to this email directly, view it on GitHub <#199>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADKZN6TS2SSVI7HDLQW3OIT3VERSBAVCNFSM6AAAAACHZDPPC2VHI2DSMVQWIX3LMV43ASLTON2WKOZTGQ3DIOBRHEZDEOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jpaulovecchi]

Hi Bala,

Thanks for your reply and sorry to bother again. I am running SONiC-VPP as a VM image over KVM with DPDK interfaces enabled. When I create the sonic config I see the following for Vlan20 interface:

sudo config vlan add 20
sudo config interface ip add Vlan20 192.168.20.1/24
sudo config switchport mode trunk Ethernet4
sudo config vlan member add 20 Ethernet4

39: Vlan20@Bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9100 qdisc noqueue state UP group default qlen 1000
link/ether 22:27:a2:45:8b:dc brd ff:ff:ff:ff:ff:ff
inet 192.168.20.1/24 brd 192.168.20.255 scope global Vlan20
valid_lft forever preferred_lft forever
inet6 fe80::2027:a2ff:fe45:8bdc/64 scope link
valid_lft forever preferred_lft forever
40: Ethernet4.20@Ethernet4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 22:27:a2:45:8b:dc brd ff:ff:ff:ff:ff:ff (I brought this interface UP but did not change anything)

jpaulo@sonic:~$ show vlan config
Name VID Member Mode

---

Vlan20 20 Ethernet4 tagged

jpaulo@sonic:~$ show int status
Interface Lanes Speed MTU FEC Alias Vlan Oper Admin Type Asym PFC

---

Ethernet0 25,26,27,28 1G 1500 N/A fortyGigE0/0 routed up up N/A N/A
Ethernet4 29,30,31,32 1G 1500 N/A fortyGigE0/4 trunk up up N/A N/A

jpaulo@sonic:~$ show ip int
Interface Master IPv4 address/mask Admin/Oper BGP Neighbor Neighbor IP

---

Ethernet0 192.168.1.3/31 up/up N/A N/A
Ethernet8 100.64.200.1/24 up/up N/A N/A
Loopback0 2.2.2.2/32 up/up N/A N/A
Vlan20 192.168.20.1/24 up/up N/A N/A
docker0 240.127.1.1/24 up/down N/A N/A
eth0 10.73.160.187/24 up/up N/A N/A
lo 127.0.0.1/16 up/up N/A N/A

jpaulo@sonic:~$ ping 192.168.20.1
PING 192.168.20.1 (192.168.20.1) 56(84) bytes of data.
64 bytes from 192.168.20.1: icmp_seq=1 ttl=64 time=0.051 ms

Attached some logs after a reboot to check interfaces coming up, it seems fine as per process syncd#syncd#syncd: :- vpp_add_del_intf_ip_addr_norif: Setting ip on hw_ifname bvi20.

Anyways I tried to use the commands you share using netns, but I cannot use the start_vpp script to call the interfaces without a container.

Thanks for your time looking into this again.

Best regards,
Joao.

[jpaulovecchi]

Hello,
I also tried to another test that was configuring the lan side interface as an access port in a vlan10. I had to enable VXLAN/EVPN for this same test and when I did that the image keeps rebooting (I can share the logs).
Is it possible to use L2 features in the SONiC VPP image without docker? My image works perfectly when the interfaces are in L3 mode and achieved more than 2.5Gbps with a traffic tester that can go up to this speed now.
Thanks for your time looking into this.
Best regards,
Joao.

[jpaulovecchi]

Hello Team,

To avoid the reboots I had to also configure the VPP and used the following steps:

Topology:
Host Port6 -- Ethernet4/Virtio/vlan10 access SONiC VPP_1 Ethernet0/Virtio 100.64.1.1/30 -- 100.64.1.2/30 Ethernet0/Virtio SONiC VPP_2 Ethernet4/Virtio/vlan10 access -- Host Port6

1. VPP (docker exec -it syncd bash)
   create vxlan tunnel src 2.2.2.2 dst 1.1.1.1 vni 100010 instance 0
   set int l2 xconnect vxlan_tunnel0 bobm1
   set int l2 xconnect bobm1 vxlan_tunnel0
   set int l2 xconnect vxlan_tunnel0 tap4097
   set int l2 xconnect tap4097 vxlan_tunnel0

2. SONiC CLI:
   sudo config vlan add 10
   sudo config switchport mode access Ethernet4
   sudo config vlan member add 10 Ethernet4
   sudo config interface ip add Loopback0 2.2.2.2/32
   sudo config vxlan add vxlan1 2.2.2.2
   sudo config vxlan evpn_nvo add vxlan_vlan10 vxlan1
   sudo config interface ip add Ethernet0 100.64.1.2/30
   sudo config vxlan map add vxlan1 10 100010

3. FRR
   router bgp 65100
   bgp router-id 100.64.1.2
   no bgp log-neighbor-changes
   no bgp default ipv4-unicast
   no bgp default show-hostname
   no bgp default show-nexthop-hostname
   no bgp deterministic-med
   bgp bestpath as-path multipath-relax
   timers bgp 60 180
   neighbor overlay peer-group
   neighbor overlay remote-as 65100
   neighbor overlay update-source 2.2.2.2
   neighbor overlay timers connect 120
   neighbor underlay peer-group
   neighbor underlay remote-as 65100
   neighbor underlay timers connect 120
   neighbor 1.1.1.1 peer-group overlay
   neighbor 100.64.1.1 peer-group underlay
   neighbor 100.64.1.1 description rv2
   !
   address-family ipv4 unicast
   network 2.2.2.2/32
   neighbor underlay activate
   maximum-paths 64
   exit-address-family
   !
   address-family l2vpn evpn
   neighbor overlay activate
   advertise-all-vni
   exit-address-family
   exit

I see the control plane working fine, but still no traffic being encapsulated:
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 100.64.1.1:2
*>i [2]:[0]:[48]:[28:9a:f7:06:62:67] HOST A
1.1.1.1 100 0 i
RT:65100:100010 ET:8
*>i [3]:[0]:[32]:[1.1.1.1]
1.1.1.1 100 0 i
RT:65100:100010 ET:8
Route Distinguisher: 100.64.1.2:2
*> [2]:[0]:[48]:[22:1c:9b:ea:08:d4]
2.2.2.2 32768 i
ET:8 RT:65100:100010
*> [2]:[0]:[48]:[22:1c:9b:ea:08:d4]:[128]:[fe80::201c:9bff:feea:8d4]
2.2.2.2 32768 i
ET:8 RT:65100:100010 ND:Router Flag
*> [2]:[0]:[48]:[28:9a:f7:06:3f:3d] HOST B
2.2.2.2 32768 i
ET:8 RT:65100:100010
*> [3]:[0]:[32]:[2.2.2.2]
2.2.2.2 32768 i
ET:8 RT:65100:100010

Traffic on Ethernet4:
jpaulo@sonic:~$ sudo tcpdump -i Ethernet4
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on Ethernet4, link-type EN10MB (Ethernet), snapshot length 262144 bytes
08:59:06.084500 28:9a:f7:06:62:67 (oui Unknown) > 01:80:ea:00:01:08 (oui Unknown), ethertype Unknown (0x88b7), length 68:

vpp# show interface
bobm1 2 up 9122/0/0/0 rx packets 1227
rx bytes 78528
tx packets 14
tx bytes 2122
drops 248
punt 4
tx-error 1
vxlan_tunnel0 7 up 9000/0/0/0 rx packets 1026
rx bytes 76067
tx packets 1244
tx bytes 136834
vpp# show bridge-domain
BD-ID Index BSN Age(min) Learning U-Forwrd UU-Flood Flooding ARP-Term arp-ufwd Learn-co Learn-li BVI-Intf
10 1 0 off on on flood on off off 0 16777216 N/A

The show errors are increasing:
vpp# show errors
Count Node Reason Severity
17 vxlan4-input good packets decapsulated error
1 vxlan4-encap good packets encapsulated error
18 l2-output L2 output packets error
18 l2-input L2 input packets error
16 vxlan4-encap good packets encapsulated error
16 l2-output L2 output packets error
16 l2-input L2 input packets error

Please, is there anything missing from my configuration? Thanks for your time looking into this.

Best regards,
Joao.

[jpaulovecchi]

I changed the bridge-domain and include the vxlan_tunnel, the dpdk and the interface together. This seems to be resolved the problem. But the other scenario with the BVI interface and IP, I could not fix yet.

Steps below for the EVPN changes:

set interface l2 bridge vxlan_tunnel0 10
set interface l2 bridge bobm1 10
set interface l2 bridge tap4097 10
set interface l2 tag-rewrite bobm1 disable
set interface l2 tag-rewrite tap4097 disable
set interface l2 tag-rewrite vxlan_tunnel0 disable

vpp# show bridge-domain 10 detail
BD-ID Index BSN Age(min) Learning U-Forwrd UU-Flood Flooding ARP-Term arp-ufwd Learn-co Learn-li BVI-Intf
10 1 0 off on on flood on off off 4 16777216 N/A
span-l2-input l2-input-classify l2-input-feat-arc l2-policer-classify l2-input-acl vpath-input-l2 l2-ip-qos-record l2-input-vtr l2-learn l2-rw l2-fwd l2-flood l2-flood l2-output

       Interface           If-idx ISN  SHG  BVI  TxFlood        VLAN-Tag-Rewrite
         bobm1               2     13   0    -      *                 none
        tap4097              4     11   0    -      *                 none
     vxlan_tunnel0           7     1    0    -      *                 non

vpp# show errors
Count Node Reason Severity
368 vxlan4-input good packets decapsulated error
13 vxlan4-encap good packets encapsulated error
428 l2-output L2 output packets error
381 l2-learn L2 learn packets error
381 l2-input L2 input packets error
47 l2-flood L2 flood packets error
352 vxlan4-encap good packets encapsulated error
369 l2-output L2 output packets error
352 l2-learn L2 learn packets error
352 l2-input L2 input packets error
17 l2-flood L2 flood packets error

18:17:21.601277 28:9a:f7:06:3f:3d (oui Unknown) > 01:80:ea:00:01:08 (oui Unknown), ethertype Unknown (0x88b7), length 64:
..
18:17:21.831681 28:9a:f7:06:62:67 (oui Unknown) > 01:80:ea:00:01:08 (oui Unknown), ethertype Unknown (0x88b7), length 64:

Thanks,
Joao.