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

End-to-end cable trace with "You are here!" #2418

New Issue
Closed
opened 2025-12-29 17:25:54 +01:00 by adam · 9 comments
adam commented 2025-12-29 17:25:54 +01:00
Owner
Copy Link

Originally created by @lcioltan on GitHub (Feb 28, 2019).

Environment

  • Python version: 3.5.3
  • NetBox version: v2.5.7

Proposed Functionality

When using the Trace option, it would be nice to always output the whole path
and mark the place from where the Trace option has been called.

Use Case

Let's use the following scenario. "Router-1" is connected to "Router-2" via 3 patchpanels:
Router-1/Port1 ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2

  1. in Netbox, if I select Router-1 and use the Trace option for "Port-1", the whole path will be displayed:
    Router-1/Port-1 ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2

  2. If I select patchpanel "PP-A" and use the Trace option for "Port-3", the following 2 paths
    will be displayed, depending on whether I use the front or the rear port:
    PP-A/Port-3 (Front): Router-1/Port-1 ---> PP-A/Port-3
    PP-A/Port-3 (Rear): PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2

With my proposal, I would like to have the complete path permanently displayed and to just mark the position from where the Trace function has been called.

  1. Router-1/Port-1 ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2
  2. Router-1/Port-1 ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2

Database Changes

None.

External Dependencies

None.

Originally created by @lcioltan on GitHub (Feb 28, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.3 * NetBox version: v2.5.7 ### Proposed Functionality When using the Trace option, it would be nice to always output the whole path and mark the place from where the Trace option has been called. ### Use Case Let's use the following scenario. "Router-1" is connected to "Router-2" via 3 patchpanels: Router-1/Port1 **--->** PP-A/Port-3 **--->** PP-B/Port-7 **--->** PP-C/Port-6 **--->** Router-2/Port-2 1. in Netbox, if I select Router-1 and use the Trace option for "Port-1", the whole path will be displayed: Router-1/Port-1 ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2 2. If I select patchpanel "PP-A" and use the Trace option for "Port-3", the following 2 paths will be displayed, depending on whether I use the front or the rear port: PP-A/Port-3 (Front): Router-1/Port-1 ---> PP-A/Port-3 PP-A/Port-3 (Rear): PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2 With my proposal, I would like to have the complete path permanently displayed and to just mark the position from where the Trace function has been called. 1. **Router-1/Port-1** ---> PP-A/Port-3 ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2 2. Router-1/Port-1 ---> **PP-A/Port-3** ---> PP-B/Port-7 ---> PP-C/Port-6 ---> Router-2/Port-2 ### Database Changes None. ### External Dependencies None.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 17:25:54 +01:00
adam closed this issue 2025-12-29 17:25:54 +01:00
adam commented 2025-12-29 17:25:55 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 28, 2019):

I will be honest, I think this would be a lot of development work for very little reward.

@DanSheps commented on GitHub (Feb 28, 2019): I will be honest, I think this would be a lot of development work for very little reward.
adam commented 2025-12-29 17:25:55 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Mar 2, 2019):

It's the same FR like https://github.com/digitalocean/netbox/issues/2758.
There we do the same discussion and it seems to be possible.

@tb-killa commented on GitHub (Mar 2, 2019): It's the same FR like https://github.com/digitalocean/netbox/issues/2758. There we do the same discussion and it seems to be possible.
adam commented 2025-12-29 17:25:55 +01:00
Author
Owner
Copy Link

@jbakklund commented on GitHub (Mar 4, 2019):

This seems to be a task for a recursive function, searching in both directions for the next port until it hits an interface, and then return the path.

@jbakklund commented on GitHub (Mar 4, 2019): This seems to be a task for a recursive function, searching in both directions for the next port until it hits an interface, and then return the path.
adam commented 2025-12-29 17:25:56 +01:00
Author
Owner
Copy Link

@jameswhite4684 commented on GitHub (Mar 5, 2019):

This is a great functionality and this can help anyone understand the cable flow of the network. That is one of the toughest things to map out and understand what is connected where without having to be inside the network device.

@jameswhite4684 commented on GitHub (Mar 5, 2019): This is a great functionality and this can help anyone understand the cable flow of the network. That is one of the toughest things to map out and understand what is connected where without having to be inside the network device.
adam commented 2025-12-29 17:25:56 +01:00
Author
Owner
Copy Link

@jameswhite4684 commented on GitHub (Mar 5, 2019):

It seems to work on add-on t1 cards now, I thought that wasn't working before but now I see it is. Great job there!

@jameswhite4684 commented on GitHub (Mar 5, 2019): It seems to work on add-on t1 cards now, I thought that wasn't working before but now I see it is. Great job there!
adam commented 2025-12-29 17:25:56 +01:00
Author
Owner
Copy Link

@seismiccollision commented on GitHub (May 2, 2019):

+1
I think the expected result for clicking on a trace would be seeing interface-to-interface regardless of where in the path the trace was called. If it is difficult to do, maybe a compromise would be having the ability to initiate a trace from the far-end back within any trace? This would at least save users the step of next clicking into a device and scrolling down to the right interface

@seismiccollision commented on GitHub (May 2, 2019): +1 I think the expected result for clicking on a trace would be seeing interface-to-interface regardless of where in the path the trace was called. If it is difficult to do, maybe a compromise would be having the ability to initiate a trace from the far-end back within any trace? This would at least save users the step of next clicking into a device and scrolling down to the right interface
adam commented 2025-12-29 17:25:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2019):

Leaving this open for grabs if someone wants to pick it up. Otherwise, it will be closed after a month for inactivity.

@jeremystretch commented on GitHub (Dec 13, 2019): Leaving this open for grabs if someone wants to pick it up. Otherwise, it will be closed after a month for inactivity.
adam commented 2025-12-29 17:25:56 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 27, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Dec 27, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 17:25:57 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 3, 2020):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Jan 3, 2020): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#2418
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?