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

Add the ability to trace path from 2 patchpanels #9207

New Issue
Closed
opened 2025-12-29 20:46:58 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:46:58 +01:00
Owner
Copy Link

Originally created by @YaHo4yPitsu on GitHub (Feb 7, 2024).

NetBox version

v3.6.3

Feature type

Change to existing functionality

Proposed functionality

As of today user can trace cable path only if there is an interface in this cable path.it would be great if user could trace path with only patchpanels too.
For example, if i create 2 patchpanels, connect them with their rear ports and try to trace path there will be error 'No path found'

Use case

I think its a great feature that will help in situations user documents all network related info in a under construction site or if you need NetBox only for passive network equipment.

Database changes

No response

External dependencies

No response

Originally created by @YaHo4yPitsu on GitHub (Feb 7, 2024). ### NetBox version v3.6.3 ### Feature type Change to existing functionality ### Proposed functionality As of today user can trace cable path only if there is an interface in this cable path.it would be great if user could trace path with only patchpanels too. For example, if i create 2 patchpanels, connect them with their rear ports and try to trace path there will be error 'No path found' ### Use case I think its a great feature that will help in situations user documents all network related info in a under construction site or if you need NetBox only for passive network equipment. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:46:58 +01:00
adam closed this issue 2025-12-29 20:46:58 +01:00
adam commented 2025-12-29 20:46:58 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Feb 8, 2024):

I would love that as well. Much of our passive infrastructure is dark fiber for other tenants, and I would love to see some traces for those connections. I've already tried to do this with connected circuits, but one circuit doesn't seem to be enough to trigger cable tracing.

@alehaa commented on GitHub (Feb 8, 2024): I would love that as well. Much of our passive infrastructure is dark fiber for other tenants, and I would love to see some traces for those connections. I've already tried to do this with connected circuits, but one circuit doesn't seem to be enough to trigger cable tracing.
adam commented 2025-12-29 20:46:59 +01:00
Author
Owner
Copy Link

@mihacucek commented on GitHub (Feb 21, 2024):

This functionality would be much appreciated and helpful.
I wish to have dark fibres documented and path shown despite the fact that is not used actively

  1. Connection between passive equipment like optical filters
  2. Lease of dark fibre that is for backup or not in use at the moment

My workaround was to create a test device with interfaces and connect them to optical patch panel ports to get the path trace shown. Not the best solution, since it makes confusion despite being a test device.

@mihacucek commented on GitHub (Feb 21, 2024): This functionality would be much appreciated and helpful. I wish to have dark fibres documented and path shown despite the fact that is not used actively 1. Connection between passive equipment like optical filters 2. Lease of dark fibre that is for backup or not in use at the moment My workaround was to create a test device with interfaces and connect them to optical patch panel ports to get the path trace shown. Not the best solution, since it makes confusion despite being a test device.
adam commented 2025-12-29 20:47:01 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 3, 2024):

Thanks for this well-reasoned feature request. I'm moving it along to the needs owner state, which means that anybody with the requisite skills and spare capacity is welcome to work on it. If you would like to volunteer to work it to a PR, just say so and somebody will assign it to you.

@jeffgdotorg commented on GitHub (Apr 3, 2024): Thanks for this well-reasoned feature request. I'm moving it along to the `needs owner` state, which means that anybody with the requisite skills and spare capacity is welcome to work on it. If you would like to volunteer to work it to a PR, just say so and somebody will assign it to you.
adam commented 2025-12-29 20:47:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2024):

I'm afraid the proposal above does not accurately capture the degree of effort required: The proposed functionality would require a substantial overhaul of the current cable path logic, which does not originate paths at pass-through (front/rear) ports. This was first explored a while back under #9718, which yielded no actionable plan for implementation.

I'm going to close this out as a duplicate of #9718. I'll be happy to re-open it if someone would like to first produce a workable proof of concept implementation that can be presented for discussion.

@jeremystretch commented on GitHub (Apr 4, 2024): I'm afraid the proposal above does not accurately capture the degree of effort required: The proposed functionality would require a substantial overhaul of the current cable path logic, which does not originate paths at pass-through (front/rear) ports. This was first explored a while back under #9718, which yielded no actionable plan for implementation. I'm going to close this out as a duplicate of #9718. I'll be happy to re-open it if someone would like to first produce a workable proof of concept implementation that can be presented for discussion.
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: duplicate 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#9207
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?