pimd: MSDP logging improvements #17469
Merged
Conversation
This file contains 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
|
I think it is good to expand an existing msdp test to at least exercise the new CLI commands, get some test coverage |
Move MSDP neighbor events global debug to per PIM instance. Signed-off-by: Rafael Zalamena <[email protected]>
Add new command to log all SA events. Signed-off-by: Rafael Zalamena <[email protected]>
Test MSDP new log toggle: the MSDP peer connection state and SA events should be logged. Signed-off-by: Rafael Zalamena <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Promote some debug logs to informational and put them behind configuration knobs per PIM instance.
This design is similar to BGP's
bgp log-neighbor-changes.