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

BNC port and Coax cable types #2758

New Issue
Closed
opened 2025-12-29 18:21:48 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:48 +01:00
Owner
Copy Link

Originally created by @ragzilla on GitHub (Jul 23, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.1

Proposed Functionality

Patch panels and cables should support at a minimum BNC/Coaxial cables to document cross connecting T3/E3 interfaces. Currently you can create a Serial interface on a Device with an interface type of T3/E3 but there are no suitable front/rear port types to connect it to on a panel.

Use Case

Documentation of T3/E3 interconnects within a datacenter, or to external T3/E3 circuits.

Database Changes

No DB changes needed, just new enums in PORT_TYPE_CHOICES and CABLE_TYPE_CHOICES

External Dependencies

None

Originally created by @ragzilla on GitHub (Jul 23, 2019). <!-- 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.6.1 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Patch panels and cables should support at a minimum BNC/Coaxial cables to document cross connecting T3/E3 interfaces. Currently you can create a Serial interface on a Device with an interface type of T3/E3 but there are no suitable front/rear port types to connect it to on a panel. <!-- 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 Documentation of T3/E3 interconnects within a datacenter, or to external T3/E3 circuits. <!-- 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 No DB changes needed, just new enums in PORT_TYPE_CHOICES and CABLE_TYPE_CHOICES <!-- 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
adam added the status: acceptedtype: feature labels 2025-12-29 18:21:48 +01:00
adam closed this issue 2025-12-29 18:21:48 +01:00
adam commented 2025-12-29 18:21:49 +01:00
Author
Owner
Copy Link

@ragzilla commented on GitHub (Jul 23, 2019):

Proposed changes ready for pull in commit 99fc8f469b (diff-586a99dcc48544d0f3261dfe26d69972)

This does simplify the typical environment a bit by reducing the cable type to just Coax. It would more accurately represent the environments I've worked in if there were 2 cable types for 734A/735A coax, but I defaulted to keeping things simple.

@ragzilla commented on GitHub (Jul 23, 2019): Proposed changes ready for pull in commit https://github.com/ragzilla/netbox/commit/99fc8f469b40b8be53dce76422d9db64f0b0c1a1#diff-586a99dcc48544d0f3261dfe26d69972 This does simplify the typical environment a bit by reducing the cable type to just Coax. It would more accurately represent the environments I've worked in if there were 2 cable types for 734A/735A coax, but I defaulted to keeping things simple.
adam commented 2025-12-29 18:21:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 31, 2019):

Looks good to submit a PR. One note: I'd change "coax" to "coaxial" just to be technically correct.

@jeremystretch commented on GitHub (Jul 31, 2019): Looks good to submit a PR. One note: I'd change "coax" to "coaxial" just to be technically correct.
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: 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#2758
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?