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

Full trace with splitter cable between patch panels #8664

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

Originally created by @betadrome on GitHub (Sep 22, 2023).

NetBox version

v3.6.1

Feature type

New functionality

Proposed functionality

In one scenario, a switch is connected to another switch via the passive cabling using splitting/breakout cables. The split cables are physically two cables between one patch panel and the other patch panel. Currently the NetBox sol cannot display a split, which is why the trace does not work and no connection is displayed. Currently the NetBox can only display these two physical cables as one with multi-terminations, i.e. there are two terminations on each side. However, this does not correspond to reality. Therefore I propose the change that the NetBox displays in this case both paths between the splitting cables, because the start and end point is exactly the same.
Here is a before and after picture:
netbox-trace-problem
image
The last picture shows my customization

Use case

The use case is a complete cable trace with splitting cables across multiple patch panels. This means that the end point is correctly displayed under the interface connection.

Database changes

I'm not deep enough into it, but I don't think so, since the general connection is currently already working

External dependencies

No response

Originally created by @betadrome on GitHub (Sep 22, 2023). ### NetBox version v3.6.1 ### Feature type New functionality ### Proposed functionality In one scenario, a switch is connected to another switch via the passive cabling using splitting/breakout cables. The split cables are physically two cables between one patch panel and the other patch panel. Currently the NetBox sol cannot display a split, which is why the trace does not work and no `connection` is displayed. Currently the NetBox can only display these two physical cables as one with multi-terminations, i.e. there are two terminations on each side. However, this does not correspond to reality. Therefore I propose the change that the NetBox displays in this case both paths between the splitting cables, because the start and end point is exactly the same. Here is a before and after picture: ![netbox-trace-problem](https://github.com/netbox-community/netbox/assets/110609354/3bca42a9-f18d-4bf6-bb3f-b447bf648773) ![image](https://github.com/netbox-community/netbox/assets/110609354/b9079695-ae6e-48b0-bf69-aab4a37c17c0) The last picture shows my customization ### Use case The use case is a complete cable trace with splitting cables across multiple patch panels. This means that the end point is correctly displayed under the interface connection. ### Database changes I'm not deep enough into it, but I don't think so, since the general connection is currently already working ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:39:36 +01:00
adam closed this issue 2025-12-29 20:39:36 +01:00
adam commented 2025-12-29 20:39:36 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 22, 2023):

Already covered by PR https://github.com/netbox-community/netbox/pull/13337 I believe...

@jsenecal commented on GitHub (Sep 22, 2023): Already covered by PR https://github.com/netbox-community/netbox/pull/13337 I believe...
adam commented 2025-12-29 20:39:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2023):

Yes, this should be covered under #11079, which is resolved by #13337 in the upcoming v3.6.3 release. Closing this out for now, but please feel to resubmit if you encounter issues on v3.6.3.

@jeremystretch commented on GitHub (Sep 26, 2023): Yes, this should be covered under #11079, which is resolved by #13337 in the upcoming v3.6.3 release. Closing this out for now, but please feel to resubmit if you encounter issues on v3.6.3.
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#8664
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?