-
Notifications
You must be signed in to change notification settings - Fork 2.7k
LLDP Virtual-Chassis Neighbor #5049
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
Comments
My question would be, can we be sure 100% of the time that the virtual chassis name would be the neighbor name? |
We are using VC with Juniper devices. Here I configure hostname which is valid for the complete VC. I don't know if there are any options to name a single member of VC. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide. |
So will this now be closed without further activity? Thought @DanSheps will takeover as he was assigned. |
Sorry, this was something I was going to work on and just haven't had time yet. I will get working on it shortly. |
Environment
Proposed Functionality
When doing a LLDP query in the frontend on a device connected to a virtual-chassis, the LLDP neighbor is shown as the specific member of the virtual-chassis. NetBox 2.9 now has a virtual-chassis name. It would be nice to use the virtual-chassis name instead of the member name here.
Use Case
Use the new Virtual-Chassis member name and have the LLDP neighbors correctly shown.
Database Changes
none
External Dependencies
none
The text was updated successfully, but these errors were encountered: