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

Add VLAN and VLAN Group to Config Context Form #9423

New Issue
Open
opened 2025-12-29 20:49:36 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:49:36 +01:00
Owner
Copy Link

Originally created by @i3D-RyanHamel on GitHub (Apr 2, 2024).

NetBox version

3.3.10

Feature type

Data model extension

Proposed functionality

Add VLAN and VLAN group fields to the Config Context creation form, to narrow down the scope of where overrides or specific configuration need to be, and not worth adding custom metadata fields to VLANs.

Use case

For my employer, it would provide more granularity in enforcing specific limitations on VLANs like IPv6 neighbor limits, VXLAN MAC IP table limits (Junos bug), for customers that have a history of abusing and taking up TCAM on a router.

The idea here is using NetBox as a UI to allow engineers to write up a set of rules for our Ansible automation to take into consideration, allowing the automation team to write a framework once in processing these rules, instead of writing edge cases into various Jinja templates or playbooks.

Database changes

Requires adding VLAN and VLAN Group fields.

External dependencies

No response

Originally created by @i3D-RyanHamel on GitHub (Apr 2, 2024). ### NetBox version 3.3.10 ### Feature type Data model extension ### Proposed functionality Add VLAN and VLAN group fields to the Config Context creation form, to narrow down the scope of where overrides or specific configuration need to be, and not worth adding custom metadata fields to VLANs. ### Use case For my employer, it would provide more granularity in enforcing specific limitations on VLANs like IPv6 neighbor limits, VXLAN MAC IP table limits (Junos bug), for customers that have a history of abusing and taking up TCAM on a router. The idea here is using NetBox as a UI to allow engineers to write up a set of rules for our Ansible automation to take into consideration, allowing the automation team to write a framework once in processing these rules, instead of writing edge cases into various Jinja templates or playbooks. ### Database changes Requires adding VLAN and VLAN Group fields. ### External dependencies _No response_
adam added the type: featurestatus: blockednetbox labels 2025-12-29 20:49:36 +01:00
adam commented 2025-12-29 20:49:36 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 17, 2024):

This might be blocked by #14451, depending on specifics around implementation as there is nothing currently directly linking a device to a vlan. You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device.

@DanSheps commented on GitHub (Apr 17, 2024): This might be blocked by #14451, depending on specifics around implementation as there is nothing currently directly linking a device to a vlan. You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device.
adam commented 2025-12-29 20:49:37 +01:00
Author
Owner
Copy Link

@i3D-RyanHamel commented on GitHub (Apr 17, 2024):

You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device.

For my environment, it would be limited to a cluster and device role ("Core Router" for example) which would shrink the scope quite significantly.

@i3D-RyanHamel commented on GitHub (Apr 17, 2024): > You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device. For my environment, it would be limited to a cluster and device role ("Core Router" for example) which would shrink the scope quite significantly.
adam commented 2025-12-29 20:49:37 +01:00
Author
Owner
Copy Link

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

Blocked by #14451

@jeremystretch commented on GitHub (May 21, 2024): Blocked by #14451
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 netbox status: blocked 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#9423
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?