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 Cable Types #7280

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

Originally created by @mstoop71 on GitHub (Nov 24, 2022).

NetBox version

v3.3.7

Feature type

Data model extension

Proposed functionality

Add on Connection types for the interfaces:

  • HDMI (Normal, Mini)
  • DisplayPort (DP) (Normal, Mini)
  • USB-A (Version 1, 2, 3.0, 3.1, 3.2)
  • USB-B (Version 1, 2, 3.0, 3.1, 3.2)
  • USB-C (Version 1, 2, 3.0, 3.1, 3.2)
  • HDBaseT (RJ45)
  • XLR
  • Mini-XLR
  • Terminalblock (3pin, 4pin & 5pin)

Use case

In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment (e.g. Matrix Switchers, HDMI Encoders, Decoders, Videowall processors, Audio DSP's etc).
When adding the additional porttypes to the Database devices can more accurately reflect the connectivity options within a single rack but can also start to map out connectivity within e.g. meetingrooms largely extending the use of Netbox. We are currently piloting this at a University where the connectivity options widely vary (Adding displays with HDMI, touchplays with USB, Cameras with USB-c, PC's with HDMI and/or Displayport, etc.).
Having these additions (or even better the option to add our own port types) Netbox suddenly becomes a relevant tool in the AV but also Video Surveillance industry (Cameras also have lots of additional connection types (e.g. SDI in different types).

Database changes

Probably no database changes are required as within the "Physical Media Classification" it just requires the additional options.

External dependencies

No response

Originally created by @mstoop71 on GitHub (Nov 24, 2022). ### NetBox version v3.3.7 ### Feature type Data model extension ### Proposed functionality Add on Connection types for the interfaces: - HDMI (Normal, Mini) - DisplayPort (DP) (Normal, Mini) - USB-A (Version 1, 2, 3.0, 3.1, 3.2) - USB-B (Version 1, 2, 3.0, 3.1, 3.2) - USB-C (Version 1, 2, 3.0, 3.1, 3.2) - HDBaseT (RJ45) - XLR - Mini-XLR - Terminalblock (3pin, 4pin & 5pin) ### Use case In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment (e.g. Matrix Switchers, HDMI Encoders, Decoders, Videowall processors, Audio DSP's etc). When adding the additional porttypes to the Database devices can more accurately reflect the connectivity options within a single rack but can also start to map out connectivity within e.g. meetingrooms largely extending the use of Netbox. We are currently piloting this at a University where the connectivity options widely vary (Adding displays with HDMI, touchplays with USB, Cameras with USB-c, PC's with HDMI and/or Displayport, etc.). Having these additions (or even better the option to add our own port types) Netbox suddenly becomes a relevant tool in the AV but also Video Surveillance industry (Cameras also have lots of additional connection types (e.g. SDI in different types). ### Database changes Probably no database changes are required as within the "Physical Media Classification" it just requires the additional options. ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:21:10 +01:00
adam closed this issue 2025-12-29 20:21:10 +01:00
adam commented 2025-12-29 20:21:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 28, 2022):

In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment

As has been discussed in numerous other issues, A/V equipment management is out of scope for NetBox.

@jeremystretch commented on GitHub (Nov 28, 2022): > In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment As has been discussed in numerous other issues, A/V equipment management is out of scope for NetBox.
adam commented 2025-12-29 20:21:11 +01:00
Author
Owner
Copy Link

@mstoop71 commented on GitHub (Nov 28, 2022):

Dear Jeremy,

thanks for the response. I'm sorry to hear this though as adding a few additional cable types would hugely increase the potential usecase and accuracy for this. I currently work with the Cable type other and I can efficiently create rooms filled with camera's in custom brackets connecting through USB etc. Adding a few names would make it more accurate whilst it is not doing anything to the structure of the database. Whether I would have an OC-1 or OC-99, an Cat6a or Cat9Z cable should be arbitrary. Yet to anyone working in equipment rooms it would be a huge help.

In any real environment the IT rooms are not just equipped with Network switches and servers, there are KVM consoles (which use VGA or HDMI and PS2 or USB ) there are Mountable displays, etc. etc.

Either way I do appreciate the response and consideration but I think you should reconsider the possibilities you would create and the potential extra audience you would gain access to.

I'm happy to discuss and elaborate if required,

Kind regards,

Micha van der Stoop
+31622493696

From: Jeremy Stretch @.>
Sent: 28 November 2022 14:16
To: netbox-community/netbox @.>
Cc: Micha van der Stoop @.>; Author @.>
Subject: Re: [netbox-community/netbox] Additional Cable Types (Issue #11019)

In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment

As has been discussed in numerous other issues, A/V equipment management is out of scope for NetBox.

—
Reply to this email directly, view it on GitHubhttps://github.com/netbox-community/netbox/issues/11019#issuecomment-1329075547, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJFJRYMT5NZMA54TNLFEA4TWKSWD3ANCNFSM6AAAAAASKHETUM.
You are receiving this because you authored the thread.Message ID: @.***>

@mstoop71 commented on GitHub (Nov 28, 2022): Dear Jeremy, thanks for the response. I'm sorry to hear this though as adding a few additional cable types would hugely increase the potential usecase and accuracy for this. I currently work with the Cable type other and I can efficiently create rooms filled with camera's in custom brackets connecting through USB etc. Adding a few names would make it more accurate whilst it is not doing anything to the structure of the database. Whether I would have an OC-1 or OC-99, an Cat6a or Cat9Z cable should be arbitrary. Yet to anyone working in equipment rooms it would be a huge help. In any real environment the IT rooms are not just equipped with Network switches and servers, there are KVM consoles (which use VGA or HDMI and PS2 or USB ) there are Mountable displays, etc. etc. Either way I do appreciate the response and consideration but I think you should reconsider the possibilities you would create and the potential extra audience you would gain access to. I'm happy to discuss and elaborate if required, Kind regards, Micha van der Stoop +31622493696 ________________________________ From: Jeremy Stretch ***@***.***> Sent: 28 November 2022 14:16 To: netbox-community/netbox ***@***.***> Cc: Micha van der Stoop ***@***.***>; Author ***@***.***> Subject: Re: [netbox-community/netbox] Additional Cable Types (Issue #11019) In the current age a lot of MERs and SERs are also equipped with AudioVisual equipment As has been discussed in numerous other issues, A/V equipment management is out of scope for NetBox. — Reply to this email directly, view it on GitHub<https://github.com/netbox-community/netbox/issues/11019#issuecomment-1329075547>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJFJRYMT5NZMA54TNLFEA4TWKSWD3ANCNFSM6AAAAAASKHETUM>. You are receiving this because you authored the thread.Message ID: ***@***.***>
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: duplicate 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#7280
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?