ip route in the kernel does not match routes in bgp #5026
Description
Description
Steps to reproduce the issue:
- download vlab-01.img, vlab-01.memdmp, vlab-01.xml from https://sonic-jenkins.westus2.cloudapp.azure.com/job/vs/job/buildimage-vs-image-pr/4972/artifact/kvmdump/
- modify disk location in vlab-01.xml to point to vlab-01.img
- in virsh, restore vlab-01.memdmp --xml vlab-01.xml
- reconnect the T0 testbed to this dut.
- ./testbed-cli.sh -m veos.vtb -t vtestbed.csv connect-topo vms-kvm-t0 lab password.txt
- do route announcement. py.test $PYTEST_COMMON_OPTS test_announce_routes.py
Describe the results you received:
check ip route.
admin@vlab-01:~$ ip route
10.0.0.56/31 dev PortChannel0001 proto kernel scope link src 10.0.0.56
10.0.0.58/31 dev PortChannel0002 proto kernel scope link src 10.0.0.58
10.0.0.60/31 dev PortChannel0003 proto kernel scope link src 10.0.0.60
10.0.0.62/31 dev PortChannel0004 proto kernel scope link src 10.0.0.62
10.250.0.0/24 dev eth0 proto kernel scope link src 10.250.0.101
192.168.0.0/21 dev Vlan1000 proto kernel scope link src 192.168.0.1
240.127.1.0/24 dev docker0 proto kernel scope link src 240.127.1.1 linkdown
check ip bgp sum
admin@vlab-01:~$ show ip bgp sum
IPv4 Unicast Summary:
BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0
BGP table version 2
RIB entries 12807, using 2301 KiB of memory
Peers 4, using 82 KiB of memory
Peer groups 6, using 384 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
10.0.0.57 4 64600 14414 1282 0 0 0 00:52:03 6399 ARISTA01T1
10.0.0.59 4 64600 7687 1289 0 0 0 00:52:02 6400 ARISTA02T1
10.0.0.61 4 64600 7687 1289 0 0 0 00:52:02 6400 ARISTA03T1
10.0.0.63 4 64600 7687 1289 0 0 0 00:52:02 6400 ARISTA04T1
Total number of neighbors 4
show ip bgp will give you lots of routes.
vlab-01# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR, f - OpenFabric,
> - selected route, * - FIB route, q - queued route, r - rejected route
C>* 10.0.0.56/31 is directly connected, PortChannel0001, 00:53:40
C>* 10.0.0.58/31 is directly connected, PortChannel0002, 00:53:39
C>* 10.0.0.60/31 is directly connected, PortChannel0003, 00:53:39
C>* 10.0.0.62/31 is directly connected, PortChannel0004, 00:53:39
C>* 10.1.0.32/32 is directly connected, Loopback0, 02:38:39
C>* 10.250.0.0/24 is directly connected, eth0, 02:38:50
C>* 192.168.0.0/21 is directly connected, Vlan1000, 02:38:40
something is wrong with frr
Describe the results you expected:
ip route in the kernel should around 32000
Additional information you deem important:
**Output of `show version`:**
```
(paste your output here)
```
**Attach debug file `sudo generate_dump`:**
```
(paste your output here)
```