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

Voice VLAN Assignment to Access Port #1825

New Issue
Closed
opened 2025-12-29 17:19:32 +01:00 by adam · 4 comments
adam commented 2025-12-29 17:19:32 +01:00
Owner
Copy Link

Originally created by @DanSheps on GitHub (Jul 3, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Environment

  • Python version: 3.5.4
  • NetBox version: 2.4.0-devel

Description

In using netbox, one thing I have noticed is there isn't a way to assign a vlan to an access port for "voice". I am not sure if this is something that is desired by everyone and may be a fairly niche request. I think the best way to do it would be to continue to use the VLAN assignment interface and add a separate option for voice vlan. The relationship may need to be edited to allow tagging a single vlan when using access ports.

Use Case

Use for documenting access ports where there phones or other media devices

Database Schema Changes

Allow tagging a single port on access ports, in addition to the untagged port.

Originally created by @DanSheps on GitHub (Jul 3, 2018). ### Issue type [X] Feature request [ ] Bug report [ ] Documentation [ ] Housekeeping ### Environment * Python version: 3.5.4 * NetBox version: 2.4.0-devel ### Description In using netbox, one thing I have noticed is there isn't a way to assign a vlan to an access port for "voice". I am not sure if this is something that is desired by everyone and may be a fairly niche request. I think the best way to do it would be to continue to use the VLAN assignment interface and add a separate option for voice vlan. The relationship may need to be edited to allow tagging a single vlan when using access ports. #### Use Case Use for documenting access ports where there phones or other media devices #### Database Schema Changes Allow tagging a single port on access ports, in addition to the untagged port.
adam closed this issue 2025-12-29 17:19:33 +01:00
adam commented 2025-12-29 17:19:33 +01:00
Author
Owner
Copy Link

@larsuhartmann commented on GitHub (Jul 3, 2018):

This would be really nice as it would allow to use netbox for campus access switchs.

@larsuhartmann commented on GitHub (Jul 3, 2018): This would be really nice as it would allow to use netbox for campus access switchs.
adam commented 2025-12-29 17:19:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 5, 2018):

NetBox already supports assigning tagged and untagged VLANs to interfaces. There's nothing special about a "voice" VLAN; it's just a shortcut configuration used to add a single tagged VLAN to an interface that's normally untagged. For example, this configuration:

switchport mode access
switchport access vlan 100
switchport voice vlan 200

would be modeled in NetBox as VLAN 100 untagged and VLAN 200 tagged.

@jeremystretch commented on GitHub (Jul 5, 2018): NetBox already supports assigning tagged and untagged VLANs to interfaces. There's nothing special about a "voice" VLAN; it's just a shortcut configuration used to add a single tagged VLAN to an interface that's normally untagged. For example, this configuration: ``` switchport mode access switchport access vlan 100 switchport voice vlan 200 ``` would be modeled in NetBox as VLAN 100 untagged and VLAN 200 tagged.
adam commented 2025-12-29 17:19:34 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jul 5, 2018):

There's nothing special about a "voice" VLAN; it's just a shortcut configuration used to add a single tagged VLAN to an interface that's normally untagged.

That's not true on all platforms. For example, in Juniper land, the switch will use LLDP to identify phones and place them on a specified VLAN.

That said, I do agree this does not need to be added to NetBox because such configuration is normally device-wide and thus can be accommodated with a custom field on the device (this is how I do this today). I comment, only to offer this solution to anyone looking for this feature in the future.

@lampwins commented on GitHub (Jul 5, 2018): > There's nothing special about a "voice" VLAN; it's just a shortcut configuration used to add a single tagged VLAN to an interface that's normally untagged. That's not true on all platforms. For example, in Juniper land, the switch will use LLDP to identify phones and place them on a specified VLAN. That said, I do agree this does not need to be added to NetBox because such configuration is normally device-wide and thus can be accommodated with a custom field on the device (this is how I do this today). I comment, only to offer this solution to anyone looking for this feature in the future.
adam commented 2025-12-29 17:19:34 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 10, 2018):

I guess I wasn't 100% clear, my thinking/problem is that when it is assigned as an access interface in Netbox, you can only assign one vlan to the interface.

This is one of the checks you perform when saving the vlans. Adding a new mode that lets you untagged a single vlan and tag a single vlan would be the workaround. If I can work it out myself, I can do a PR for it, the only thing is making sure it doesn't break anything else.

@DanSheps commented on GitHub (Jul 10, 2018): I guess I wasn't 100% clear, my thinking/problem is that when it is assigned as an access interface in Netbox, you can only assign one vlan to the interface. This is one of the checks you perform when saving the vlans. Adding a new mode that lets you untagged a single vlan and tag a single vlan would be the workaround. If I can work it out myself, I can do a PR for it, the only thing is making sure it doesn't break anything else.
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
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#1825
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?