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

Increase maximum cable segment length #3242

New Issue
Closed
opened 2025-12-29 18:27:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:27:02 +01:00
Owner
Copy Link

Originally created by @agebel on GitHub (Jan 29, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.2

Proposed Functionality

Increase maximum length of a given cable segment to facilitate recording inter-site connections, backhaul runs, etc.

Use Case

Currently, the maximum length for a given cable segment is 32767 meters. This creates difficulty when documenting cable runs (e.g. fiber connections) connecting sites more than 33 km apart. Network operators, those leasing dark fiber point-to-point connections, etc would benefit from being able to document longer connections.

Database Changes

I'm still learning Django, so can't say for sure, but I think perhaps simply changing the cable model's length field from 'length', models.PositiveSmallIntegerField to
'length', models.PositiveIntegerField would suffice as it would allow for 2B+ meter runs at a maximum cost of just 2 bytes per instance.

Perhaps it would make sense to update the field so that a validator is used to limit the length to a rational maximum.

If accepted, I would be more than happy to attempt to implement any recommended/desired changes and submit any necessary pull requests.

External Dependencies

None (that I can tell)

Originally created by @agebel on GitHub (Jan 29, 2020). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.7.2 ### Proposed Functionality Increase maximum length of a given cable segment to facilitate recording inter-site connections, backhaul runs, etc. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Currently, the maximum length for a given cable segment is 32767 meters. This creates difficulty when documenting cable runs (e.g. fiber connections) connecting sites more than 33 km apart. Network operators, those leasing dark fiber point-to-point connections, etc would benefit from being able to document longer connections. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes I'm still learning Django, so can't say for sure, but I think perhaps simply changing the cable model's _length_ field from `'length', models.PositiveSmallIntegerField` to `'length', models.PositiveIntegerField` would suffice as it would allow for 2B+ meter runs at a maximum cost of just 2 bytes per instance. Perhaps it would make sense to update the field so that a validator is used to limit the length to a rational maximum. If accepted, I would be more than happy to attempt to implement any recommended/desired changes and submit any necessary pull requests. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None (that I can tell)
adam closed this issue 2025-12-29 18:27:02 +01:00
adam commented 2025-12-29 18:27:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2020):

Cables are intended to represent contiguous physical connections between two points. To represent a long-haul communications circuit, use the circuit model.

@jeremystretch commented on GitHub (Jan 29, 2020): Cables are intended to represent contiguous physical connections between two points. To represent a long-haul communications circuit, use the circuit model.
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#3242
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?