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 and Circuit Termination for duplex patchcord ending #7760

New Issue
Closed
opened 2025-12-29 20:27:54 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:27:54 +01:00
Owner
Copy Link

Originally created by @krancslawomir on GitHub (Mar 15, 2023).

NetBox version

v3.4.5

Python version

3.8

Steps to Reproduce

Location A:

  1. Create Fiber Optic Patch Panel (ODF A)
  2. Create Rear Ports - 12 positions represents 12 fibers
  3. Create Front Ports - 12 positions represents 12 ports
  4. Create Router device A with interfaces

Location B:

  1. Create Fiber Optic Patch Panel (ODF B)
  2. Create Rear Ports - 12 positions represents 12 fibers
  3. Create Front Ports - 12 positions represents 12 ports
  4. Create Router device B with interfaces

Circuits:

  1. Create example circuit
  2. Set Circuit Termination A -> Site Location A -> ODF A > Rear Ports 1, 2
  3. Set Circuit Termination Z -> Site Location B -> ODF B -> Rear Ports 5, 6

Connections:

  1. Create Cable:
    A Side: Location A -> Router device A -> interface ex. xe-0/0/1
    B Side: Location A-> Fiber Otpic Patch Panel (ODF A) -> Front Port 1, 2

And now there is an error: <class 'AssertionError'>

I have verified that you can do connection cable only for 1 Front Port which represents simplex fiber patchcord (1 port) .
But in my case i would like to use also duplex fiber patchcord which reprezents 2 ports.

NetBox Error:
NetBox Error

What I can achieve currently:
What I can achieve v1
What I can achieve v2

Expected Behavior

I would like to use also duplex fiber patchcord (2 ports).
I would like to use different ports on Fiber Optcs Patch Panel in different locations like this:
What I want to achieve

Observed Behavior

<class 'AssertionError'>

Originally created by @krancslawomir on GitHub (Mar 15, 2023). ### NetBox version v3.4.5 ### Python version 3.8 ### Steps to Reproduce **Location A:** 1. Create Fiber Optic Patch Panel (ODF A) 2. Create Rear Ports - 12 positions represents 12 fibers 3. Create Front Ports - 12 positions represents 12 ports 4. Create Router device A with interfaces **Location B:** 1. Create Fiber Optic Patch Panel (ODF B) 2. Create Rear Ports - 12 positions represents 12 fibers 3. Create Front Ports - 12 positions represents 12 ports 4. Create Router device B with interfaces **Circuits:** 1. Create example circuit 2. Set Circuit Termination A -> Site Location A -> ODF A > Rear Ports 1, 2 3. Set Circuit Termination Z -> Site Location B -> ODF B -> Rear Ports 5, 6 **Connections:** 1. Create Cable: A Side: Location A -> Router device A -> interface ex. xe-0/0/1 B Side: Location A-> Fiber Otpic Patch Panel (ODF A) -> Front Port 1, 2 And now there is an error: <class 'AssertionError'> I have verified that you can do connection cable only for 1 Front Port which represents simplex fiber patchcord (1 port) . But in my case i would like to use also duplex fiber patchcord which reprezents 2 ports. **NetBox Error:** ![NetBox Error](https://user-images.githubusercontent.com/56762524/225308944-8964fc44-8da9-4e2f-bfe2-af9c98ba5a97.png) **What I can achieve currently:** ![What I can achieve v1](https://user-images.githubusercontent.com/56762524/225309094-5759536f-1d7d-45e6-a755-1ece0a2792b1.png) ![What I can achieve v2](https://user-images.githubusercontent.com/56762524/225309104-d0756a09-4149-4e10-a0da-353cb0a2ff81.png) ### Expected Behavior I would like to use also duplex fiber patchcord (2 ports). I would like to use different ports on Fiber Optcs Patch Panel in different locations like this: ![What I want to achieve](https://user-images.githubusercontent.com/56762524/225309386-d53e1ffd-3ba4-4ad0-9fbc-5c464733591e.jpg) ### Observed Behavior <class 'AssertionError'>
adam added the type: bugtopic: cablingseverity: medium labels 2025-12-29 20:27:54 +01:00
adam closed this issue 2025-12-29 20:27:54 +01:00
adam commented 2025-12-29 20:27:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 22, 2023):

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 (Sep 22, 2023): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:27:55 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 26, 2023):

https://github.com/netbox-community/netbox/pull/13337 looks like it fixes this as well.

@arthanson commented on GitHub (Sep 26, 2023): https://github.com/netbox-community/netbox/pull/13337 looks like it fixes this as well.
adam commented 2025-12-29 20:27:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2023):

I'm not able to reproduce this on v3.6.2. It was likely resolved in the course of some other work in a more recent release (unrelated to #13337). (Screenshot of the complete path below.)

screenshot

@jeremystretch commented on GitHub (Sep 26, 2023): I'm not able to reproduce this on v3.6.2. It was likely resolved in the course of some other work in a more recent release (unrelated to #13337). (Screenshot of the complete path below.) ![screenshot](https://github.com/netbox-community/netbox/assets/13487278/4cfa6cb6-2724-4194-a516-159915dd103d)
adam commented 2025-12-29 20:27:55 +01:00
Author
Owner
Copy Link

@krancslawomir commented on GitHub (Oct 11, 2023):

Hi, I confirm. I have installed latest version 3.6.3 and issue does not exist.
Thanks.

@krancslawomir commented on GitHub (Oct 11, 2023): Hi, I confirm. I have installed latest version 3.6.3 and issue does not exist. Thanks.
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 severity: medium 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#7760
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?