starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow a cable to be connected to multiple devices #8688

New Issue
Closed
opened 2025-12-29 20:39:54 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:39:54 +01:00
Owner
Copy Link

Originally created by @cpmills1975 on GitHub (Sep 28, 2023).

NetBox version

v3.6.3

Feature type

Change to existing functionality

Proposed functionality

I can see that it is possible to connect a cable from the A end to multiple components on a single B end device, but it does not appear to be possible to model a cable that is connected to a single component on multiple B end devices.

Use case

Break-out cables are frequently used to 'break out' a multi-channeled interface in to separate channels, sometimes across several devices. e.g. there is no reason why a 40G QSFP interface cannot be connected to a single 10G SFP interface on four different downstream devices.

I've managed to model this by traversing a patch panel with four front ports and four rear ports such that the four downstream devices have one-to-one cables going in to the rear port and the QSFP is connected to the four front ports on the patch panel, but I cannot connect the QSFP port directly to the four SFP ports.

Database changes

Presumably none - the cable end point references a single component, the fact those components can't be on different devices feels like a UI issue.

External dependencies

None

Originally created by @cpmills1975 on GitHub (Sep 28, 2023). ### NetBox version v3.6.3 ### Feature type Change to existing functionality ### Proposed functionality I can see that it is possible to connect a cable from the A end to multiple components on a single B end device, but it does not appear to be possible to model a cable that is connected to a single component on multiple B end devices. ### Use case Break-out cables are frequently used to 'break out' a multi-channeled interface in to separate channels, sometimes across several devices. e.g. there is no reason why a 40G QSFP interface cannot be connected to a single 10G SFP interface on four different downstream devices. I've managed to model this by traversing a patch panel with four front ports and four rear ports such that the four downstream devices have one-to-one cables going in to the rear port and the QSFP is connected to the four front ports on the patch panel, but I cannot connect the QSFP port directly to the four SFP ports. ### Database changes Presumably none - the cable end point references a single component, the fact those components can't be on different devices feels like a UI issue. ### External dependencies None
adam added the type: feature label 2025-12-29 20:39:54 +01:00
adam closed this issue 2025-12-29 20:39:55 +01:00
adam commented 2025-12-29 20:39:55 +01:00
Author
Owner
Copy Link

@craized commented on GitHub (Sep 28, 2023):

If I'm understanding correctly, I second this. I've been waiting for quite a while for the fixes that came with https://github.com/netbox-community/netbox/pull/13337 and am excited to see them released.

The above fix CAN cover this use case, however it was determined that it wasn't part of the bug fix, but rather a feature request (as stated here: https://github.com/netbox-community/netbox/pull/13337/files#r1295124404).

On my own instance, I've resolved this to test by commenting out the following lines https://github.com/netbox-community/netbox/blob/develop/netbox/dcim/models/cables.py#L521-L525. I assume this is a naive implementation and it may break something else.

I'm including the trace from my modeled span both as a PoC and to clarify the use case. Note that this is only half of the cable trace, and the other side would be the exact mirror.

split-cable-trace

@craized commented on GitHub (Sep 28, 2023): If I'm understanding correctly, I second this. I've been waiting for quite a while for the fixes that came with https://github.com/netbox-community/netbox/pull/13337 and am excited to see them released. The above fix CAN cover this use case, however it was determined that it wasn't part of the bug fix, but rather a feature request (as stated here: https://github.com/netbox-community/netbox/pull/13337/files#r1295124404). On my own instance, I've resolved this to test by commenting out the following lines https://github.com/netbox-community/netbox/blob/develop/netbox/dcim/models/cables.py#L521-L525. I assume this is a naive implementation and it may break something else. I'm including the trace from my modeled span both as a PoC and to clarify the use case. Note that this is only half of the cable trace, and the other side would be the exact mirror. ![split-cable-trace](https://github.com/netbox-community/netbox/assets/499818/6dac0370-3cbf-4df1-a4d3-e985cc3d1f40)
adam commented 2025-12-29 20:39:55 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Oct 4, 2023):

Isn't his already possible ??
I tried it on the demo instance, and there you can connect one port to multiple devices.
image

Steps

  • create a new connection
  • select a device, and an interface
  • the interface becomes a 'label'
  • select another device, and an interface
  • a second interface is show in the list

image

I do agree that the EDIT UI is not very intuitive nor showing enough details for these kind of cables.
The cable view does show all the devices and interfaces :
image

@PieterL75 commented on GitHub (Oct 4, 2023): Isn't his already possible ?? I tried it on the demo instance, and there you can connect one port to multiple devices. ![image](https://github.com/netbox-community/netbox/assets/74899468/6bf1b31b-07c9-465c-9139-b1c98e90f2f4) Steps - create a new connection - select a device, and an interface - the interface becomes a 'label' - select another device, and an interface - a second interface is show in the list ![image](https://github.com/netbox-community/netbox/assets/74899468/bb346fdf-8d65-48dc-8c92-a8fe9a391ddd) I do agree that the EDIT UI is not very intuitive nor showing enough details for these kind of cables. The cable view does show all the devices and interfaces : ![image](https://github.com/netbox-community/netbox/assets/74899468/7d9f980d-12e0-4327-9c5f-ce95c9f658b5)
adam commented 2025-12-29 20:39:55 +01:00
Author
Owner
Copy Link

@craized commented on GitHub (Oct 4, 2023):

Interfaces connected to multiple devices are fine (and have been since multi termination was introduced
iirc).
The failure mode comes from connecting to front ports on a device that map to more than one rear port, which in turn connect to multiple devices.

On Wed, Oct 4, 2023, 1:56 AM PieterL75 @.***> wrote:

Isn't his already possible ??
I tried it on the demo instance, and there you can connect one port to
multiple devices.
[image: image]
https://user-images.githubusercontent.com/74899468/272518176-6bf1b31b-07c9-465c-9139-b1c98e90f2f4.png

Steps

  • create a new connection
  • select a device, and an interface
  • the interface becomes a 'label'
  • select another device, and an interface
  • a second interface is show in the list

[image: image]
https://user-images.githubusercontent.com/74899468/272518614-bb346fdf-8d65-48dc-8c92-a8fe9a391ddd.png

I do agree that the EDIT UI is not very intuitive nor showing enough
details for these kind of cables.
The cable view does show all the devices and interfaces :
[image: image]
https://user-images.githubusercontent.com/74899468/272518917-7d9f980d-12e0-4327-9c5f-ce95c9f658b5.png

—
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/13923#issuecomment-1746435104,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD2A2RHZMDIQS3Z6KA7Z3DX5UQE7AVCNFSM6AAAAAA5KCISSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGQZTKMJQGQ
.
You are receiving this because you commented.Message ID:
@.***>

@craized commented on GitHub (Oct 4, 2023): Interfaces connected to multiple devices are fine (and have been since multi termination was introduced iirc). The failure mode comes from connecting to front ports on a device that map to more than one rear port, which in turn connect to multiple devices. On Wed, Oct 4, 2023, 1:56 AM PieterL75 ***@***.***> wrote: > Isn't his already possible ?? > I tried it on the demo instance, and there you can connect one port to > multiple devices. > [image: image] > <https://user-images.githubusercontent.com/74899468/272518176-6bf1b31b-07c9-465c-9139-b1c98e90f2f4.png> > > Steps > > - create a new connection > - select a device, and an interface > - the interface becomes a 'label' > - select another device, and an interface > - a second interface is show in the list > > [image: image] > <https://user-images.githubusercontent.com/74899468/272518614-bb346fdf-8d65-48dc-8c92-a8fe9a391ddd.png> > > I do agree that the EDIT UI is not very intuitive nor showing enough > details for these kind of cables. > The cable view does show all the devices and interfaces : > [image: image] > <https://user-images.githubusercontent.com/74899468/272518917-7d9f980d-12e0-4327-9c5f-ce95c9f658b5.png> > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/13923#issuecomment-1746435104>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAD2A2RHZMDIQS3Z6KA7Z3DX5UQE7AVCNFSM6AAAAAA5KCISSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGQZTKMJQGQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
adam commented 2025-12-29 20:39:56 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 4, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 4, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:39:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 12, 2024):

Closing this out as the requested functionality already exists, per @PieterL75's comment above. If there's some other requirement not surfaced here, please submit a new FR detailing it.

@jeremystretch commented on GitHub (Mar 12, 2024): Closing this out as the requested functionality already exists, per @PieterL75's comment [above](https://github.com/netbox-community/netbox/issues/13923#issuecomment-1746435104). If there's some other requirement not surfaced here, please submit a new FR detailing it.
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 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#8688
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?