Skip to content

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

Closed
tobzsc opened this issue Aug 25, 2020 · 6 comments
Closed

LLDP Virtual-Chassis Neighbor #5049

tobzsc opened this issue Aug 25, 2020 · 6 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@tobzsc
Copy link

tobzsc commented Aug 25, 2020

Environment

  • Python version: 3.6.8
  • NetBox version: 2.9.1

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.

LLDP Neighbor VC

Use Case

Use the new Virtual-Chassis member name and have the LLDP neighbors correctly shown.

Database Changes

none

External Dependencies

none

@DanSheps DanSheps added status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application labels Aug 27, 2020
@DanSheps
Copy link
Member

My question would be, can we be sure 100% of the time that the virtual chassis name would be the neighbor name?

@tobzsc
Copy link
Author

tobzsc commented Aug 28, 2020

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.

@dotpy88
Copy link

dotpy88 commented Sep 20, 2020

I just ran across this same issue. Using virtual chassis for Cisco stackwise, LLDP neighbor is showing the virtual chassis name and not the device name so you get the RED row indicating something is different.

image

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Oct 13, 2020
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: accepted This issue has been accepted for implementation labels Nov 17, 2020
@stale
Copy link

stale bot commented Jan 1, 2021

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.

@stale stale bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jan 1, 2021
@tobzsc
Copy link
Author

tobzsc commented Jan 5, 2021

So will this now be closed without further activity? Thought @DanSheps will takeover as he was assigned.

@stale stale bot removed the pending closure Requires immediate attention to avoid being closed for inactivity label Jan 5, 2021
@DanSheps
Copy link
Member

DanSheps commented Jan 5, 2021

Sorry, this was something I was going to work on and just haven't had time yet. I will get working on it shortly.

@DanSheps DanSheps added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jan 5, 2021
@DanSheps DanSheps self-assigned this Jan 5, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants