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 groups - add an option for "excluded" vlan id's to Child VLANs setting #6326

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

Originally created by @ITJamie on GitHub (Apr 8, 2022).

NetBox version

v3.2.0

Feature type

Change to existing functionality

Proposed functionality

add a third field, to contain a list of comma seperated vlan id's that should be skipped / not allowed in a vlan group.
add logic so that vlan isnt accepted into the group and not offered as the "next available vlan"

Use case

there are some vlan id's we would not like to be shown as "available" for certain vlan groups. (eg ciscos pre-resevered vlans 1002 – 1005 )

other examples may be that a certain vlan was in use long before that "range" was assigned a use and needs to be excluded from the list of "available" vlans

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Apr 8, 2022). ### NetBox version v3.2.0 ### Feature type Change to existing functionality ### Proposed functionality add a third field, to contain a list of comma seperated vlan id's that should be skipped / not allowed in a vlan group. add logic so that vlan isnt accepted into the group and not offered as the "next available vlan" ### Use case there are some vlan id's we would not like to be shown as "available" for certain vlan groups. (eg ciscos pre-resevered vlans 1002 – 1005 ) other examples may be that a certain vlan was in use long before that "range" was assigned a use and needs to be excluded from the list of "available" vlans ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:39:26 +01:00
adam closed this issue 2025-12-29 19:39:27 +01:00
adam commented 2025-12-29 19:39:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 1, 2022):

I'm going to close this in favor of #9627, which seeks to provide the same functionality, but moves the model to a single ArrayField defining valid VLAN IDs.

@jeremystretch commented on GitHub (Jul 1, 2022): I'm going to close this in favor of #9627, which seeks to provide the same functionality, but moves the model to a single ArrayField defining valid VLAN IDs.
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#6326
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?