Skip to content

LLDP with stacked members in virtual chassis --> use virtual chassis name instead of the member name #10518

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
Clarebout opened this issue Sep 30, 2022 · 2 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application

Comments

@Clarebout
Copy link

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

Hi,

I have a similar issue as LLDP Virtual-Chassis Neighbor #5049
It's marked as resolved and fixed. But I have this same problem.

python version: 3.8.10
netbox version 3.4.4

I have configured multiple switches that are stacked. Hostname of the switch is CLF-CLIENTSWITCH201. Names in netbox are CLF-CLIENTSWITCH201 #1, CLF-CLIENTSWITCH201 #2.

I created a virtual chassis named CLF-CLIENTSWITCH201 and made #1 and #2 members. With member 1 as master.

When clicking on lldp neighbors, i get the lldp devices and interfaces, but when i look at the connection between the switches i see as lldp device CLF-CLIENTSWITCH201 and in netbox it is connected to CLF-CLIENTSWITCH201 #2
Which gives as result that those are different.

Is there a way, to let netbox use the name of the virtual chassis in the lldp screen (if one exists) instead of the device name?

image

Regards, Kevin

Use case

being able to read lldp neighbors from stacked switches

Database changes

No response

External dependencies

No response

@Clarebout Clarebout added the type: feature Introduction of new functionality to the application label Sep 30, 2022
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Oct 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2022

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Dec 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2023

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

1 participant