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

Virtual Chassis - Add all interfaces under VC from all members #7562

New Issue
Closed
opened 2025-12-29 20:25:28 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:25:28 +01:00
Owner
Copy Link

Originally created by @PVM-NL on GitHub (Jan 26, 2023).

NetBox version

v3.3.9

Feature type

New functionality

Proposed functionality

From deku-m discussion:
As i see value in this. But can be that its not accepted ofcourse.
For now the individual switches that are member of a VC are getting all the interfaces from the members as well.
Wondering how the idea is on a Virtual Chassis as now we create the chassis and add the members under it.

Looking at how Cisco models their "stacking switches" you notice that they also create some sort of virtual switch with all members under them and when asking, "show interfaces" the numbering is like 1/0/1-1/0/2, 2/0/1, 2/0/2. While you cant acces the underlaying second or third switch. Because it reachable by primary/master only by console. Physically they are still separated switches of course.

Isnt it an idea to add all interfaces combined under a tab in virtual chassis and let the members have their own interfaces like now? Most beautiful thing would be that, it will also create the interfaces like for example Cisco does.
But i can imagine this isnt possible or to hard to implement.

Mock up:
image

Use case

Overview of all interfaces immediatly under Virtual Chassis instead of adding them to the physical device from other devices (switch 1/2/3/4)

Database changes

Dont know?

External dependencies

None?

Originally created by @PVM-NL on GitHub (Jan 26, 2023). ### NetBox version v3.3.9 ### Feature type New functionality ### Proposed functionality **From deku-m discussion:** As i see value in this. But can be that its not accepted ofcourse. For now the individual switches that are member of a VC are getting all the interfaces from the members as well. Wondering how the idea is on a Virtual Chassis as now we create the chassis and add the members under it. Looking at how Cisco models their "stacking switches" you notice that they also create some sort of virtual switch with all members under them and when asking, "show interfaces" the numbering is like 1/0/1-1/0/2, 2/0/1, 2/0/2. While you cant acces the underlaying second or third switch. Because it reachable by primary/master only by console. Physically they are still separated switches of course. Isnt it an idea to add all interfaces combined under a tab in virtual chassis and let the members have their own interfaces like now? Most beautiful thing would be that, it will also create the interfaces like for example Cisco does. But i can imagine this isnt possible or to hard to implement. **Mock up:** ![image](https://user-images.githubusercontent.com/120473446/214821441-9f6559e4-e731-4a6e-b5b0-9f54bd94efa7.png) ### Use case Overview of all interfaces immediatly under Virtual Chassis instead of adding them to the physical device from other devices (switch 1/2/3/4) ### Database changes Dont know? ### External dependencies None?
adam added the type: feature label 2025-12-29 20:25:28 +01:00
adam closed this issue 2025-12-29 20:25:28 +01:00
adam commented 2025-12-29 20:25:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2023):

You need to designate one of the switches as the master for the virtual chassis. All member interfaces will then appear on that switch.

@jeremystretch commented on GitHub (Jan 26, 2023): You need to designate one of the switches as the [master for the virtual chassis](https://docs.netbox.dev/en/stable/models/dcim/virtualchassis/). All member interfaces will then appear on that switch.
adam commented 2025-12-29 20:25:29 +01:00
Author
Owner
Copy Link

@PVM-NL commented on GitHub (Jan 26, 2023):

You need to designate one of the switches as the master for the virtual chassis. All member interfaces will then appear on that switch.

I know that the member(master) gets the interfaces (of all switches) but i was just thinking of having those interfaces as extentions on the VC overview as well. Like the mockup. So that we dont have to click through the member then to their interfaces but just see all combined interfaces in VC aswell.

@PVM-NL commented on GitHub (Jan 26, 2023): > You need to designate one of the switches as the [master for the virtual chassis](https://docs.netbox.dev/en/stable/models/dcim/virtualchassis/). All member interfaces will then appear on that switch. I know that the member(master) gets the interfaces (of all switches) but i was just thinking of having those interfaces as extentions on the VC overview as well. Like the mockup. So that we dont have to click through the member then to their interfaces but just see all combined interfaces in VC aswell.
adam commented 2025-12-29 20:25:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2023):

This would be completely redundant to viewing the master device. (And not just interfaces; all components would need to be replicated.)

@jeremystretch commented on GitHub (Jan 26, 2023): This would be completely redundant to viewing the master device. (And not just interfaces; _all_ components would need to be replicated.)
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 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#7562
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?