netbox icon indicating copy to clipboard operation
netbox copied to clipboard

Add the ability to trace path from 2 patchpanels

Open FckG0vn0 opened this issue 1 year ago • 2 comments

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

FckG0vn0 avatar Feb 07 '24 13:02 FckG0vn0

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 avatar Feb 07 '24 23:02 alehaa

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 avatar Feb 21 '24 09:02 mihacucek

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 avatar Apr 03 '24 21:04 jeffgdotorg

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 avatar Apr 04 '24 12:04 jeremystretch