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

Cable trace of multiple pairs of MPO CABLE #3075

New Issue
Closed
opened 2025-12-29 18:25:22 +01:00 by adam · 8 comments
adam commented 2025-12-29 18:25:22 +01:00
Owner
Copy Link

Originally created by @surlyjake on GitHub (Dec 16, 2019).

Environment

Netbox Version 2.6.7


  Device A                             Patch Panel A                              Patch Panel B          

+-----------+                +-------------+                                              +------------+

| Interface | --- Cable1 --- | Front Port1 | --+                                       +--| Front Port1|  ----+

+-----------+                +-------------+   |                                       |  +------------+      |

                                               |                                       |                      |

                                               |                                       |                      |

                                               +-----------+               +-----------+

                                               | Rear Port1| --- Cable3 ---| Rear Port1|                   Cable4

                                               +-----------+     (MPO)     +-----------+

                                               |                                       |                      |

  Device B                                     |                                       |                      |

+-----------+                +-------------+   |                                       |  +-------------+     |

| Interface | --- Cable2 --- | Front Port2 | --+                                       +--| Front Port 2|  ---+

+-----------+                +-------------+                                              +-------------+

Setup the environment for the topology:

  1. Create a device type for the endpoint device "example box"
  2. While viewing the "example box" device type, select "add components", then select "interfaces".
  3. Add a SFP interface ("test int") to the "example box" device type.
  4. Create a device type for a patch panel. ("example patch")
  5. While viewing the "example patch" device type, select "add components", then "rear port". Name: "rear", type: "MPO", positions: "12"
  6. While viewing the "example patch" device type, select "add components", then "front port". Name: "front[1-12]", type: "LC", rear ports: "back:1" hold down shift, then select "back:12"
  7. Click "devices", then the "add" icon next to "devices". Name: "example box 1". Device role "server". Device type: "example box".
  8. Click "devices", then the "add" icon next to "devices". Name: "example box 2". Device role "server". Device type: "example box".
  9. Click "devices", then the "add" icon next to "devices". Name: "example patch 1". Device role "Patch Panel. Device type: "example patch".
  10. Click "devices", then the "add" icon next to "devices". Name: "example patch 2". Device role "Patch Panel. Device type: "example patch".
  11. Click "devices" then "devices".
  12. Select "example box 1". In the interface list, for interface "test int", select the green connection icon (second from the left). Select "front port".
  13. On the "B side", select device "example patch 1" and port name "front1"
  14. Click "devices" then "devices".
  15. Select "example box 2". In the interface list, for interface "test int", select the green connection icon (second from the left). Select "front port".
  16. On the "B side", select device "example patch 1" and port name "front2"
  17. Click "devices" then "devices".
  18. Select "example patch 1". In the rear ports list, for port "back", select the green connection icon. Select "rear port"
  19. On the "B side", select "example patch 2" and port name "rear".
  20. Click "devices" then "devices".
  21. Select "example patch 2". In the front ports list, for port "front1". Select the green connection icon. Select "front port"
  22. On the "B side", select "example patch 2" and port name "front2"

Expected Behavior

Expected to see the observed cables AND the following:
d. Cable from "example patch 2" rear port "rear" => "example patch 1" rear port "rear"
e. Cable from "example patch 1" front port "front2" => "example box 2" interface "test int"

Observed Behavior

Now to check the topology:

  1. Select "devices", then "devices".
  2. Select "example box 1".
    a. In the interfaces list, it correctly shows that "example box 1" interface "test int" is connected to "example box 2" interface "test int".
  3. Select the blue icon next to the cable used in "test int" interface.
  4. Cable trace shows:
    a. Cable from "example box 1" interface "test int" => "example patch 1" front port "front1"
    b. Cable from "example patch 1" rear port "back" => "example patch 2" rear port "back"
    c. Cable from "example patch 2" front port "front1" => "example patch 2" front port "front2".
  5. From the cable trace, the last two cables of the full path are missing.
Originally created by @surlyjake on GitHub (Dec 16, 2019). ### Environment Netbox Version 2.6.7 ``` Device A Patch Panel A Patch Panel B +-----------+ +-------------+ +------------+ | Interface | --- Cable1 --- | Front Port1 | --+ +--| Front Port1| ----+ +-----------+ +-------------+ | | +------------+ | | | | | | | +-----------+ +-----------+ | Rear Port1| --- Cable3 ---| Rear Port1| Cable4 +-----------+ (MPO) +-----------+ | | | Device B | | | +-----------+ +-------------+ | | +-------------+ | | Interface | --- Cable2 --- | Front Port2 | --+ +--| Front Port 2| ---+ +-----------+ +-------------+ +-------------+ ``` Setup the environment for the topology: 1. Create a device type for the endpoint device "example box" 2. While viewing the "example box" device type, select "add components", then select "interfaces". 3. Add a SFP interface ("test int") to the "example box" device type. 4. Create a device type for a patch panel. ("example patch") 5. While viewing the "example patch" device type, select "add components", then "rear port". Name: "rear", type: "MPO", positions: "12" 6. While viewing the "example patch" device type, select "add components", then "front port". Name: "front[1-12]", type: "LC", rear ports: "back:1" hold down shift, then select "back:12" 7. Click "devices", then the "add" icon next to "devices". Name: "example box 1". Device role "server". Device type: "example box". 8. Click "devices", then the "add" icon next to "devices". Name: "example box 2". Device role "server". Device type: "example box". 9. Click "devices", then the "add" icon next to "devices". Name: "example patch 1". Device role "Patch Panel. Device type: "example patch". 10. Click "devices", then the "add" icon next to "devices". Name: "example patch 2". Device role "Patch Panel. Device type: "example patch". 11. Click "devices" then "devices". 12. Select "example box 1". In the interface list, for interface "test int", select the green connection icon (second from the left). Select "front port". 13. On the "B side", select device "example patch 1" and port name "front1" 14. Click "devices" then "devices". 15. Select "example box 2". In the interface list, for interface "test int", select the green connection icon (second from the left). Select "front port". 16. On the "B side", select device "example patch 1" and port name "front2" 17. Click "devices" then "devices". 18. Select "example patch 1". In the rear ports list, for port "back", select the green connection icon. Select "rear port" 19. On the "B side", select "example patch 2" and port name "rear". 20. Click "devices" then "devices". 21. Select "example patch 2". In the front ports list, for port "front1". Select the green connection icon. Select "front port" 22. On the "B side", select "example patch 2" and port name "front2" <!-- What did you expect to happen? --> ### Expected Behavior Expected to see the observed cables AND the following: d. Cable from "example patch 2" rear port "rear" => "example patch 1" rear port "rear" e. Cable from "example patch 1" front port "front2" => "example box 2" interface "test int" <!-- What happened instead? --> ### Observed Behavior Now to check the topology: 1. Select "devices", then "devices". 2. Select "example box 1". a. In the interfaces list, it correctly shows that "example box 1" interface "test int" is connected to "example box 2" interface "test int". 3. Select the blue icon next to the cable used in "test int" interface. 4. Cable trace shows: a. Cable from "example box 1" interface "test int" => "example patch 1" front port "front1" b. Cable from "example patch 1" rear port "back" => "example patch 2" rear port "back" c. Cable from "example patch 2" front port "front1" => "example patch 2" front port "front2". 5. From the cable trace, the last two cables of the full path are missing.
adam closed this issue 2025-12-29 18:25:23 +01:00
adam commented 2025-12-29 18:25:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 16, 2019):

Please expand your bug report to include the specific steps you are taking to reproduce the behavior.

@jeremystretch commented on GitHub (Dec 16, 2019): Please expand your bug report to include the specific steps you are taking to reproduce the behavior.
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 30, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Dec 30, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@surlyjake commented on GitHub (Dec 31, 2019):

<>

@surlyjake commented on GitHub (Dec 31, 2019): <<comment moved into body of post>>
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 31, 2019):

@surlyjake Please update the body of the issue with the steps to reproduce and fix the formatting so that they are legible.

@jeremystretch commented on GitHub (Dec 31, 2019): @surlyjake Please update the body of the issue with the steps to reproduce and fix the formatting so that they are legible.
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@surlyjake commented on GitHub (Dec 31, 2019):

Sorry for formatting. Updated the body. Should be legible now.

@surlyjake commented on GitHub (Dec 31, 2019): Sorry for formatting. Updated the body. Should be legible now.
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@fablabo commented on GitHub (Jan 7, 2020):

This is most likely to be resolved by implementing the suggested changes from #3633

@fablabo commented on GitHub (Jan 7, 2020): This is most likely to be resolved by implementing the suggested changes from #3633
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 21, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Jan 21, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:25:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2020):

Closing this as it will be addressed by #4388.

@jeremystretch commented on GitHub (Mar 30, 2020): Closing this as it will be addressed by #4388.
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
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#3075
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?