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 description #268

New Issue
Closed
opened 2025-12-29 16:20:23 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:20:23 +01:00
Owner
Copy Link

Originally created by @andreas1o on GitHub (Jul 22, 2016).

Hi would it be possible to add a description field to vlan ?
In some switches you tend to use vlanmanes more than tags so name becomes very significant and vlanid is something you configure once.
Then a description added to the vlan would make sense ?

Originally created by @andreas1o on GitHub (Jul 22, 2016). Hi would it be possible to add a description field to vlan ? In some switches you tend to use vlanmanes more than tags so name becomes very significant and vlanid is something you configure once. Then a description added to the vlan would make sense ?
adam added the type: feature label 2025-12-29 16:20:23 +01:00
adam closed this issue 2025-12-29 16:20:23 +01:00
adam commented 2025-12-29 16:20:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 22, 2016):

I think a description field would be redundant since VLANs already have a name. There isn't usually much other context that needs to be provided around a VLAN. Can you provide a specific use case where a description would provide additional information not conveyed by the name?

@jeremystretch commented on GitHub (Jul 22, 2016): I think a description field would be redundant since VLANs already have a name. There isn't usually much other context that needs to be provided around a VLAN. Can you provide a specific use case where a description would provide additional information not conveyed by the name?
adam commented 2025-12-29 16:20:24 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jul 22, 2016):

I think @andreas1o is just asking for this given some platforms (JUNOS) allow for their config of a vlanid, name, and description separately.

@ryanmerolle commented on GitHub (Jul 22, 2016): I think @andreas1o is just asking for this given some platforms (JUNOS) allow for their config of a vlanid, name, and description separately.
adam commented 2025-12-29 16:20:24 +01:00
Author
Owner
Copy Link

@andreas1o commented on GitHub (Jul 22, 2016):

yes exactly vlanname is usually limited in the lenght but descriptions are not.
For instans vlan id 100 name FINANCIALSERVICE - description Financial Service EastCoast
vlan id 101 name FINANCIALSERVICE - description Financial Service Westcoast.

@andreas1o commented on GitHub (Jul 22, 2016): yes exactly vlanname is usually limited in the lenght but descriptions are not. For instans vlan id 100 name FINANCIALSERVICE - description Financial Service EastCoast vlan id 101 name FINANCIALSERVICE - description Financial Service Westcoast.
adam commented 2025-12-29 16:20:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 25, 2016):

Added a description to the VLAN model in d241cce.

@jeremystretch commented on GitHub (Jul 25, 2016): Added a description to the VLAN model in d241cce.
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#268
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?