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

Allow input over 64 Chars (200 Chars needed in my case) for name fields on both VLANs and Vitulization Interfaces. #7552

New Issue
Closed
opened 2025-12-29 20:25:10 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:25:10 +01:00
Owner
Copy Link

Originally created by @jamesdio on GitHub (Jan 24, 2023).

NetBox version

v3.4.3

Feature type

Data model extension

Proposed functionality

Increase the length of the name fields on both VLANs and Vitulization Interfaces beyond the current 64 character limit (200 Chars in my case)

Use case

Those who managing SDDC with NetBox can easily recognize where the interface is attached on and what VM the interface belongs to as soon as reading the interface name which is included with distributed port group name like below

example

  • NIC Seq. (Distibuted Port Group name) (VM name)
vNIC 1 (vxw-dvs-120-virtualwire-16-sid-5020-LS-PRD-MSA-Service-192_168_201_0-24) (usw-prd-msa-lgs-01)

Database changes

I think interface name fields are located on both ipam_vlan and virtualization_vminterface tables. but I'm not confident if there are more fields to alter.

External dependencies

None

Originally created by @jamesdio on GitHub (Jan 24, 2023). ### NetBox version v3.4.3 ### Feature type Data model extension ### Proposed functionality Increase the length of the name fields on both VLANs and Vitulization Interfaces beyond the current 64 character limit (200 Chars in my case) ### Use case Those who managing SDDC with NetBox can easily recognize where the interface is attached on and what VM the interface belongs to as soon as reading the interface name which is included with distributed port group name like below ### example - `NIC Seq. (Distibuted Port Group name) (VM name)` ``` vNIC 1 (vxw-dvs-120-virtualwire-16-sid-5020-LS-PRD-MSA-Service-192_168_201_0-24) (usw-prd-msa-lgs-01) ``` ### Database changes I think interface name fields are located on both ipam_vlan and virtualization_vminterface tables. but I'm not confident if there are more fields to alter. ### External dependencies None
adam added the type: featurestatus: needs owner labels 2025-12-29 20:25:10 +01:00
adam closed this issue 2025-12-29 20:25:10 +01:00
adam commented 2025-12-29 20:25:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 25, 2023):

The 64-character limitation was initially imposed to mimic the behavior of many network operating systems, which limit the VLAN names to 64 characters natively. However, with the more recent introduction of custom validation rules, it's probably reasonable to open this up and let administrators configure a shorter length if needed.

@jeremystretch commented on GitHub (Jan 25, 2023): The 64-character limitation was initially imposed to mimic the behavior of many network operating systems, which limit the VLAN names to 64 characters natively. However, with the more recent introduction of [custom validation rules](https://docs.netbox.dev/en/stable/customization/custom-validation/), it's probably reasonable to open this up and let administrators configure a shorter length if needed.
adam commented 2025-12-29 20:25:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 25, 2023):

I should clarify that while this makes sense for VLANs, I don't agree that we should lengthen component names. In your example above, the interface name would be vNIC 1, and the other attributes should be recorded as other parameters (either in the description or as custom fields).

@jeremystretch commented on GitHub (Jan 25, 2023): I should clarify that while this makes sense for VLANs, I _don't_ agree that we should lengthen component names. In your example above, the interface name would be `vNIC 1`, and the other attributes should be recorded as other parameters (either in the description or as custom fields).
adam commented 2025-12-29 20:25:11 +01:00
Author
Owner
Copy Link

@jamesdio commented on GitHub (Jan 26, 2023):

I should clarify that while this makes sense for VLANs, I don't agree that we should lengthen component names. In your example above, the interface name would be vNIC 1, and the other attributes should be recorded as other parameters (either in the description or as custom fields).

Thanks for your suggestion. I didn't even think about using custom fields. You've given me insights.

@jamesdio commented on GitHub (Jan 26, 2023): > I should clarify that while this makes sense for VLANs, I _don't_ agree that we should lengthen component names. In your example above, the interface name would be `vNIC 1`, and the other attributes should be recorded as other parameters (either in the description or as custom fields). Thanks for your suggestion. I didn't even think about using custom fields. You've given me insights.
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 status: needs owner 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#7552
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?