Replies: 2 comments 4 replies
-
I think cables trace a little different now. Can you try and replicate this on master.netbox.dev and I can take a look and see what you want and perhaps we can get a FR crafted for eventual inclusion. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Did you run the upgrade script? This calls |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I've upgraded our Netbox from 2.9.3 to 2.10.4 last week. Since then cables between front/rear ports are not traceable any more.
Our Datacenter Engineers use this to keep track of all cables between ODF's within our Datacenter.
There are no circuits or interfaces connected as originate or destination on these cables, yet.
Trace with cables connected to an interface or circuit do show the segments.
I think it would be beneficial to be able to trace any cable and view all segments with or without an originate or destination.
If the originate or destination is removed, you still would like to know from which ODF to which ODF cables are connected.
This is probably related to: Improved Cable Trace Performance (#4900)
Examples from v2.9.3:
![Front/Rear cable trace v2.9](https://user-images.githubusercontent.com/852442/106716678-0632f200-65ff-11eb-9896-742fba794a21.PNG)
Example from v2.10.4:
![Front/Rear cable trace v2.10](https://user-images.githubusercontent.com/852442/106716727-1054f080-65ff-11eb-8384-054073c24b6d.PNG)
Note: Same cable trace after upgrade.
Is this expected behavior for v2.10 (due to #4900) or should I create a bug report for this?
Kind regards,
Bram
Beta Was this translation helpful? Give feedback.
All reactions