'config bgp [shutdown|startup] neighbor <hostname>' now affects all sessions for neighbor #195
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.
- What I did
Previously, if multiple BGP sessions existed for a neighbor (e.g., an IPv4 session and an IPv6 session), calling
config bgp shutdown neighbor <hostname>
would only shut down the first session it located in ConfigDB. This PR will now cause the command to shut down all BGP sessions associated with that neighbor. (The same is true ofconfig bgp startup neighbor <hostname>
)Also fix a bug where passing
config bgp [shutdown|startup] neighbor <ip_address>
would fail to locate a neighbor with that IP address if the IP address passed was an IPv6 address containing lowercase alphabet characters. IPv6 addresses are stored in ConfigDB with all uppercase alphabet characters and the lookup is case-sensitive. Now converting all IP addresses to uppercase before performing ConfigDB operations with them.- Previous command output (if the output of a command-line utility has changed)
- New command output (if the output of a command-line utility has changed)