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 a Many:Many connection device #2215

New Issue
Closed
opened 2025-12-29 17:23:40 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:23:40 +01:00
Owner
Copy Link

Originally created by @millijuna on GitHub (Dec 14, 2018).

Environment

  • Python version: 3.6.5
  • NetBox version: 2.5.1

Proposed Functionality

It would be very helpful for capturing my campus network configuration to be able to document my Many:Many splice enclosures. Conceptually, the idea would be akin to connecting rear ports to each other.

Related: when dealing with rear ports, it would be great to have a "Fusion Splice" connector type.

Use Case

In my campus network, I have a significant quantity of OSP (OutSide Plant) cable that comes into our main administration building. Due to fire regulations (OSP cable is only permitted 50' inside a structure), and due to mechanical constraints, that OSP cable goes into a splice enclosure in the basement.

Inside the enclosure is a series of splicing cassettes that each take two OSP cables (6 SMF strands) and splice them onto a riser cable that has 12 strands.

Another use case for this would be other situations where you're transitioning from one cable to another, with a change in designation/color/other property, or peeling a fiber pair off of a trunk cable.

Database Changes

Could possibly need some relaxation of constraints to permit rear ports to be connected to each other.

External Dependencies

Originally created by @millijuna on GitHub (Dec 14, 2018). <!-- 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.5 * NetBox version: 2.5.1 ### Proposed Functionality It would be very helpful for capturing my campus network configuration to be able to document my Many:Many splice enclosures. Conceptually, the idea would be akin to connecting rear ports to each other. Related: when dealing with rear ports, it would be great to have a "Fusion Splice" connector type. <!-- 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 In my campus network, I have a significant quantity of OSP (OutSide Plant) cable that comes into our main administration building. Due to fire regulations (OSP cable is only permitted 50' inside a structure), and due to mechanical constraints, that OSP cable goes into a splice enclosure in the basement. Inside the enclosure is a series of splicing cassettes that each take two OSP cables (6 SMF strands) and splice them onto a riser cable that has 12 strands. Another use case for this would be other situations where you're transitioning from one cable to another, with a change in designation/color/other property, or peeling a fiber pair off of a trunk cable. <!-- 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 Could possibly need some relaxation of constraints to permit rear ports to be connected to each other. ### External Dependencies
adam closed this issue 2025-12-29 17:23:40 +01:00
adam commented 2025-12-29 17:23:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2018):

Unfortunately the data model we've implemented for cabling doesn't support directly splicing one cable to another. It's important to remember that the data model we decided on during the v2.5 beta period was chosen because it strikes a reasonable balance between flexibility, performance, and maintainability.

In your case, I'd probably create a device to represent the splicing enclosure, with the cables terminated as rear ports and "patched" together via front ports. You should be able to model this with a single device. Alternatively, you could model one or both cables continuing for the entire span, with the understanding that it doesn't fully reflect reality.

@jeremystretch commented on GitHub (Dec 14, 2018): Unfortunately the data model we've implemented for cabling doesn't support directly splicing one cable to another. It's important to remember that the data model we decided on during the v2.5 beta period was chosen because it strikes a reasonable balance between flexibility, performance, and maintainability. In your case, I'd probably create a device to represent the splicing enclosure, with the cables terminated as rear ports and "patched" together via front ports. You should be able to model this with a single device. Alternatively, you could model one or both cables continuing for the entire span, with the understanding that it doesn't fully reflect reality.
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#2215
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?