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

Cable Trace (frontport to frontport) not available #4586

New Issue
Closed
opened 2025-12-29 18:37:57 +01:00 by adam · 6 comments
adam commented 2025-12-29 18:37:57 +01:00
Owner
Copy Link

Originally created by @PerAndersS on GitHub (Feb 24, 2021).

Environment

  • Python version: 3.9.1
  • NetBox version: v2.10.4

Steps to Reproduce

To create two devices, do the following:

  1. Create a device Role: "Role"
  2. Create a manufactorer: "Cisco"
  3. Create a Device type: manufactorer: Cisco, Model: TestModel, Height: 2
  4. Create two sites: Name: TestSite1/TestSite2
  5. Create one device on each site.
    Name: TestDevice1/TestDevice2
    Site: TestSite1/TestSite2
    Device type: Cisco TestModel
    Role: Role
  6. Create one rear port on each of the two devices:
    Device: TestDevice1/TestDevice2
    Name: rear1/rear2
    Type: SC
    Positions: 1
  7. Create one front port on each of the two devices, connected to the rear ports created in step 6.
    Device: TestDevice1/TestDevice2
    Name: front1/front2
    Type: SC
    Rear Port: rear1/rear2
  8. Finally, connect the two front ports by clicking "connect -- Front Port -- connect", then creating the cable between the two. Image to illustrate:
    image

Expected Behavior

Showing a trace between TestDevice1 and TestDevice2 with a cable in between.

Observed Behavior

When trace is clicked, nothing appears. Here is the trace view:
image

Additional Infromation

  • I have developed some plugins, but they are disabled.
  • Initially, I observed that most of the trace where broken. The majority where fixed by running the command: python manage.py trace_paths.

Thank you for your time!

Originally created by @PerAndersS on GitHub (Feb 24, 2021). ### Environment * Python version: 3.9.1 * NetBox version: v2.10.4 ### Steps to Reproduce To create two devices, do the following: 1. Create a device Role: "Role" 2. Create a manufactorer: "Cisco" 3. Create a Device type: manufactorer: Cisco, Model: TestModel, Height: 2 4. Create two sites: Name: TestSite1/TestSite2 5. Create one device on each site. Name: TestDevice1/TestDevice2 Site: TestSite1/TestSite2 Device type: Cisco TestModel Role: Role 6. Create one rear port on each of the two devices: Device: TestDevice1/TestDevice2 Name: rear1/rear2 Type: SC Positions: 1 7. Create one front port on each of the two devices, connected to the rear ports created in step 6. Device: TestDevice1/TestDevice2 Name: front1/front2 Type: SC Rear Port: rear1/rear2 8. Finally, connect the two front ports by clicking "connect -- Front Port -- connect", then creating the cable between the two. Image to illustrate: ![image](https://user-images.githubusercontent.com/46927491/108981380-f9993b00-768c-11eb-97c3-71768fdd88b6.png) ### Expected Behavior Showing a trace between TestDevice1 and TestDevice2 with a cable in between. ### Observed Behavior When trace is clicked, nothing appears. Here is the trace view: ![image](https://user-images.githubusercontent.com/46927491/108981185-c5be1580-768c-11eb-8760-322d7f174e4b.png) ### Additional Infromation - I have developed some plugins, but they are disabled. - Initially, I observed that most of the trace where broken. The majority where fixed by running the command: `python manage.py trace_paths`. Thank you for your time!
adam closed this issue 2025-12-29 18:37:58 +01:00
adam commented 2025-12-29 18:37:58 +01:00
Author
Owner
Copy Link

@dreng commented on GitHub (Feb 27, 2021):

I can confirm this issue and just want to add that the trace will be successful if "end devices" are connected (via interface). I'm not sure since when it is broken but I'm pretty sure that it has been functional before. My guess is that it's broken since v2.10. Maybe related to #4900 ?

@dreng commented on GitHub (Feb 27, 2021): I can confirm this issue and just want to add that the trace will be successful if "end devices" are connected (via interface). I'm not sure since when it is broken but I'm pretty sure that it has been functional before. My guess is that it's broken since v2.10. Maybe related to #4900 ?
adam commented 2025-12-29 18:37:58 +01:00
Author
Owner
Copy Link

@Rock-Y commented on GitHub (Mar 4, 2021):

See also: discussion #5741

@Rock-Y commented on GitHub (Mar 4, 2021): See also: [discussion #5741](https://github.com/netbox-community/netbox/discussions/5741)
adam commented 2025-12-29 18:37:59 +01:00
Author
Owner
Copy Link

@JonasKs commented on GitHub (Mar 25, 2021):

@jeremystretch, do you have any thoughts on this?

@JonasKs commented on GitHub (Mar 25, 2021): @jeremystretch, do you have any thoughts on this?
adam commented 2025-12-29 18:37:59 +01:00
Author
Owner
Copy Link

@networkhorse commented on GitHub (Apr 6, 2021):

Definitely needed for MMRs and other similar ODFs!

@networkhorse commented on GitHub (Apr 6, 2021): Definitely needed for MMRs and other similar ODFs!
adam commented 2025-12-29 18:37:59 +01:00
Author
Owner
Copy Link

@proudbro commented on GitHub (Apr 6, 2021):

Cable Traces rearport to rearport are not available too

@proudbro commented on GitHub (Apr 6, 2021): Cable Traces rearport to rearport are not available too
adam commented 2025-12-29 18:38:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2021):

This behavior is expected as front and rear ports are pass-through ports. Cable traces are created only when there is at least one non-pass-through endpoint, as all traces must define an origin point. Once you connect an endpoint (interface, console port, etc.) you'll be able to trace the path.

@jeremystretch commented on GitHub (Apr 6, 2021): This behavior is expected as front and rear ports are pass-through ports. Cable traces are created only when there is at least one non-pass-through endpoint, as all traces must define an origin point. Once you connect an endpoint (interface, console port, etc.) you'll be able to trace the path.
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
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#4586
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?