Kelly Chen e0f8aa71d6 [lldpmgrd] only log error in is_port_up() after port init done (#4606) ... lldpmgrd listens for changes to the PORT table in the CONFIG_DB and APP_DB in order to handle alias/description config change. It checks if port is up or down by looking into the oper-status for in APP_DB PORT TABLE. If it cannot find it in the App DB, it will log error. During initializing, it is possible that there is a port change in CONFIG_DB and but the not ready in APP_DB. The change here is to only log error in is_port_up() after port init done.		2020-05-19 02:52:48 -07:00
..
base_image_files	[lldp]add the excutable mode for 'lldpcli' (#4385)	2020-04-07 12:49:34 -07:00
critical_processes	[Services] Restart LLDP service upon unexpected critical process exit. (#3713)	2019-11-06 11:02:57 -08:00
docker-lldp-init.sh	Changes for LLDP docker to support multi-npu platforms (#4530)	2020-05-11 11:05:44 -07:00
Dockerfile.j2	[docker-lldp-sv2]: upgrade docker-lldp-sv2 to buster (#4598)	2020-05-15 14:51:53 -07:00
lldpd	sonic-cfggen with sonicv2 dockers (#190)	2017-01-19 20:56:26 -08:00
lldpd.conf.j2	configure the hostname for lldpd	2019-02-12 09:40:51 +00:00
lldpmgrd	[lldpmgrd] only log error in is_port_up() after port init done (#4606)	2020-05-19 02:52:48 -07:00
start.sh	start lldp-syncd and lldpmgrd after lldpd fully started	2019-02-12 10:38:55 +00:00
supervisord.conf.j2	Changes for LLDP docker to support multi-npu platforms (#4530)	2020-05-11 11:05:44 -07:00