Cable Trace (frontport to frontport) not available
See original GitHub issueEnvironment
- Python version: 3.9.1
- NetBox version: v2.10.4
Steps to Reproduce
To create two devices, do the following:
- Create a device Role: “Role”
- Create a manufactorer: “Cisco”
- Create a Device type: manufactorer: Cisco, Model: TestModel, Height: 2
- Create two sites: Name: TestSite1/TestSite2
- Create one device on each site. Name: TestDevice1/TestDevice2 Site: TestSite1/TestSite2 Device type: Cisco TestModel Role: Role
- Create one rear port on each of the two devices: Device: TestDevice1/TestDevice2 Name: rear1/rear2 Type: SC Positions: 1
- 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
- Finally, connect the two front ports by clicking “connect – Front Port – connect”, then creating the cable between the two. Image to illustrate:
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:
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!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Unable to trace cable if front and back ports are not both ...
Create a connection from a device interface to a front port on another device, but do not connect the rear port to another...
Read more >Front port status when rear port has a connection
When an interface from a router or switch is connected to Rack Z F2, a trace perfectly shows the connection ending up on...
Read more >Cable trace over multiple hops isn't possible? : r/Netbox
I can get trace to work with the 1 sfp to 2 front port breakout like what I'm trying but only if there's...
Read more >Netbox Cabling - YouTube
As you get into NetBox, you'll realize that you can do much more than simply IPAM (IP Address Management)!NetBox is a full-featured “single ......
Read more >Netbox – Creating patch panels and passive cabling
Each front port should be mapped to a rear port. ... Now click on the green cable trace button and behold the patching...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
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 ?