starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cable Length Adding Parallel Paths Together #9492

New Issue
Closed
opened 2025-12-29 20:50:37 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:50:37 +01:00
Owner
Copy Link

Originally created by @jf5264835 on GitHub (Apr 16, 2024).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.5

Python Version

3.10

Steps to Reproduce

  1. Create device with interfaces.
  2. Create a patch panel with front and rear ports.
  3. Create second device with interfaces and second device with front and rear ports at different site.
  4. Patch interface to 2 front ports of patch panel (Simulating the two individual strands of a duplex fiber cable)
  5. Patch two rear ports from the first patch panel device to two rear ports of the second patch panel device.
  6. Patch two front ports from second patch panel device to one interface of second device with interfaces.

Expected Behavior

Distance reported in total distance field should be 57426m, the length of 2m patch cable, a 3m patch cable, and 57,421m of dark fiber.

Observed Behavior

Total cable is being calculated as the sum of all cables, even when two cables are parallel runs where a duplex cable was broken into two simplex cables. For the purposes of specing optics and other gear the total distance is only 57.421km, not 114.847km. Screenshot below of cable trace.
Snag_1079e34

Originally created by @jf5264835 on GitHub (Apr 16, 2024). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.5 ### Python Version 3.10 ### Steps to Reproduce 1. Create device with interfaces. 2. Create a patch panel with front and rear ports. 3. Create second device with interfaces and second device with front and rear ports at different site. 4. Patch interface to 2 front ports of patch panel (Simulating the two individual strands of a duplex fiber cable) 5. Patch two rear ports from the first patch panel device to two rear ports of the second patch panel device. 6. Patch two front ports from second patch panel device to one interface of second device with interfaces. ### Expected Behavior Distance reported in total distance field should be 57426m, the length of 2m patch cable, a 3m patch cable, and 57,421m of dark fiber. ### Observed Behavior Total cable is being calculated as the sum of all cables, even when two cables are parallel runs where a duplex cable was broken into two simplex cables. For the purposes of specing optics and other gear the total distance is only 57.421km, not 114.847km. Screenshot below of cable trace. ![Snag_1079e34](https://github.com/netbox-community/netbox/assets/5048674/615a61f9-6593-49d3-895d-3bebd790d029)
adam added the type: bugstatus: acceptednetboxtopic: cablingseverity: low labels 2025-12-29 20:50:37 +01:00
adam closed this issue 2025-12-29 20:50:37 +01:00
adam commented 2025-12-29 20:50:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 16, 2024):

What if the two parallel cables have different lengths?

@jeremystretch commented on GitHub (Apr 16, 2024): What if the two parallel cables have different lengths?
adam commented 2025-12-29 20:50:38 +01:00
Author
Owner
Copy Link

@jf5264835 commented on GitHub (Apr 16, 2024):

In that senario my thought would be that the two paths should then report two separate totals. The only time I can think that a total sum like this would be useful would be if one of the interfaces was unplugged and a loop back cable was installed for shooting the fiber with an OTDR.

@jf5264835 commented on GitHub (Apr 16, 2024): In that senario my thought would be that the two paths should then report two separate totals. The only time I can think that a total sum like this would be useful would be if one of the interfaces was unplugged and a loop back cable was installed for shooting the fiber with an OTDR.
adam commented 2025-12-29 20:50:38 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 24, 2025):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 24, 2025): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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 netbox severity: low status: accepted 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#9492
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?