Skip to content

Latest commit

 

History

History
184 lines (151 loc) · 4.32 KB

README.simple.bgp.md

File metadata and controls

184 lines (151 loc) · 4.32 KB
Raw

Use a simple routing topology as below to demonstrate SONiC VPP routing with bgp running as a routing protocol to distribute routes.

Host1 --------------------- Sonic-VPP-Router1 -------------- Sonic-VPP-Router2 ---------------- Host2

172.16.1.2/24       172.16.1.1/24   172.16.3.1/24  172.16.3.2/24   172.16.2.1/24        172.16.2.2/24

Pre-requisites for testing this out Make sure the docker is installed on the Linux system. iproute2 and sudo packages should be installed.

Load container images

docker load < docker-sonic-vpp.gz

Check if SONiC-VPP container image is listed

docker images | grep "sonic-vpp\|pause"

Get the script to create and run the sonic container from the sonic-platform-vpp repo if you have not cloned the repo.

wget https://raw.githubusercontent.com/sonic-net/sonic-platform-vpp/main/start_sonic_vpp.sh

Set the execute bits of the downloaded script file

chmod +x start_sonic_vpp.sh

Else if you have already cloned the sonic-platform-repo you can copy the script to the local directory and use it.

On the host create veth interface pairs for vpp and host

sudo ip link add name veth_vpp1 type veth peer name vpp1
sudo ip link add name veth_vpp2 type veth peer name vpp2
sudo ip link add name ir_vpp1 type veth peer name ir_vpp2

Create network namespace for end hosts and inject one end of veth pair

sudo ip netns add host-1.0
sudo ip netns add host-2.0

sudo ip link set dev veth_vpp1 netns host-1.0
sudo ip link set dev veth_vpp2 netns host-2.0

Configure IP addresses inside the host net namepaces

sudo ip netns exec host-1.0 bash
ip link set dev lo up
ip link set dev veth_vpp1 up
ip addr add 172.16.1.2/24 dev veth_vpp1
ip route add 172.16.2.0/24 via 172.16.1.1
ip address show
ip route show
exit

sudo ip netns exec host-2.0 bash
ip link set dev lo up
ip link set dev veth_vpp2 up
ip addr add 172.16.2.2/24 dev veth_vpp2
ip route add 172.16.1.0/24 via 172.16.2.1
ip address show
ip route show
exit

Now start the sonic container and pass the veth interfaces to sonic-vpp

sudo ./start_sonic_vpp.sh start -n sonic-vpp1 -i vpp1,ir_vpp1

start the second sonic container and pass the veth interfaces to sonic-vpp

sudo ./start_sonic_vpp.sh start -n sonic-vpp2 -i vpp2,ir_vpp2

Get into the first sonic container and configure network addresses and routes

docker exec -it sonic-vpp1 /bin/bash
ip link show

config interface ip add Ethernet0 172.16.1.1/24
config interface ip add Ethernet1 172.16.3.1/24
config interface startup Ethernet0
config interface startup Ethernet1

vtysh
config
router bgp 65100
 bgp log-neighbor-changes
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 bgp bestpath as-path multipath-relax
 neighbor 172.16.3.2 remote-as 65100
 !
 address-family ipv4 unicast
  network 172.16.1.0/24
  neighbor 172.16.3.2 activate
  maximum-paths 64
 exit-address-family
 !
 address-family ipv6 unicast
  maximum-paths 64
 exit-address-family
exit
exit
exit

ip route show
exit

Get into the second sonic container and configure network addresses and routes

docker exec -it sonic-vpp2 /bin/bash
ip link show

config interface ip add Ethernet0 172.16.2.1/24
config interface ip add Ethernet1 172.16.3.2/24
config interface startup Ethernet0
config interface startup Ethernet1

vtysh
config
router bgp 65100
 bgp log-neighbor-changes
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 bgp bestpath as-path multipath-relax
 neighbor 172.16.3.1 remote-as 65100
 !
 address-family ipv4 unicast
  network 172.16.2.0/24
  neighbor 172.16.3.1 activate
  maximum-paths 64
 exit-address-family
 !
 address-family ipv6 unicast
  maximum-paths 64
 exit-address-family
exit
exit
exit

ip route show
exit

Check the bgp status in the container

docker exec -it sonic-vpp1 /bin/bash
vtysh -c "show ip bgp summary"
vtysh -c "show ip bgp neighbor"
vtysh -c "show ip bgp"

Check the routes injected in the routing table

docker exec -it sonic-vpp1 /bin/bash
ip route show

Test the end-to-end packet routing from the host

sudo ip netns exec host-1.0 bash
ping -c5  172.16.1.1
ping -c5  172.16.2.2
exit

You should see the ping reachability to sonic router and to the host in the other network namespace.

Use below command to stop the sonic-vpp containers

sudo ./start_sonic_vpp.sh stop -n sonic-vpp1
sudo ./start_sonic_vpp.sh stop -n sonic-vpp2