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

Change of Vlan Group Scope to Add DCIM -> Device #6194

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

Originally created by @cruse1977 on GitHub (Mar 10, 2022).

NetBox version

v3.2

Feature type

Change to existing functionality

Proposed functionality

In IP Fabrics, vlan relevance is often solely to a single leaf device, with vxlan (VNI) taking over beyond that device - however its currently not possible to assign a vlan group to a device.

This proposal would add DCIM -> Device to the Scope types of vlan groups

Use case

Allowing a vlan group to be assigned on a device level would allow a IP fabrics to be further documented within netbox.

Database changes

.

External dependencies

.

Originally created by @cruse1977 on GitHub (Mar 10, 2022). ### NetBox version v3.2 ### Feature type Change to existing functionality ### Proposed functionality In IP Fabrics, vlan relevance is often solely to a single leaf device, with vxlan (VNI) taking over beyond that device - however its currently not possible to assign a vlan group to a device. This proposal would add DCIM -> Device to the Scope types of vlan groups ### Use case Allowing a vlan group to be assigned on a device level would allow a IP fabrics to be further documented within netbox. ### Database changes . ### External dependencies .
adam added the type: feature label 2025-12-29 19:37:54 +01:00
adam closed this issue 2025-12-29 19:37:54 +01:00
adam commented 2025-12-29 19:37:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2022):

This might be something to look at once we explore VXLAN/VNI modeling, but it doesn't make sense given the current data model.

@jeremystretch commented on GitHub (Mar 30, 2022): This might be something to look at once we explore VXLAN/VNI modeling, but it doesn't make sense given the current data model.
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#6194
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?