Cable Trace and Circuit Termination for duplex patchcord ending

[krancslawomir]

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:

What I can achieve currently:

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:

Observed Behavior

<class 'AssertionError'>

[github-actions]

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.

[arthanson]

#13337 looks like it fixes this as well.

[jeremystretch]

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.)

[krancslawomir]

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