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

Assign IP Interface to Virtual Chassis #10964

New Issue
Closed
opened 2025-12-29 21:38:30 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:38:30 +01:00
Owner
Copy Link

Originally created by @aroth01 on GitHub (Mar 28, 2025).

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

For the virtual chassis(stacked) switches we have, we have been creating them as individual devices per slot and then assigning them to a virtual chassis to relate them together. The device is managed by a virtual vlan interface in-band. But the ip interface can migrate between stack members if one fails.

It would be nice to potentially create a virtual interface and relate it to the virtual chassis object to be able to assign the IP address for it.

Use case

It addresses when a virtual chassis has an IP address shared between members and allows it to track the IP based on the vc as a whole instead of just one device in the stack.

Database changes

It would create a new foreign key field on virtual chassis to tie to a interface object.

External dependencies

No response

Originally created by @aroth01 on GitHub (Mar 28, 2025). ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality For the virtual chassis(stacked) switches we have, we have been creating them as individual devices per slot and then assigning them to a virtual chassis to relate them together. The device is managed by a virtual vlan interface in-band. But the ip interface can migrate between stack members if one fails. It would be nice to potentially create a virtual interface and relate it to the virtual chassis object to be able to assign the IP address for it. ### Use case It addresses when a virtual chassis has an IP address shared between members and allows it to track the IP based on the vc as a whole instead of just one device in the stack. ### Database changes It would create a new foreign key field on virtual chassis to tie to a interface object. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:38:30 +01:00
adam closed this issue 2025-12-29 21:38:31 +01:00
adam commented 2025-12-29 21:38:32 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Apr 3, 2025):

Virtual chassis management in general has surfaced a lot of suggestions like this. The current implementation does not support the proposed concept unfortunately; in order to implement it there would need to be a considerably more detailed proposal covering how exactly this would work; I would suggest moving this to a discussion to help flesh out the proposal in a way that is consistent with our data model.

For the time being it's best to just model the management IP on the master device.

@bctiemann commented on GitHub (Apr 3, 2025): Virtual chassis management in general has surfaced a lot of suggestions like this. The current implementation does not support the proposed concept unfortunately; in order to implement it there would need to be a considerably more detailed proposal covering how exactly this would work; I would suggest moving this to a discussion to help flesh out the proposal in a way that is consistent with our data model. For the time being it's best to just model the management IP on the 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#10964
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?