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

"Connection" column does not shows other end through 2 patch panels, also when tracing it does stop on the second panel #8116

New Issue
Closed
opened 2025-12-29 20:32:38 +01:00 by adam · 14 comments
adam commented 2025-12-29 20:32:38 +01:00
Owner
Copy Link

Originally created by @jmacias-packet on GitHub (May 25, 2023).

NetBox version

v3.3.7

Python version

3.8

Steps to Reproduce

  1. Create switch A
  2. Create patch panel 1
  3. Create patch panel 2
  4. Create switch B
  5. patch switch A - port 1 -> patch panel 1 - Front port 1A
  6. patch patch panel 1 - Rear port 1A to patch panel 2 - Rear port 1a
  7. patch patch panel 2 - Front port 1A to switch B - port 1

Click Trace either from switch A port 1 or switch B port 1

Expected Behavior

I should see a full trace of the link, as it happens when there is only 1 patch panel in between.

Observed Behavior

Some times shows "Patch split" at the bottom, then you choose the cable and it shows full trace correctly, but when you click trace again it happens again. Other times it just shows from switch A port 1 to the second patch panel and thats' it, it should show the full patch between both switches.
It never shows the "connection" info, just after "cable", as it does when you patch straight between switches or only through 1 patch panel.
Screenshot 2023-05-25 at 14 18 33
From the screenshot, you can see ethernet49/1 and 50/1 wrong, and 51/1 correctly working.

Originally created by @jmacias-packet on GitHub (May 25, 2023). ### NetBox version v3.3.7 ### Python version 3.8 ### Steps to Reproduce 1. Create switch A 2. Create patch panel 1 3. Create patch panel 2 4. Create switch B 5. patch switch A - port 1 -> patch panel 1 - Front port 1A 6. patch patch panel 1 - Rear port 1A to patch panel 2 - Rear port 1a 7. patch patch panel 2 - Front port 1A to switch B - port 1 Click Trace either from switch A port 1 or switch B port 1 ### Expected Behavior I should see a full trace of the link, as it happens when there is only 1 patch panel in between. ### Observed Behavior Some times shows "Patch split" at the bottom, then you choose the cable and it shows full trace correctly, but when you click trace again it happens again. Other times it just shows from switch A port 1 to the second patch panel and thats' it, it should show the full patch between both switches. It never shows the "connection" info, just after "cable", as it does when you patch straight between switches or only through 1 patch panel. ![Screenshot 2023-05-25 at 14 18 33](https://github.com/netbox-community/netbox/assets/69234931/daf6c015-e9a8-4096-a62c-1f1e28ebc30b) From the screenshot, you can see ethernet49/1 and 50/1 wrong, and 51/1 correctly working.
adam added the type: bugtopic: cabling labels 2025-12-29 20:32:38 +01:00
adam closed this issue 2025-12-29 20:32:38 +01:00
adam commented 2025-12-29 20:32:38 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (May 25, 2023):

I would like to highlight that this behaviour is random, it happens with most of the links through 2 patch panels but a few of them show correctly, also happens that it shoes correctly on one side but on the other side it shows with a "-"...

@jmacias-packet commented on GitHub (May 25, 2023): I would like to highlight that this behaviour is random, it happens with most of the links through 2 patch panels but a few of them show correctly, also happens that it shoes correctly on one side but on the other side it shows with a "-"...
adam commented 2025-12-29 20:32:39 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (May 25, 2023):

Another example is connecting to a circuit through 1 patch panel, it does trace correctly from the interface on the device but it does not show anything in "Connection" column.

@jmacias-packet commented on GitHub (May 25, 2023): Another example is connecting to a circuit through 1 patch panel, it does trace correctly from the interface on the device but it does not show anything in "Connection" column.
adam commented 2025-12-29 20:32:39 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (May 29, 2023):

I had to do something similar to this, feel free to correct me if I'm wrong but I did the following: Created two switches and two patch panels. From there - Switch 1 - Gi1(Interface) connected to 1(Rear Port) of Panel 1 followed by 1(Front Port) of Panel 1 connects to 1(Rear Port) of Panel 2. This ends with Switch 2 - Gi1(Interface) connecting to 1(Front Port) of Panel 2. I can see the whole trace.

image

Not sure if this is exactly what you tried to highlight or not but I was having the same issue and then realized it was Layer 8 problem (me configuring)

@Tene-brious commented on GitHub (May 29, 2023): I had to do something similar to this, feel free to correct me if I'm wrong but I did the following: Created two switches and two patch panels. From there - Switch 1 - Gi1(Interface) connected to 1(Rear Port) of Panel 1 followed by 1(Front Port) of Panel 1 connects to 1(Rear Port) of Panel 2. This ends with Switch 2 - Gi1(Interface) connecting to 1(Front Port) of Panel 2. I can see the whole trace. ![image](https://github.com/netbox-community/netbox/assets/128482272/6e2eb013-9d15-4017-a2b4-4cf41cf8d348) Not sure if this is exactly what you tried to highlight or not but I was having the same issue and then realized it was Layer 8 problem (me configuring)
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (May 31, 2023):

hi! I tried patching same as you and as I specified above but that behaviour is random, it seems a bug, you never got that thing again?

@jmacias-packet commented on GitHub (May 31, 2023): hi! I tried patching same as you and as I specified above but that behaviour is random, it seems a bug, you never got that thing again?
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (Jun 1, 2023):

No, because as I was saying it was an issue on my side. I was able to replicate something similar and I can see the whole trace of the cables I connected. I changed the names so it is a bit more clear but I tried to change the order in which the panels connect to see if the bug happened but it works as it should.

image

@Tene-brious commented on GitHub (Jun 1, 2023): No, because as I was saying it was an issue on my side. I was able to replicate something similar and I can see the whole _trace_ of the cables I connected. I changed the names so it is a bit more clear but I tried to change the order in which the panels connect to see if the bug happened but it works as it should. ![image](https://github.com/netbox-community/netbox/assets/128482272/89fd2b81-b8af-4fb6-9307-bcc51280a3ea)
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (Jun 1, 2023):

What NB version you using?

@jmacias-packet commented on GitHub (Jun 1, 2023): What NB version you using?
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (Jun 1, 2023):

v3.5.2

@Tene-brious commented on GitHub (Jun 1, 2023): v3.5.2
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (Jun 9, 2023):

Hi Tene, I upgraded to 3.5.3 version and tried it again, it is weird because from switch A to switch B, it traces well when at A side, but from 4 or 5 tests I did, 1 of them does not show well a
Screenshot 2023-06-09 at 14 00 48
Screenshot 2023-06-09 at 14 00 41

t B side, I mean, it does not show the Connection and trace shows a split, see a couple of screenshots.
I followed the sense of switch A - front | rear -> rear | front -> switch B.

@jmacias-packet commented on GitHub (Jun 9, 2023): Hi Tene, I upgraded to 3.5.3 version and tried it again, it is weird because from switch A to switch B, it traces well when at A side, but from 4 or 5 tests I did, 1 of them does not show well a ![Screenshot 2023-06-09 at 14 00 48](https://github.com/netbox-community/netbox/assets/69234931/fc7a6f23-a878-4e3d-a8a9-ab5c9a779f15) ![Screenshot 2023-06-09 at 14 00 41](https://github.com/netbox-community/netbox/assets/69234931/734ba60b-3916-4ecb-8199-2549a7379568) t B side, I mean, it does not show the Connection and trace shows a split, see a couple of screenshots. I followed the sense of switch A - front | rear -> rear | front -> switch B.
adam commented 2025-12-29 20:32:40 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (Jun 9, 2023):

I see, you're able to see the initial part of the trace but it does not show where it ends for you being from the front-port of the second patch panel to the second switch, is that what the problem is? Have you tried using a copper cable as a termination (at switch B)? I find it very odd that this does not work for you :/

@Tene-brious commented on GitHub (Jun 9, 2023): I see, you're able to see the initial part of the trace but it does not show where it ends for you being from the front-port of the second patch panel to the second switch, is that what the problem is? Have you tried using a copper cable as a termination (at switch B)? I find it very odd that this does not work for you :/
adam commented 2025-12-29 20:32:41 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (Jun 10, 2023):

Let me try but should be the same and we use fiber, there must be a bug because doing the same way for all 4 connections, that one is not working properly :(
No one from netbox replied or acknowledged this report yet..

@jmacias-packet commented on GitHub (Jun 10, 2023): Let me try but should be the same and we use fiber, there must be a bug because doing the same way for all 4 connections, that one is not working properly :( No one from netbox replied or acknowledged this report yet..
adam commented 2025-12-29 20:32:41 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (Jun 12, 2023):

I agree it should function exactly the same with fiber or copper connection. Just found it weird that I am not able to replicate this again on my end. Have you tried creating a separate rack with only 4 equipments to test this out?
You can always create a thread on slack (which is where I usually hang around and ask whenever I'm in doubt) to see if anyone else has this issue and maybe they can help.

@Tene-brious commented on GitHub (Jun 12, 2023): I agree it should function exactly the same with fiber or copper connection. Just found it weird that I am not able to replicate this again on my end. Have you tried creating a separate rack with only 4 equipments to test this out? You can always create a thread on slack (which is where I usually hang around and ask whenever I'm in doubt) to see if anyone else has this issue and maybe they can help.
adam commented 2025-12-29 20:32:41 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (Jun 17, 2023):

Hello Tene-brious, do you have the slack link? Maybe asking there will be quicker to get a reply from them.
Thank you

@jmacias-packet commented on GitHub (Jun 17, 2023): Hello Tene-brious, do you have the slack link? Maybe asking there will be quicker to get a reply from them. Thank you
adam commented 2025-12-29 20:32:41 +01:00
Author
Owner
Copy Link

@Tene-brious commented on GitHub (Jun 17, 2023):

https://join.slack.com/t/netdev-community/shared_invite/zt-1xg6cjhvn-ICQUUJTSQgWgjxLczd4CwQ thought you had joined already but here you go!
Have a nice weekend

@Tene-brious commented on GitHub (Jun 17, 2023): https://join.slack.com/t/netdev-community/shared_invite/zt-1xg6cjhvn-ICQUUJTSQgWgjxLczd4CwQ thought you had joined already but here you go! Have a nice weekend
adam commented 2025-12-29 20:32:42 +01:00
Author
Owner
Copy Link

@jmacias-packet commented on GitHub (Jun 17, 2023):

Thank you! Have a wonderful one!

@jmacias-packet commented on GitHub (Jun 17, 2023): Thank you! Have a wonderful one!
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 topic: cabling 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#8116
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?