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 button missing for console and power connections #2605

New Issue
Closed
opened 2025-12-29 18:20:21 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:20:21 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (May 10, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.12

Steps to Reproduce

Make a console connection which goes via patch panels, e.g.

  1. Create device X with console server port and device Y with console port
  2. Create patch panels A and B with front and rear ports
  3. Connect A rear port to B rear port
  4. Connect device X console server port to patch panel A front port
  5. Connect device Y console port to patch panel B front panel

Expected Behavior

To be able to trace the console connection, in the same way interface connections can be traced.

Observed Behavior

image

The display correctly shows the near-side cable ID, and it shows the connected far-end console port. However there is no "trace" button so it's hard to find the path the connection takes.

Partial workaround:

  • Click on the cable
  • Look at the termination B information; remember which front port it is using
  • Click on the termination B device
  • Do a trace from the corresponding rear port

However that wouldn't work if multiple front ports link to the same rear port.

Originally created by @candlerb on GitHub (May 10, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.5.12 ### Steps to Reproduce Make a console connection which goes via patch panels, e.g. 1. Create device X with console server port and device Y with console port 2. Create patch panels A and B with front and rear ports 3. Connect A rear port to B rear port 4. Connect device X console server port to patch panel A front port 5. Connect device Y console port to patch panel B front panel ### Expected Behavior To be able to trace the console connection, in the same way interface connections can be traced. ### Observed Behavior ![image](https://user-images.githubusercontent.com/44789/57525513-d5873100-7322-11e9-9057-f149d953cedb.png) The display correctly shows the near-side cable ID, and it shows the connected far-end console port. However there is no "trace" button so it's hard to find the path the connection takes. Partial workaround: * Click on the cable * Look at the termination B information; remember which front port it is using * Click on the termination B device * Do a trace from the corresponding rear port However that wouldn't work if multiple front ports link to the same rear port.
adam added the type: bugstatus: accepted labels 2025-12-29 18:20:21 +01:00
adam closed this issue 2025-12-29 18:20:21 +01:00
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: accepted type: bug
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#2605
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?