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

No cable trace available when using modules #6741

New Issue
Closed
opened 2025-12-29 19:44:52 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:44:52 +01:00
Owner
Copy Link

Originally created by @bjankovich407 on GitHub (Jul 29, 2022).

NetBox version

3.2.5

Python version

3.8

Steps to Reproduce

Hello,

So I've created a few fiber patch panel devices. Each one utilizes Module Bays to then attack the respective fiber adapter module. Then I've created modules to assign to each bay with the respective number of front and back ports to link cables. I've tried making 12 front ports and linking them to one rear port with multiple positions and I've tried to have equal number of front and back ports. Then linking cabling between interfaces and am unable to get the cable trace functionality working no matter what I try.

We did recently update from version 3.1.7 and afterwards I am able to confirm that some traces are working and the ones that are not have all been added since version 3.2.25 was installed. I know this is a somewhat new feature and think th at either I'm not following a best practice or maybe there's functionality not fully implemented yet?

Expected Behavior

Expected for cable trace data to appear when clicking the link.

Observed Behavior

Netbox says "No paths found'.

Originally created by @bjankovich407 on GitHub (Jul 29, 2022). ### NetBox version 3.2.5 ### Python version 3.8 ### Steps to Reproduce Hello, So I've created a few fiber patch panel devices. Each one utilizes Module Bays to then attack the respective fiber adapter module. Then I've created modules to assign to each bay with the respective number of front and back ports to link cables. I've tried making 12 front ports and linking them to one rear port with multiple positions and I've tried to have equal number of front and back ports. Then linking cabling between interfaces and am unable to get the cable trace functionality working no matter what I try. We did recently update from version 3.1.7 and afterwards I am able to confirm that some traces are working and the ones that are not have all been added since version 3.2.25 was installed. I know this is a somewhat new feature and think th at either I'm not following a best practice or maybe there's functionality not fully implemented yet? ### Expected Behavior Expected for cable trace data to appear when clicking the link. ### Observed Behavior Netbox says "No paths found'.
adam added the type: bug label 2025-12-29 19:44:52 +01:00
adam closed this issue 2025-12-29 19:44:52 +01:00
adam commented 2025-12-29 19:44:53 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 29, 2022):

Cables need to be terminated to a fixed termination (interface, console port, etc) for it to generate a cable path. Are these terminating to something like a interface or are you just using the panels?

https://github.com/netbox-community/netbox/issues/9718 is the relevant FR to re-enable this functionality

@DanSheps commented on GitHub (Jul 29, 2022): Cables need to be terminated to a fixed termination (interface, console port, etc) for it to generate a cable path. Are these terminating to something like a interface or are you just using the panels? https://github.com/netbox-community/netbox/issues/9718 is the relevant FR to re-enable this functionality
adam commented 2025-12-29 19:44:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2022):

@DanSheps seems to have identified the root issue here, so I'm going to close this out. Happy to re-open it if this is not the case.

@jeremystretch commented on GitHub (Aug 3, 2022): @DanSheps seems to have identified the root issue here, so I'm going to close this out. Happy to re-open it if this is not the case.
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 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#6741
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?