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

Feature Request: Have Virtual Chassis own control plane resources #7688

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

Originally created by @marcartz on GitHub (Feb 27, 2023).

NetBox version

v3.4.5

Feature type

Data model extension

Proposed functionality

The virtual chassis model is ideal to represent stacks of networks switches (e.g. VSS, StackWise, etc.)
Give virtual chassis the possibility to directly own control plane resources: SVIs, Management IPs and Router-Ids/Loopback-Interfaces.
Also add meta-information: site, location, vendor, type
Current options, like assigning those resources to a random stack member does badly represent the actual function of a stack: The control plane is assigned to an elected master, which could potentially be any of the available stack members (the ID of a potential master is non-deterministic).
Currently I use a fake stack member with the same name as the VC, which owns the control plane resources, while the actual stack members have only a serial number assigned.

Use case

Real-Life representation of stacks of network switches in Netbox.

Database changes

Virtual Chassis

  • Interfaces
  • IP addresses
  • Site
  • Location
  • Vendor
  • Type

External dependencies

No response

Originally created by @marcartz on GitHub (Feb 27, 2023). ### NetBox version v3.4.5 ### Feature type Data model extension ### Proposed functionality The virtual chassis model is ideal to represent stacks of networks switches (e.g. VSS, StackWise, etc.) Give virtual chassis the possibility to directly own control plane resources: SVIs, Management IPs and Router-Ids/Loopback-Interfaces. Also add meta-information: site, location, vendor, type Current options, like assigning those resources to a random stack member does badly represent the actual function of a stack: The control plane is assigned to an elected master, which could potentially be any of the available stack members (the ID of a potential master is non-deterministic). Currently I use a fake stack member with the same name as the VC, which owns the control plane resources, while the actual stack members have only a serial number assigned. ### Use case Real-Life representation of stacks of network switches in Netbox. ### Database changes # Virtual Chassis - Interfaces - IP addresses - Site - Location - Vendor - Type ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:27:00 +01:00
adam closed this issue 2025-12-29 20:27:00 +01:00
adam commented 2025-12-29 20:27:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 27, 2023):

Current options, like assigning those resources to a random stack member does badly represent the actual function of a stack

The current implementation most closely mirrors the way a stack actually functions: The master device is responsible for operation of the control plane. I'm sorry if the was this is implemented in NetBox does not meet your needs, but we will not be changing it.

@jeremystretch commented on GitHub (Feb 27, 2023): > Current options, like assigning those resources to a random stack member does badly represent the actual function of a stack The current implementation most closely mirrors the way a stack actually functions: The master device is responsible for operation of the control plane. I'm sorry if the was this is implemented in NetBox does not meet your needs, but we will not be changing it.
adam commented 2025-12-29 20:27:01 +01:00
Author
Owner
Copy Link

@marcartz commented on GitHub (Feb 27, 2023):

Thanks Jeremy, that was by no means meant as criticism. I really appreciate your incredible work with NetBox.
Using a fake placeholder device is a viable workaround to represent an actual switch stack.
I was just trying to point out that in actual real-world stacking implementations logical interfaces are not tied to any particular physical device but rather dynamically handed over to whatever device takes over the control plane.

@marcartz commented on GitHub (Feb 27, 2023): Thanks Jeremy, that was by no means meant as criticism. I really appreciate your incredible work with NetBox. Using a fake placeholder device is a viable workaround to represent an actual switch stack. I was just trying to point out that in actual real-world stacking implementations logical interfaces are not tied to any particular physical device but rather dynamically handed over to whatever device takes over the control plane.
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#7688
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?