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

Not Paths Found on cable tracing of Rear Ports with Modules #12025

Closed
jonatangobbato opened this issue Mar 21, 2023 · 6 comments
Closed

Not Paths Found on cable tracing of Rear Ports with Modules #12025

jonatangobbato opened this issue Mar 21, 2023 · 6 comments
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation topic: cabling type: bug A confirmed report of unexpected behavior in the application

Comments

@jonatangobbato
Copy link

NetBox version

v3.4.5

Python version

3.9

Steps to Reproduce

  1. Create a device A (Switch) and add some Interface SFP+
  2. Create a device B (Fiber Patch Panel) and add a Module with 12 Front ports (LC [1-12]) and 12 Rear Ports (SC [1-12])
  3. Create a device C (Fiber Patch Panel) and add a Module with 12 Front ports (LC [1-12]) and 12 Rear Ports (SC [1-12])
  4. Create a device D (Switch) and add some Interface SFP+
  5. Connect interface of Device A to 2 front Ports Of Device B LC 1 and LC2
  6. Connect the rear interfaces SC 1 and SC 2 of Device B to the rear interfaces SC 1 and SC 2 of the Device C
  7. Connect SFP+ interface of Device D to the front interfaces LC 1 and LC 2 of the device C.

Expected Behavior

When click on cable trace of the interface SFP+ of the device A, show the entire trace of the cable to the Device D, including the fiber patch panels on the way.

Observed Behavior

When click on the cable trace of Device A interface, only the trace to the device B are show, and a "Path split!" Warning appears and ask to select what nodes have to continue. When i click on one node, a page with the "No paths found" appears.

image

image

@jonatangobbato jonatangobbato added the type: bug A confirmed report of unexpected behavior in the application label Mar 21, 2023
@jonatangobbato
Copy link
Author

Update.
IF no Module on device B and dedvice C, the trace works fine.

image

@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 4, 2023
@jeremystretch jeremystretch added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Jun 23, 2023
@DanSheps
Copy link
Member

DanSheps commented Aug 7, 2023

This might be fixed with #13337 (#11079), I will test when I have time

@arthanson
Copy link
Collaborator

@DanSheps were you able to test if this was fixed?

@arthanson
Copy link
Collaborator

@jonatangobbato would you be able to test this with NetBox v3.6.3? I think it is probably fixed

@DanSheps
Copy link
Member

DanSheps commented Oct 10, 2023

This should be fixed, but let me test it out.

I think the big thing is going to be you shouldn't be using multi-position rear ports with multi-plex cables as we have no easy/clean way of telling which cable which rear port should connect to. You should instead use a single cable for each rear port (typically rear ports will be your plant fiber, if you are using multi-position ports, that is your "buffer" (12 fibers strands bundled). If you think of a 244, you would have:

  • 288 strands total
  • 24 buffers (Buffer tube really, Blue, Green, ... Blue-1, Green-1, etc)
  • 12 strands per buffer

Rear ports, with 12 positions, should be a single cable that is your "buffer". You shouldn't try and connect 2 "buffers" to 2 rear-ports.

@DanSheps
Copy link
Member

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation topic: cabling type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

5 participants