-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[show] add new CLI to show tunnel route objects #2255
Conversation
I tent to disagree with this change. First of all, |
Hi Prince - Yes |
This pull request introduces 1 alert when merging 6609452 into c7389bd - view on LGTM.com new alerts:
|
6609452
to
599215b
Compare
599215b
to
86a9ba3
Compare
Agree, but was there an issue observed in transition that a tunnel route is not removed? I mean in active-active, there should not be any tunnel route. Just want to understand the motivation. |
There wasn't an issue like that. But |
aa7a2f8
to
df94706
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Update sonic-utilities submodule pointer to include the following: * [show] add new CLI to show tunnel route objects ([sonic-net#2255](sonic-net/sonic-utilities#2255)) * Add support for IP interface loopback action ([sonic-net#2192](sonic-net/sonic-utilities#2192)) * Update load minigraph to load backend acl ([sonic-net#2236](sonic-net/sonic-utilities#2236)) * show linkmgrd status in ([sonic-net#2254](sonic-net/sonic-utilities#2254)) Signed-off-by: dprital <drorp@nvidia.com>
What I did Add new CLI support to show tunnel route objects in ASIC DB. sign-off: Jing Zhang zhangjing@microsoft.com How I did it Check if tunnel route object exists for server_ipv4, server_ipv6, soc_ipv4. If existing, print it out. If not specifying port name, print all tunnel route objects. How to verify it Added unit tests. Tested on dual testbed.
This commit could not be cleanly cherry-picked to 202012. Please submit another PR. |
What I did Add new CLI support to show tunnel route objects in ASIC DB. sign-off: Jing Zhang zhangjing@microsoft.com How I did it Check if tunnel route object exists for server_ipv4, server_ipv6, soc_ipv4. If existing, print it out. If not specifying port name, print all tunnel route objects. How to verify it Added unit tests. Tested on dual testbed.
What I did Add new CLI support to show tunnel route objects in APP DB. sign-off: Jing Zhang zhangjing@microsoft.com How I did it Check if tunnel route object exists for server_ipv4, server_ipv6. If existing, print it out. If not specifying port name, print all tunnel route objects. How to verify it Added unit tests. Tested on dual testbeds: show mux tunnel-route Ethernet140 PORT DEST_TYPE DEST_ADDRESS ----------- ----------- --------------- Ethernet140 server_ipv4 192.168.0.29/32 show mux tunnel-route --json Ethernet140 { "TUNNEL_ROUTE": { "Ethernet140": { "server_ipv4": { "DEST": "192.168.0.29/32" } } } }
Cherry-pick PR merged: #2659 |
What I did
Add new CLI support to show tunnel route objects in ASIC DB.
sign-off: Jing Zhang zhangjing@microsoft.com
How I did it
How to verify it
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)