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

Multiple connections cable trace fails with multiple hops #6977

New Issue
Closed
opened 2025-12-29 19:47:23 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:47:23 +01:00
Owner
Copy Link

Originally created by @CupcakeMunster on GitHub (Sep 13, 2022).

NetBox version

v3.3.2

Python version

3.8

Steps to Reproduce

1.Create 2 devices with SFP interfaces
2.Connect those devices to patch panel devices in a 1 SFP to 2 POS relationship. Related to issue #9102

162635585-91e99e13-cde7-4cbe-84fc-301d827ff206

  1. Create 1 more hop in the path via another patch panel device and connect both devices together using the patch panels.

Expected Behavior

Cable trace functions all the way through and show the endpoint device.

Untitled Diagram drawio

Observed Behavior

Split path detected at fiber patch panel Building 2. If I use only one position instead of the 1 SFP to 2 positions relationship then cable trace functions all the way through.

Originally created by @CupcakeMunster on GitHub (Sep 13, 2022). ### NetBox version v3.3.2 ### Python version 3.8 ### Steps to Reproduce 1.Create 2 devices with SFP interfaces 2.Connect those devices to patch panel devices in a 1 SFP to 2 POS relationship. Related to issue #9102 ![162635585-91e99e13-cde7-4cbe-84fc-301d827ff206](https://user-images.githubusercontent.com/26608204/189928060-f34ed831-e14f-4853-8e56-2a5161d7f1a1.png) 3. Create 1 more hop in the path via another patch panel device and connect both devices together using the patch panels. ### Expected Behavior Cable trace functions all the way through and show the endpoint device. ![Untitled Diagram drawio](https://user-images.githubusercontent.com/26608204/189927218-5c15b051-2402-42fa-9871-dd54b6b79b98.svg) ### Observed Behavior Split path detected at fiber patch panel Building 2. If I use only one position instead of the 1 SFP to 2 positions relationship then cable trace functions all the way through.
adam closed this issue 2025-12-29 19:47:23 +01:00
adam commented 2025-12-29 19:47:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2022):

Split path detected at fiber patch panel Building 2

This is expected behavior: At this point in the path, there is a split to two different cables, and we cannot support tracing any further. (Although it looks very clean in this scenario, consider that the cables may never reconverge if connected differently.) This was identified and accepted as a limitation during work on #9102.

You're welcome to submit a feature request suggesting this as a new capability, however it would require a very detailed technical implementation proposal to be considered.

@jeremystretch commented on GitHub (Sep 13, 2022): > Split path detected at fiber patch panel Building 2 This is expected behavior: At this point in the path, there is a split to two different cables, and we cannot support tracing any further. (Although it looks very clean in this scenario, consider that the cables may never reconverge if connected differently.) This was identified and accepted as a limitation during work on #9102. You're welcome to submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) suggesting this as a new capability, however it would require a very detailed technical implementation proposal to be considered.
adam commented 2025-12-29 19:47:24 +01:00
Author
Owner
Copy Link

@CupcakeMunster commented on GitHub (Sep 13, 2022):

Split path detected at fiber patch panel Building 2

This is expected behavior: At this point in the path, there is a split to two different cables, and we cannot support tracing any further. (Although it looks very clean in this scenario, consider that the cables may never reconverge if connected differently.) This was identified and accepted as a limitation during work on #9102.

You're welcome to submit a feature request suggesting this as a new capability, however it would require a very detailed technical implementation proposal to be considered.

Thanks for the clarification. I rebuilt all my connections again but used 1 cable to connect both fiber positions in the middle patch and that seems to get my intended cable trace look but better. I must have messed up a setting somewhere. Thank-you for all you do btw. This is a godsend.

@CupcakeMunster commented on GitHub (Sep 13, 2022): > > Split path detected at fiber patch panel Building 2 > > This is expected behavior: At this point in the path, there is a split to two different cables, and we cannot support tracing any further. (Although it looks very clean in this scenario, consider that the cables may never reconverge if connected differently.) This was identified and accepted as a limitation during work on #9102. > > You're welcome to submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) suggesting this as a new capability, however it would require a very detailed technical implementation proposal to be considered. Thanks for the clarification. I rebuilt all my connections again but used 1 cable to connect both fiber positions in the middle patch and that seems to get my intended cable trace look but better. I must have messed up a setting somewhere. Thank-you for all you do btw. This is a godsend.
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#6977
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?