Skip to content

Unable to trace Cables when single Interfaces are connected across multiple Circuits #20432

@craized

Description

@craized

NetBox Edition

NetBox Community

NetBox Version

v4.4.1

Python Version

3.10

Steps to Reproduce

I created this setup in the NetBox demo instance in case anyone has a chance to look before it gets blown out. I'm just linking the originating interfaces since everything else is very easy to find from a cable trace

https://demo.netbox.dev/dcim/interfaces/2493/
https://demo.netbox.dev/dcim/interfaces/2438/

  1. Create two Sites, SITEA and SITEB
  2. Create two Devices, device1.sitea and device1.siteb (Example QFX5100-48T
  3. Create two Circuits, SPAN1-SITEA-TX and SPAN1-SITEA-RX
  4. Create Circuit Termination at SITEA and SITEB on each Circuit
  5. Connect device1.sitea interface et-0/0/48 to Circuit Termination "A" for both Circuit SPAN1-SITEA-TX and SPAN1-SITEA-RX by
    • Selecting two Circuits, SPAN1-SITEA-TX and SPAN1-SITEA-RX
    • Selecting two Sides, SPAN1-SITEA-TX: Termination A and SPAN1-SITEA-RX: Termination A
  6. Connect device1.siteb interface et-0/0/48 to Circuit Termination "Z" for both Circuit SPAN1-SITEA-TX and SPAN1-SITEA-RX by
    • Selecting two Circuits, SPAN1-SITEA-TX and SPAN1-SITEA-RX
    • Selecting two Sides, SPAN1-SITEA-TX: Termination B and SPAN1-SITEA-RX: Termination B
  7. Attempt to trace interface

Expected Behavior

A cable trace that goes from one interface, splits to both Circuit Termination Zs, then collapses from both Circuit Termination As to the far end interface

Observed Behavior

Path split! is detected between the Circuit and Termination Zs

Initial trace:
Image

Remaining trace after a split node is selected
Image

Metadata

Metadata

Assignees

Labels

status: under reviewFurther discussion is needed to determine this issue's scope and/or implementationtype: bugA confirmed report of unexpected behavior in the application

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions