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

Additional CableTypeChoices for Coaxial Cables #11588

New Issue
Closed
opened 2025-12-29 21:47:15 +01:00 by adam · 8 comments
adam commented 2025-12-29 21:47:15 +01:00
Owner
Copy Link

Originally created by @jniec-js on GitHub (Sep 8, 2025).

Originally assigned to: @jniec-js on GitHub.

NetBox version

v4.2.2

Feature type

Data model extension

Proposed functionality

Currently the CableType choices gives a breakdown for different types of cables for Ethernet and Fiber, however, for Coaxial cables it only offers one choice - "Coaxial".

The proposal is to augment the existing CableTypeChoices model (a611ade5d3/netbox/dcim/choices.py (L1541)) to include additional commonly used Coaxial Cables:

  • RG-6
  • RG-59
  • RG-62
  • RG-8
  • RG-11
  • RG-213
  • LMR-100
  • LMR-200
  • LMR-400

I am happy to contribute this feature if the proposal is accepted.

Use case

There are different features about different types of Coaxial cables that might impact how certain system configurations/parameters are derived. One such property that is particularly important to me is the signal propagation delay, this value is typically directly related to the type of coxial cable (but further defined by vendor datasheets). Either way, it is important to know the type of Coaxial cable being used, much like it is important to know the type of fiber cable being used.

Database changes

No new models are necessary as a result of this change. New entries would be added underneath the Copper section for the CableTypeChoices for some popular Coaxial cable types used in deployments.

External dependencies

n/a

Originally created by @jniec-js on GitHub (Sep 8, 2025). Originally assigned to: @jniec-js on GitHub. ### NetBox version v4.2.2 ### Feature type Data model extension ### Proposed functionality Currently the CableType choices gives a breakdown for different types of cables for Ethernet and Fiber, however, for Coaxial cables it only offers one choice - "Coaxial". The proposal is to augment the existing CableTypeChoices model (https://github.com/netbox-community/netbox/blob/a611ade5d34e50ff42161707276cc483e9f1d793/netbox/dcim/choices.py#L1541) to include additional commonly used Coaxial Cables: * RG-6 * RG-59 * RG-62 * RG-8 * RG-11 * RG-213 * LMR-100 * LMR-200 * LMR-400 I am happy to contribute this feature if the proposal is accepted. ### Use case There are different features about different types of Coaxial cables that might impact how certain system configurations/parameters are derived. One such property that is particularly important to me is the signal propagation delay, this value is typically directly related to the type of coxial cable (but further defined by vendor datasheets). Either way, it is important to know the type of Coaxial cable being used, much like it is important to know the type of fiber cable being used. ### Database changes No new models are necessary as a result of this change. New entries would be added underneath the Copper section for the CableTypeChoices for some popular Coaxial cable types used in deployments. ### External dependencies n/a
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:47:15 +01:00
adam closed this issue 2025-12-29 21:47:15 +01:00
adam commented 2025-12-29 21:47:15 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Sep 8, 2025):

If you're going to break them out like that, then you should also include the 734 and 735 types from GR-139-CORE for DS3 connections.

@sleepinggenius2 commented on GitHub (Sep 8, 2025): If you're going to break them out like that, then you should also include the 734 and 735 types from GR-139-CORE for DS3 connections.
adam commented 2025-12-29 21:47:16 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 11, 2025):

There are many different types (see: https://en.wikipedia.org/wiki/Coaxial_cable) why just these 9 types? Can you provide some examples of use cases for these different types of cables.

@arthanson commented on GitHub (Sep 11, 2025): There are many different types (see: https://en.wikipedia.org/wiki/Coaxial_cable) why just these 9 types? Can you provide some examples of use cases for these different types of cables.
adam commented 2025-12-29 21:47:16 +01:00
Author
Owner
Copy Link

@jniec-js commented on GitHub (Sep 11, 2025):

There are many different types (see: https://en.wikipedia.org/wiki/Coaxial_cable) why just these 9 types? Can you provide some examples of use cases for these different types of cables.

I tried to pick out what seemed like popular types of Coax. Alternatively, I could look into supporting adding cable types via FIELD_CHOICES if that would otherwise be preferred (currently according to the documentation, CableTypeChoices is not available to be modified via FIELD_CHOICES).

In our case, we use Coax for connectivity from Antennas to GPS appliances, tracking the type of cable is important because it affects the signal propagation delay of the received signal from Antenna to GPS appliance. Similarly, we use Coax to deliver PPS to various systems, and knowing the type of Coax cable used for deliverying PPS is important to us.

By tracking the type of cable, it would allow us to derive from our source of truth (Netbox) the amount of "delay" to add to the received signal on the GPS appliance, this delay is based off of length (which is already something tracked by Cables in Netbox) and Cable Type (the signal propagation delay is based on the type of cable). These inputs would be fed into our tooling/automation to apply the correct delay offset to our equipment.

@jniec-js commented on GitHub (Sep 11, 2025): > There are many different types (see: https://en.wikipedia.org/wiki/Coaxial_cable) why just these 9 types? Can you provide some examples of use cases for these different types of cables. I tried to pick out what seemed like popular types of Coax. Alternatively, I could look into supporting adding cable types via FIELD_CHOICES if that would otherwise be preferred (currently according to the documentation, CableTypeChoices is not available to be modified via FIELD_CHOICES). In our case, we use Coax for connectivity from Antennas to GPS appliances, tracking the type of cable is important because it affects the signal propagation delay of the received signal from Antenna to GPS appliance. Similarly, we use Coax to deliver PPS to various systems, and knowing the type of Coax cable used for deliverying PPS is important to us. By tracking the type of cable, it would allow us to derive from our source of truth (Netbox) the amount of "delay" to add to the received signal on the GPS appliance, this delay is based off of length (which is already something tracked by Cables in Netbox) and Cable Type (the signal propagation delay is based on the type of cable). These inputs would be fed into our tooling/automation to apply the correct delay offset to our equipment.
adam commented 2025-12-29 21:47:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 19, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Sep 19, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:47:16 +01:00
Author
Owner
Copy Link

@jniec-js commented on GitHub (Sep 23, 2025):

@arthanson any thoughts? The status label you added will autoclose the issue so I would like to discuss this so my request doesn't get autoclosed. I am interested in getting this type of thing added whether it be via adding additional values in the code directly or adding support for field choice extensions for CableTypes.

@jniec-js commented on GitHub (Sep 23, 2025): @arthanson any thoughts? The status label you added will autoclose the issue so I would like to discuss this so my request doesn't get autoclosed. I am interested in getting this type of thing added whether it be via adding additional values in the code directly or adding support for field choice extensions for CableTypes.
adam commented 2025-12-29 21:47:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 9, 2025):

@jniec-js opened this for an owner if you'd like to volunteer.

@jeremystretch commented on GitHub (Oct 9, 2025): @jniec-js opened this for an owner if you'd like to volunteer.
adam commented 2025-12-29 21:47:17 +01:00
Author
Owner
Copy Link

@jniec-js commented on GitHub (Oct 9, 2025):

@jniec-js opened this for an owner if you'd like to volunteer.

Thanks @jeremystretch, will happily contribute this.

Would you prefer to see this implemented as proposed/requested originally or exposing CableTypeChoices through the FIELD_CHOICES setting?

@jniec-js commented on GitHub (Oct 9, 2025): > [@jniec-js](https://github.com/jniec-js) opened this for an owner if you'd like to volunteer. Thanks @jeremystretch, will happily contribute this. Would you prefer to see this implemented as proposed/requested originally or exposing CableTypeChoices through the FIELD_CHOICES setting?
adam commented 2025-12-29 21:47:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 9, 2025):

No, cable types should not be customizable.

@jeremystretch commented on GitHub (Oct 9, 2025): No, cable types should not be customizable.
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 complexity: low netbox status: accepted 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#11588
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?