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

Trace only works when an interface is connected. #7107

New Issue
Closed
opened 2025-12-29 20:19:19 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:19:19 +01:00
Owner
Copy Link

Originally created by @LHBL2003 on GitHub (Oct 14, 2022).

NetBox version

v3.5.4

Python version

3.10

Steps to Reproduce

Create 2 to 3 devices with at least one front port and rear port.

Link the front and rear ports together.

Form a chain

Device 1 Front Port --> Rear Port --> Device 2 Rear Port --> Front Port --> Device 3 Rear Port --> Front Port

You now have e.g. three patch panels connected to each other.

Expected Behavior

The Trace button can be operated at Rear Port 1 of Device 1. However, "No paths found" is displayed.

Observed Behavior

On Device 1 I go to the Rear Port
Now I click on Trace at Rear Port 1.
Result: I do not see the connections between the patch panels. (No paths found)

Navigate to the front ports of Device 1.
Connect port 1 to an interface.
Result 1: The trace symbol can be operated at the front port. The complete cable path is displayed.
Result 2: The trace symbol can still be operated at the front port. The complete cable path is now also displayed here.

image

image

Please also show the cable path if no interface is connected.

This shows from where to where e.g. a network socket is patched via the patch panels before connecting a device. Sometimes no device is connected to the Netbox, e.g. staff workstations with notebooks. Nevertheless, we would like to be able to trace where the cable routes lead to.

Many thanks

Originally created by @LHBL2003 on GitHub (Oct 14, 2022). ### NetBox version v3.5.4 ### Python version 3.10 ### Steps to Reproduce Create 2 to 3 devices with at least one front port and rear port. Link the front and rear ports together. Form a chain Device 1 Front Port --> Rear Port --> Device 2 Rear Port --> Front Port --> Device 3 Rear Port --> Front Port You now have e.g. three patch panels connected to each other. ### Expected Behavior The Trace button can be operated at Rear Port 1 of Device 1. However, "No paths found" is displayed. ### Observed Behavior On Device 1 I go to the Rear Port Now I click on Trace at Rear Port 1. Result: I do not see the connections between the patch panels. (No paths found) Navigate to the front ports of Device 1. Connect port 1 to an interface. Result 1: The trace symbol can be operated at the front port. The complete cable path is displayed. Result 2: The trace symbol can still be operated at the front port. The complete cable path is now also displayed here. ![image](https://user-images.githubusercontent.com/46369917/195791426-24a6aa71-81ae-456e-abfd-a1b14398915f.png) ![image](https://user-images.githubusercontent.com/46369917/195791464-7019858b-2111-4e1f-ad1c-de7dc8295b2d.png) Please also show the cable path if no interface is connected. This shows from where to where e.g. a network socket is patched via the patch panels before connecting a device. Sometimes no device is connected to the Netbox, e.g. staff workstations with notebooks. Nevertheless, we would like to be able to trace where the cable routes lead to. Many thanks
adam added the status: duplicate label 2025-12-29 20:19:19 +01:00
adam closed this issue 2025-12-29 20:19:20 +01:00
adam commented 2025-12-29 20:19:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 14, 2022):

This is intended behavior, however FR #9718 has been opened to explore the feasibility of implementing the described changes.

@jeremystretch commented on GitHub (Oct 14, 2022): This is intended behavior, however FR #9718 has been opened to explore the feasibility of implementing the described changes.
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
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#7107
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?