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

Allow MIN and MAX VLan ID in VLAN_GROUP #6141

New Issue
Closed
opened 2025-12-29 19:37:15 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:37:15 +01:00
Owner
Copy Link

Originally created by @wwerther on GitHub (Feb 24, 2022).

NetBox version

v.3.1.8

Feature type

Change to existing functionality

Proposed functionality

It would be great if VLAN groups would have optional support for a min and a max VLAN-ID. Currently when clicking on a VLAN group I always see the amount of free vlans from 1 - 4096. I would prefer to see it only in assigned boundary.
Currently I'm adding this information using two custom fields, but their value is not reflected in the view for the VLAN-group where the amount of availble VLANs is listed.

Use case

On one site we have several VLAN-blocks that we use for certain purpose. So we try to have a unique VLAN-number on a complete site (even though double usage would be in theorie possible).
E.g. one building on a site get's VLAN IDs 100 - 199, the next building 200 - 299. Also in DC we have several ranges (e.g. DMZ 1000-1200). So for each building / purpose a special range is reserved.
So it would be very beneficial to open a vlan group and only see the available VIDs within the assigned range (and mabye add a function to get the next free-VID )

Database changes

add additional column to vlan-group with min and max (defaults to 1 and 4096 when not set otherwise)

External dependencies

No response

Originally created by @wwerther on GitHub (Feb 24, 2022). ### NetBox version v.3.1.8 ### Feature type Change to existing functionality ### Proposed functionality It would be great if VLAN groups would have optional support for a min and a max VLAN-ID. Currently when clicking on a VLAN group I always see the amount of free vlans from 1 - 4096. I would prefer to see it only in assigned boundary. Currently I'm adding this information using two custom fields, but their value is not reflected in the view for the VLAN-group where the amount of availble VLANs is listed. ### Use case On one site we have several VLAN-blocks that we use for certain purpose. So we try to have a unique VLAN-number on a complete site (even though double usage would be in theorie possible). E.g. one building on a site get's VLAN IDs 100 - 199, the next building 200 - 299. Also in DC we have several ranges (e.g. DMZ 1000-1200). So for each building / purpose a special range is reserved. So it would be very beneficial to open a vlan group and only see the available VIDs within the assigned range (and mabye add a function to get the next free-VID ) ### Database changes add additional column to vlan-group with min and max (defaults to 1 and 4096 when not set otherwise) ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 19:37:15 +01:00
adam closed this issue 2025-12-29 19:37:15 +01:00
adam commented 2025-12-29 19:37:16 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Feb 24, 2022):

This is already planned in the next release: https://github.com/netbox-community/netbox/issues/8168

@hagbarddenstore commented on GitHub (Feb 24, 2022): This is already planned in the next release: https://github.com/netbox-community/netbox/issues/8168
adam commented 2025-12-29 19:37:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 24, 2022):

Yep, this has already been implemented for NetBox v3.2. You can experiment with it in the beta demo instance.

@jeremystretch commented on GitHub (Feb 24, 2022): Yep, this has already been implemented for NetBox v3.2. You can experiment with it in the [beta demo instance](https://beta-demo.netbox.dev/).
adam commented 2025-12-29 19:37:16 +01:00
Author
Owner
Copy Link

@wwerther commented on GitHub (Feb 26, 2022):

Cool :) Then we can close this request!

@wwerther commented on GitHub (Feb 26, 2022): Cool :) Then we can close this request!
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 status: duplicate 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#6141
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?