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

Add MRJ21 as port type as well as MRJ21 cable assembly as cable type #3412

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

Originally created by @marktizzard on GitHub (Feb 26, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.7

Proposed Functionality

Add additional port type of "MRJ21" port for pre-terminated cable deployments as well as addition cable type of 'MRJ21 cable assembly' for connection between MRJ21 ports.

Use Case

This would aid users who currently use modular components to build data center infrastructure, rather than traditional individual cable pulls with standard terminations for copper cabling (Cat5e\Cat6\Cat6a). For example we employ the use of pre-terminated MRJ21 cable assemblies in pre-determined lengths to be able to add capacity on the fly without a cabling tech to perform terminations of tradition category cabling. While the configuration described can be modeled using existing cable types and connectors within the tool, the ability to denote the difference between pre-terminated vs traditional terminated cable would be useful in the tool.

Included device drawings as an example of what the system looks like:

Cable assembly:
https://www.commscope.com/globalassets/digizuite/43343-2111439-c-pdf.pdf

Cassette with 6 8P8C front and 1 MRJ21 rear:
https://www.commscope.com/globalassets/digizuite/42255-1479459-c-pdf.pdf

However just the addition of the MRJ21 connector would allow these and other similar devices to be modeled by the end user.

Database Changes

Not entirely sure - I suspect it is just an addition of another cable and connector type the list of existing types. I am not familiar with the relationships between types and connectors and if that would change database relationships or schemas.

External Dependencies

None

Originally created by @marktizzard on GitHub (Feb 26, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.8 * NetBox version: 2.7.7 ### Proposed Functionality Add additional port type of "MRJ21" port for pre-terminated cable deployments as well as addition cable type of 'MRJ21 cable assembly' for connection between MRJ21 ports. ### Use Case This would aid users who currently use modular components to build data center infrastructure, rather than traditional individual cable pulls with standard terminations for copper cabling (Cat5e\Cat6\Cat6a). For example we employ the use of pre-terminated MRJ21 cable assemblies in pre-determined lengths to be able to add capacity on the fly without a cabling tech to perform terminations of tradition category cabling. While the configuration described can be modeled using existing cable types and connectors within the tool, the ability to denote the difference between pre-terminated vs traditional terminated cable would be useful in the tool. Included device drawings as an example of what the system looks like: Cable assembly: https://www.commscope.com/globalassets/digizuite/43343-2111439-c-pdf.pdf Cassette with 6 8P8C front and 1 MRJ21 rear: https://www.commscope.com/globalassets/digizuite/42255-1479459-c-pdf.pdf However just the addition of the MRJ21 connector would allow these and other similar devices to be modeled by the end user. ### Database Changes Not entirely sure - I suspect it is just an addition of another cable and connector type the list of existing types. I am not familiar with the relationships between types and connectors and if that would change database relationships or schemas. ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:28:51 +01:00
adam closed this issue 2025-12-29 18:28:51 +01:00
adam commented 2025-12-29 18:28:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 26, 2020):

What's the canonical name for the cable itself? "MRJ21 Trunk" would probably work but should we stick to something more generic?

@jeremystretch commented on GitHub (Feb 26, 2020): What's the canonical name for the cable itself? "MRJ21 Trunk" would probably work but should we stick to something more generic?
adam commented 2025-12-29 18:28:52 +01:00
Author
Owner
Copy Link

@marktizzard commented on GitHub (Feb 27, 2020):

"MRJ21 Trunk" would be best here - this would be the most generic way to describe this cable assembly type amongst different vendors. The canonical name would be "MRJ21 Cable Assembly" - which could mean different things depending on the termination and\or breakouts, so in this application trunk makes most sense as it is a trunk in data networking terms.

@marktizzard commented on GitHub (Feb 27, 2020): "MRJ21 Trunk" would be best here - this would be the most generic way to describe this cable assembly type amongst different vendors. The canonical name would be "MRJ21 Cable Assembly" - which could mean different things depending on the termination and\or breakouts, so in this application trunk makes most sense as it is a trunk in data networking terms.
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#3412
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?