-
Notifications
You must be signed in to change notification settings - Fork 710
[show] Enhance show interface status command output #597
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
base: master
Are you sure you want to change the base?
Conversation
my concern is that if there's something cabling/configuration issue, the real fact does not align with the information in the configuration database. Then the output will be misleading. |
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.
As comments, plus please replace instances of "neighbour" with the American English spelling, "neighbor".
Ethernet0 49,50,51,52 100G 9100 hundredGigE1/1 down up N/A off | ||
Ethernet4 53,54,55,56 100G 9100 hundredGigE1/2 down up N/A off | ||
Ethernet8 57,58,59,60 100G 9100 hundredGigE1/3 down down N/A off | ||
Interface Lanes Speed MTU Alias Vlan Oper Admin Type Asym PFC Neighbour Port |
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.
This output is not displaying properly in the rendered Markdown. Please fix.
Agree @stcheng . However I thought we can compare this output with |
@prsunny agree. i would recommend some components in LLDP docker could write the current neighbors into the database. that would be a useful piece of information. |
retest this please |
- What I did
I have added neighbour device and neighbour device's port info output at the end of the "show interface status" command. Resolved comments from Previous PR :
https://github.com/Azure/sonic-utilities/pull/590
which was closed due to merge conflict issues- How I did it
I did this by getting the neighbour info from the CONFIG DB
- How to verify it
Verified using the lab test machine
- 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)