Multi-ASIC support for show ip route#1060
Closed
gechiang wants to merge 2 commits intosonic-net:masterfrom
gechiang:master
Closed
Multi-ASIC support for show ip route#1060gechiang wants to merge 2 commits intosonic-net:masterfrom gechiang:master
gechiang wants to merge 2 commits intosonic-net:masterfrom
gechiang:master
Conversation
arlakshm
requested changes
Aug 27, 2020
Contributor
|
@gechiang Are you going with separate implementation for multi ASIC and single ASIC or are you going to refactor to use common code. |
…d + review update)
Contributor
Author
Yes. I have changed the code so that even pizzabox case will also use the same code processing. Originally was trying to minimize the potential impact in case this code has some bug that I was not able to shake out. Feel pretty confident about the overall changes so all will go through same code path now. |
Contributor
Author
|
Canceling this PR. Will make a new PR with the latest update instead. |
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
3 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.
Add Multi-ASIC support to handle "show ip route" on multi-ASIC devices
Depends on the following PRs
Signed-off-by: Gen-Hwa Chiang [email protected]
- What I did
Add support for multi ASIC CLI options for "show ip route"
2 new options have added
[-n, --namespace] to allow user to display the information for given namespaces (ASIC)
If this option is not present the information from all the namespaces will be displayed
[-d, --display] to allow user to display ip routes related with nexthop that are going through both internal and external interfaces
If this option is not present only ip routes with external interfaces as its nexthop will be display
On single ASIC platform, this options are not valid, so the behavior remains unchanged
- How I did it
- How to verify it
Help menu
show ip route for all routes (include routes that uses internal interface as nexthop) from ASIC0 in multi ASIC device
show ip route (exclude routes that uses internal interface as nexthop) from ASIC0 in multi ASIC device
show ip route (exclude routes that uses internal interface as nexthop) from ASIC5 in multi ASIC device in json format
show ip route (exclude routes that uses internal interface as nexthop) from ASIC5 in multi ASIC device
show ip route for all routes (exclude routes that uses internal interface as nexthop) from ALL ASICs in multi ASIC device
- 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)
** Please Note **
The test case changes will be submitted with a separate PR later so that we can take advantage of some other multi-ASIC CLI PR that have already created the test modules that can be reused without too much duplication of work.