-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
@DanSheps were you able to test if this was fixed? |
@jonatangobbato would you be able to test this with NetBox v3.6.3? I think it is probably fixed |
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:
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. |
Tried 2 different ways:
I would say 100% fixed |
NetBox version
v3.4.5
Python version
3.9
Steps to Reproduce
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.
The text was updated successfully, but these errors were encountered: