starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 19:48:25 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:48:25 +01:00
Owner
Copy Link

Originally created by @Clarebout on GitHub (Sep 30, 2022).

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

Originally created by @Clarebout on GitHub (Sep 30, 2022). ### 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](https://github.com/netbox-community/netbox/issues/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](https://user-images.githubusercontent.com/68003793/193271452-733a74f1-7047-4adb-ae48-d5ec82e333b5.png) Regards, Kevin ### Use case being able to read lldp neighbors from stacked switches ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:48:25 +01:00
adam closed this issue 2025-12-29 19:48:25 +01:00
adam commented 2025-12-29 19:48:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (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[bot] commented on GitHub (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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:48:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (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[bot] commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7054
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?