search

sonic-net / sonic-dbsyncd

Python library for sonic/redis database syncing
Other
6 stars 47 forks source link

applDB not updated after LLDP neighbor goes offline #24

Closed GarrickHe closed 5 years ago

GarrickHe commented 5 years ago

The applDB still contains entries of LLDP neighbor(s) even when the neighbor goes offline.

Steps to reproduce:

1. shutdown the interface connected to a lldp neighbor.
2. start redis-cli
3. run 'keys "*LLDP*"
4. notice disabled neighbors still in applDB

On my testbed I did:

root@sonic:~# ifconfig eth0 down
root@sonic:~# ifconfig Ethernet0 down
<<< waited until TTL (120s) expired >>>
root@sonic:~# redis-cli -n 0
127.0.0.1:6379> keys "*LLDP*"
1) "LLDP_ENTRY_TABLE:Ethernet0"   <<=== should not be here
2) "LLDP_LOC_CHASSIS"
3) "LLDP_ENTRY_TABLE:eth0"   <<=== should not be here
127.0.0.1:6379>

From Linux's perspective, there are no neighbors:

root@sonic:~# lldpctl
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
root@sonic:~#

version information:

root@sonic:~# show version

SONiC Software Version: SONiC.master.0-dirty-20190717.222513
Distribution: Debian 9.9
Kernel: 4.9.0-9-2-amd64
Build commit: 66ea5b53
Build date: Thu Jul 18 05:40:18 UTC 2019
Built by: ghe@ghe-sonic1

Platform: x86_64-dell_z9100_c2538-r0
HwSKU: Force10-Z9100-C32
ASIC: broadcom
Serial Number: CN03GT5N7793154G0033
Uptime: 00:42:33 up 1 day,  3:57,  1 user,  load average: 0.04, 0.10, 0.14

Docker images:
REPOSITORY                    TAG                              IMAGE ID            SIZE
docker-sonic-mgmt-framework   latest                           a4966c8fb578        413MB
docker-sonic-telemetry        latest                           9429665feb17        344MB
docker-sonic-telemetry        master.0-dirty-20190717.222513   1f517230b92c        305MB
docker-fpm-frr                latest                           a2ac606a41b5        318MB
docker-fpm-frr                master.0-dirty-20190717.222513   a2ac606a41b5        318MB
docker-orchagent              latest                           312692460b8b        318MB
docker-orchagent              master.0-dirty-20190717.222513   312692460b8b        318MB
docker-snmp-sv2               latest                           66ed850a701c        312MB
docker-snmp-sv2               master.0-dirty-20190717.222513   66ed850a701c        312MB
docker-teamd                  latest                           a2e48312bc5d        300MB
docker-teamd                  master.0-dirty-20190717.222513   a2e48312bc5d        300MB
docker-syncd-brcm             latest                           35c8d14a2074        391MB
docker-syncd-brcm             master.0-dirty-20190717.222513   35c8d14a2074        391MB
docker-lldp-sv2               latest                           dc5c3e897c47        298MB
docker-lldp-sv2               master.0-dirty-20190717.222513   dc5c3e897c47        298MB
docker-platform-monitor       latest                           ca3c990ab67c        325MB
docker-platform-monitor       master.0-dirty-20190717.222513   ca3c990ab67c        325MB
docker-dhcp-relay             latest                           01c30e7c6c00        287MB
docker-dhcp-relay             master.0-dirty-20190717.222513   01c30e7c6c00        287MB
docker-database               latest                           dc332c1fbbd8        279MB
docker-database               master.0-dirty-20190717.222513   dc332c1fbbd8        279MB
docker-router-advertiser      latest                           18ab2795b5cc        278MB
docker-router-advertiser      master.0-dirty-20190717.222513   18ab2795b5cc        278MB
GarrickHe commented 5 years ago

Any updates?