Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to trace cables with a Path Split on two sides of a path #17400

Closed
derjam opened this issue Sep 6, 2024 · 3 comments · Fixed by #17712
Closed

Unable to trace cables with a Path Split on two sides of a path #17400

derjam opened this issue Sep 6, 2024 · 3 comments · Fixed by #17712
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation topic: cabling type: bug A confirmed report of unexpected behavior in the application

Comments

@derjam
Copy link

derjam commented Sep 6, 2024

Deployment Type

Self-hosted

NetBox Version

v4.1.0

Python Version

3.12

Steps to Reproduce

We have an Evironment with 40G Switch Ports, which we split up with a cable to 4 x LC Connections. to a patch Panel. On the other side we have the same cable and go from 4 x LC to one 40G Switch Port. I found the error in our self-hosted netbox with a bit more complicated setting. But I was able to reproduce it with the netbox demo environment.

  1. Create a Switch called SwitchA
  2. Create a Switch called SwitchB
  3. Create a Patch Panel called PP1
  4. Create a Patch Panel called PP2
  5. Cable Front Ports 1-4 from PP1 to Front Ports 1-4 to PP2
  6. Cable GigabitEthernet1/0/1 from SwitchA to PP1 Rear Ports 1-4
  7. Cable GigabitEthernet1/0/1 from SwitchB to PP2 Rear Ports 1-4

Expected Behavior

You should be able to do a cable trace.
First you get a Path Split and select one Path:
netbox2
And then you should see the trace:
netbox3

Observed Behavior

You get the Path Split and you can select one Path:
netbox2#
But instead you get a Error, no Path is found:
netbox4

But when you change the connection from one switch interface to only one rear Port on the Patch Panel it works and you are able to trace this connection.

So you go from this:
netbox6
To this setting:
netbox7
It works, you can trace from both directions.

@derjam derjam added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Sep 6, 2024
@derjam derjam changed the title Unable to trace cables with a Path Split on two sides of a cable Unable to trace cables with a Path Split on two sides of a path Sep 6, 2024
@bctiemann bctiemann added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation topic: cabling severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Sep 6, 2024
@bctiemann
Copy link
Contributor

See also #17273 which I closed as a duplicate though it was opened earlier; its repro steps are also valid but are less detailed than in this one.

@eriktm
Copy link
Contributor

eriktm commented Oct 9, 2024

We are also hitting, what appears to be, this same bug. The issue seems to occur when connecting via multiple rear ports with 1 position mapped to 1 front port, and only when the cable trace hits the rear port before hitting the front port.

I already have a possible fix in my test environment, so I can do some more testing and submit a PR on it if thats ok by the maintainers?

@bctiemann
Copy link
Contributor

By all means!

eriktm added a commit to eriktm/netbox that referenced this issue Oct 9, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation topic: cabling type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants