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 VLANs to Devices #4894

New Issue
Closed
opened 2025-12-29 19:21:45 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:21:45 +01:00
Owner
Copy Link

Originally created by @avidpontoon on GitHub (May 10, 2021).

NetBox version

v2.11.3

Feature type

Data model extension

Proposed functionality

Within each Device, you should be able to assign VLANs to it. Much like you can do on an interface. Allowing you to track which devices have which VLANs on them. This should then be displayed somewhere within the 'Device' tab to view at a glance.

Use case

Allowing users to immediately know if a certain device already has a specified VLAN on it or if it needs adding. Could also mean that when you go to assign VLANs to interfaces on a specific device, it only shows VLANs that are configured on that specific device. This could help with accidentally assigning a VLAN that isn't on the device.

Database changes

New VLAN ID's field would be required for devices.

External dependencies

None

Originally created by @avidpontoon on GitHub (May 10, 2021). ### NetBox version v2.11.3 ### Feature type Data model extension ### Proposed functionality Within each Device, you should be able to assign VLANs to it. Much like you can do on an interface. Allowing you to track which devices have which VLANs on them. This should then be displayed somewhere within the 'Device' tab to view at a glance. ### Use case Allowing users to immediately know if a certain device already has a specified VLAN on it or if it needs adding. Could also mean that when you go to assign VLANs to interfaces on a specific device, it only shows VLANs that are configured on that specific device. This could help with accidentally assigning a VLAN that isn't on the device. ### Database changes New VLAN ID's field would be required for devices. ### External dependencies None
adam added the type: feature label 2025-12-29 19:21:45 +01:00
adam closed this issue 2025-12-29 19:21:45 +01:00
adam commented 2025-12-29 19:21:45 +01:00
Author
Owner
Copy Link

@romanstech commented on GitHub (May 10, 2021):

Agree with this request. Yesterday started thinking where I can save such info on each switch in Netbox.

@romanstech commented on GitHub (May 10, 2021): Agree with this request. Yesterday started thinking where I can save such info on each switch in Netbox.
adam commented 2025-12-29 19:21:46 +01:00
Author
Owner
Copy Link

@TheNetworkGuy commented on GitHub (May 11, 2021):

Do not agree with this feature request. VLAN's are interface specific, not device specific.

Besides you can look at the interface overview to see all assigned VLAN's to all interfaces, call the API for a list of VLAN's etc.

@TheNetworkGuy commented on GitHub (May 11, 2021): Do not agree with this feature request. VLAN's are interface specific, not device specific. Besides you can look at the interface overview to see all assigned VLAN's to all interfaces, call the API for a list of VLAN's etc.
adam commented 2025-12-29 19:21:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2021):

VLANs are difficult to model effectively. While we do "create" VLANs on switches, what we're really doing is partitioning the L2 forwarding table into discrete domains. In reality, VLANs are really link-specific. For example, I can create subinterfaces Gi0/0.100 and Gi0/1.100 both using 802.1Q encapsulation tagged for VLAN 100, but these aren't necessarily in the same VLAN.

Also, NetBox v2.11 introduced the available_on_device and available_on_virtualmachine filters which largely obviate the need for the direct assignment proposed here.

@jeremystretch commented on GitHub (May 11, 2021): VLANs are difficult to model effectively. While we do "create" VLANs on switches, what we're really doing is partitioning the L2 forwarding table into discrete domains. In reality, VLANs are really link-specific. For example, I can create subinterfaces Gi0/0.100 and Gi0/1.100 both using 802.1Q encapsulation tagged for VLAN 100, but these aren't necessarily in the same VLAN. Also, NetBox v2.11 introduced the `available_on_device` and `available_on_virtualmachine` filters which largely obviate the need for the direct assignment proposed here.
adam commented 2025-12-29 19:21:46 +01:00
Author
Owner
Copy Link

@avidpontoon commented on GitHub (May 11, 2021):

Hi Jeremy,

Is there any documentation on the available_on_device addition?

Thanks
Nick

@avidpontoon commented on GitHub (May 11, 2021): Hi Jeremy, Is there any documentation on the available_on_device addition? Thanks Nick
adam commented 2025-12-29 19:21:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 12, 2021):

It's listed as an available filter in the REST API docs, but that's about it.

@jeremystretch commented on GitHub (May 12, 2021): It's listed as an available filter in the REST API docs, but that's about it.
adam commented 2025-12-29 19:21:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 12, 2021):

I'm going to go ahead and close this as it would only serve to complicate the data model at this point.

@jeremystretch commented on GitHub (May 12, 2021): I'm going to go ahead and close this as it would only serve to complicate the data model at this point.
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#4894
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?