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

Extend VLAN Group scoping to Devices and Virtual Chassis #9093

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

Originally created by @dago158 on GitHub (Jan 16, 2024).

NetBox version

v3.6.4

Feature type

Data model extension

Proposed functionality

Extended to enable scoping of VLAN Groups to DCIM > Devices an DCIM > Virtual Chassis

Use case

Actually, VLAN Group scoping is currently limited to clusters (virtualization) or locations (DCIM).

In Layer 3 leaf-spine networks configurations include access VLAN networks that are specific to spines,wether individual switches or switches pair (MLAG).

It's not possible to properly link the information between the VLANs / VLAN Group and devices that way,
as there can be multiple VLANs with same ID at the same site/location/rack but on different devices.

Database changes

None

External dependencies

None

Originally created by @dago158 on GitHub (Jan 16, 2024). ### NetBox version v3.6.4 ### Feature type Data model extension ### Proposed functionality Extended to enable scoping of VLAN Groups to DCIM > Devices an DCIM > Virtual Chassis ### Use case Actually, VLAN Group scoping is currently limited to clusters (virtualization) or locations (DCIM). In Layer 3 leaf-spine networks configurations include access VLAN networks that are specific to spines,wether individual switches or switches pair (MLAG). It's not possible to properly link the information between the VLANs / VLAN Group and devices that way, as there can be multiple VLANs with same ID at the same site/location/rack but on different devices. ### Database changes None ### External dependencies None
adam added the type: featurepending closurestatus: under reviewcomplexity: medium labels 2025-12-29 20:45:20 +01:00
adam closed this issue 2025-12-29 20:45:20 +01:00
adam commented 2025-12-29 20:45:21 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 3, 2024):

Thanks for your interest in helping improve NetBox. I'm moving this issue along for engineering review, because I'm not sure whether this work can be done within an existing release train. It may need to be scheduled out for a minor release boundary.

@jeffgdotorg commented on GitHub (Apr 3, 2024): Thanks for your interest in helping improve NetBox. I'm moving this issue along for engineering review, because I'm not sure whether this work can be done within an existing release train. It may need to be scheduled out for a minor release boundary.
adam commented 2025-12-29 20:45:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 28, 2024):

It sounds like what you're really after is probably captured by #14451.

@jeremystretch commented on GitHub (May 28, 2024): It sounds like what you're really after is probably captured by #14451.
adam commented 2025-12-29 20:45:21 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 27, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 27, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:45:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 27, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 27, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 complexity: medium pending closure status: under review 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#9093
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?