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

Manage switch stack and port channels #6522

New Issue
Closed
opened 2025-12-29 19:41:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:41:56 +01:00
Owner
Copy Link

Originally created by @michal-staniszewski on GitHub (May 30, 2022).

NetBox version

v3.2.3

Feature type

Change to existing functionality

Proposed functionality

Hi
Today to create a switch stack we can use "Virtual Chassis". It has no functionality apart from documenting that few devices are building up a stack of switches. It does not provide any function regarding naming and managing switch ports and port channels.
I suggest to extend it with interfaces section that takes all interfaces from contained switches and also to allow creation of MLAG port channels. Second option could be to have a device type called "Switch Stack" that would be able to groups several physical switches and allow also to manage all interfaces and create MLAG port channels.
Thanks in advance for consideration.

Use case

Better manage logical switch that represents a stack comprised from physical switches, to allow management of all stack interfaces and also MLAG port channels from one place

Database changes

??

External dependencies

Originally created by @michal-staniszewski on GitHub (May 30, 2022). ### NetBox version v3.2.3 ### Feature type Change to existing functionality ### Proposed functionality Hi Today to create a switch stack we can use "Virtual Chassis". It has no functionality apart from documenting that few devices are building up a stack of switches. It does not provide any function regarding naming and managing switch ports and port channels. I suggest to extend it with interfaces section that takes all interfaces from contained switches and also to allow creation of MLAG port channels. Second option could be to have a device type called "Switch Stack" that would be able to groups several physical switches and allow also to manage all interfaces and create MLAG port channels. Thanks in advance for consideration. ### Use case Better manage logical switch that represents a stack comprised from physical switches, to allow management of all stack interfaces and also MLAG port channels from one place ### Database changes ?? ### External dependencies -
adam added the type: feature label 2025-12-29 19:41:56 +01:00
adam closed this issue 2025-12-29 19:41:56 +01:00
adam commented 2025-12-29 19:41:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 31, 2022):

I suggest to extend it with interfaces section that takes all interfaces from contained switches and also to allow creation of MLAG port channels.

I'm afraid this has already been discussed and we settled on the current implementation. The solution is to assign any "shared" interfaces to the virtual chassis master device.

@jeremystretch commented on GitHub (May 31, 2022): > I suggest to extend it with interfaces section that takes all interfaces from contained switches and also to allow creation of MLAG port channels. I'm afraid this has already been discussed and we settled on the current implementation. The solution is to assign any "shared" interfaces to the virtual chassis master device.
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#6522
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?