Cable tracing starting from patch panels #2237

New Issue

adam · 2025-12-29T17:24:00+01:00

adam commented

2025-12-29 17:24:00 +01:00

Originally created by @coloHsq on GitHub (Dec 21, 2018).

Environment

Python version: 3.6.5
NetBox version: 2.5.1

Proposed Functionality

Add cable tracing starting from devices that have pass-through ports, generally patch panels.

Use Case

In my case where I have to manage devices located in multiple sites is a very useful feature in case you need detailed reports of devices that use patch panels between two sites.
I've already developed "cable tracing" (including this feature) on Netbox < 2.5 and for me it's very useful
In my custom app all the cable tracing functions are displayed in tables (separated from the device page) to have a complete vision of the situation and not to open the single trace, starting from device
I actually prefer your version, but for this feature, which would actually serve as a report, it would be great have a view like this :

On the first column the end of the trace starting from the front port, in the middle the port name and in the last column the end of the trace starting from the rear port.

Database Changes

None

External Dependencies

None

Originally created by @coloHsq on GitHub (Dec 21, 2018). ### Environment * Python version: 3.6.5 * NetBox version: 2.5.1 ### Proposed Functionality Add cable tracing starting from devices that have pass-through ports, generally patch panels. ### Use Case In my case where I have to manage devices located in multiple sites is a very useful feature in case you need detailed reports of devices that use patch panels between two sites. I've already developed "cable tracing" (including this feature) on Netbox < 2.5 and for me it's very useful In my custom app all the cable tracing functions are displayed in tables (separated from the device page) to have a complete vision of the situation and not to open the single trace, starting from device I actually prefer your version, but for this feature, which would actually serve as a report, it would be great have a view like this : ![pptrace_li](https://user-images.githubusercontent.com/46020242/50335219-def63500-050a-11e9-9cb5-0f39af847fee.jpg) On the first column the end of the trace starting from the front port, in the middle the port name and in the last column the end of the trace starting from the rear port. ### Database Changes None ### External Dependencies None

adam closed this issue

2025-12-29 17:24:00 +01:00

adam commented

2025-12-29 17:24:00 +01:00

@jeremystretch commented on GitHub (Dec 21, 2018):

This information is available in the current view. Front and rear port connections are not displayed on the same line both to allow sufficient space and because they are not necessarily mapped one-to-one.

@jeremystretch commented on GitHub (Dec 21, 2018): This information is available in the current view. Front and rear port connections are not displayed on the same line both to allow sufficient space and because they are not necessarily mapped one-to-one.

adam commented

2025-12-29 17:24:01 +01:00

@coloHsq commented on GitHub (Dec 21, 2018):

This information is available in the current view. Front and rear port connections are not displayed on the same line both to allow sufficient space and because they are not necessarily mapped one-to-one.

Forgive me, but I think you haven't correctly understand my request, this feature, that I'm currently using on older version, was designed, in anticipation of some work on a bridge where our fibers pass, to know which devices would have been impacted in case of damage to the fiber (there were not any cables yet, so I made it based on patch panel's interface relations)
Regarding the initial request I realize that it is not so clear. I'll try to explain it better, starting from a patch panel I do the complete trace , like the actual netbox version, but in both directions (first from front, and then from rear), and I display only the terminations (the devices), for example, in the screenshot I've posted, starting from the front port "6", the connection goes through four patch panels and arrives on a fiber channel switch on port 10 (swfc01-b1306 : 10), and this is the termination of the front port trace, while for rear port trace do the same thing on the patch panel connected by trunk to the examinated patch panel.
I hope this is more clear, so you can understand my request.

@coloHsq commented on GitHub (Dec 21, 2018): > This information is available in the current view. Front and rear port connections are not displayed on the same line both to allow sufficient space and because they are not necessarily mapped one-to-one. Forgive me, but I think you haven't correctly understand my request, this feature, that I'm currently using on older version, was designed, in anticipation of some work on a bridge where our fibers pass, to know which devices would have been impacted in case of damage to the fiber (there were not any cables yet, so I made it based on patch panel's interface relations) Regarding the initial request I realize that it is not so clear. I'll try to explain it better, starting from a patch panel I do the complete trace , like the actual netbox version, but in both directions (first from front, and then from rear), and I display only the terminations (the devices), for example, in the screenshot I've posted, starting from the front port "6", the connection goes through four patch panels and arrives on a fiber channel switch on port 10 (swfc01-b1306 : 10), and this is the termination of the front port trace, while for rear port trace do the same thing on the patch panel connected by trunk to the examinated patch panel. I hope this is more clear, so you can understand my request.

adam referenced this issue

2025-12-29 21:19:41 +01:00

Add additional `save / create / cancel` buttons to top of forms (or make existing buttons stay visible) #9609

adam referenced this issue

2025-12-29 22:21:04 +01:00

[PR #2327] [CLOSED] Move the create/update/cancel buttons to the right-hand side and make them float #12359

adam referenced this issue

2025-12-29 22:22:06 +01:00

[PR #3225] [CLOSED] Make obj_edit form buttons float on the side #12529

Sign in to join this conversation.