[dbsycnd] update submodule head of dbsyncd#5916
Merged
lguohan merged 1 commit intosonic-net:masterfrom Nov 13, 2020
Merged
Conversation
[lldp daemon] improve lldp daemon event when neighbor capability is not sent (sonic-net#30) Signed-off-by: Ying Xie <ying.xie@microsoft.com>
lguohan
approved these changes
Nov 12, 2020
santhosh-kt
pushed a commit
to santhosh-kt/sonic-buildimage
that referenced
this pull request
Feb 25, 2021
[lldp daemon] improve lldp daemon event when neighbor capability is not sent (sonic-net#30) Signed-off-by: Ying Xie <ying.xie@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
- Why I did it
To fix issue #5912
- How I did it
[lldp daemon] improve lldp daemon event when neighbor capability is not sent (#30)
Signed-off-by: Ying Xie ying.xie@microsoft.com
- How to verify it
Copied daemon.py to an DUT subject to the issue. Restart lldp service, and validated that the log message came out as INFO level and with expected contents.