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

VLAN Pool and ranges support #2661

New Issue
Closed
opened 2025-12-29 18:20:59 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:20:59 +01:00
Owner
Copy Link

Originally created by @eddiehaug on GitHub (Jun 9, 2019).

Proposed Functionality

In the VLAN ID Field, allow to select whether it's a single VLAN or a VLAN Pool. Using a parent-child relationship, we could have a single VLAN Pool with one or more VLANs or VLAN Ranges.

  1. Logic change: Single or Pool
  2. If Single -> Enter ID
  3. If Pool -> Enter Pool Name -> Add ranges

Use Case

In Cisco's SDN solution, ACI, and I guess in other SDN solutions as well, it's possible to create VLAN Pools, which contain either static or dynamic VLAN allocations using VLAN ranges. Being able to document this would be really helpful in order to properly plan the VLAN allocations, specially in multi-tenant environments.

chapter-10-vlan-pool

Database Changes

Add Pool Name Column
Add Ranges Column
Create relationship between Pool Names and Ranges

External Dependencies

None

Originally created by @eddiehaug on GitHub (Jun 9, 2019). ### Proposed Functionality In the VLAN ID Field, allow to select whether it's a single VLAN or a VLAN Pool. Using a parent-child relationship, we could have a single VLAN Pool with one or more VLANs or VLAN Ranges. 1) Logic change: Single or Pool 2) If Single -> Enter ID 3) If Pool -> Enter Pool Name -> Add ranges <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case In Cisco's SDN solution, ACI, and I guess in other SDN solutions as well, it's possible to create VLAN Pools, which contain either static or dynamic VLAN allocations using VLAN ranges. Being able to document this would be really helpful in order to properly plan the VLAN allocations, specially in multi-tenant environments. ![chapter-10-vlan-pool](https://user-images.githubusercontent.com/13933303/59159340-891d4580-8ac8-11e9-8782-fd0b5329e30a.png) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Add Pool Name Column Add Ranges Column Create relationship between Pool Names and Ranges <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 18:20:59 +01:00
adam commented 2025-12-29 18:20:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 20, 2019):

The NetBox data model requires each VLAN to be modeled independently. We are unable to deviate from this model for many reasons.

@jeremystretch commented on GitHub (Jun 20, 2019): The NetBox data model requires each VLAN to be modeled independently. We are unable to deviate from this model for many reasons.
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
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#2661
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?