Toggle "allow duplicate vlans" in each group #2665

Closed
opened 2025-12-29 18:21:01 +01:00 by adam · 2 comments
Owner

Originally created by @clinta on GitHub (Jun 13, 2019).

Environment

  • Python version: 3.6.7
  • NetBox version: v2.5.14-dev

Proposed Functionality

Allow each VLAN group to have a boolean indicating whether or not to enforce uniqueness.

Use Case

I am using VLANs to track VXLAN overlays with a custom field for VXLAN ID. I'd like to create a VLAN group for my VXLANs, but all the VXLANs have the same VLAN ID so this is not possible.

Originally created by @clinta on GitHub (Jun 13, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.7 * NetBox version: v2.5.14-dev <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Allow each VLAN group to have a boolean indicating whether or not to enforce uniqueness. <!-- 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 I am using VLANs to track VXLAN overlays with a custom field for VXLAN ID. I'd like to create a VLAN group for my VXLANs, but all the VXLANs have the same VLAN ID so this is not possible.
adam closed this issue 2025-12-29 18:21:01 +01:00
Author
Owner

@clinta commented on GitHub (Jun 13, 2019):

Perhaps a VLAN role is more appropriate for this, so maybe this isn't necessary.

@clinta commented on GitHub (Jun 13, 2019): Perhaps a VLAN role is more appropriate for this, so maybe this isn't necessary.
Author
Owner

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

VLAN groups were added primarily to enforce uniqueness among member VLANs. Role/site assignment and tags can also be used for organization as you note.

@jeremystretch commented on GitHub (Jun 14, 2019): VLAN groups were added primarily to enforce uniqueness among member VLANs. Role/site assignment and tags can also be used for organization as you note.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2665