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

Front port "knows" interface at other end of the cable, but interface doesn't know the front port back #11312

New Issue
Closed
opened 2025-12-29 21:43:25 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:43:25 +01:00
Owner
Copy Link

Originally created by @bin-bern on GitHub (Jun 23, 2025).

Deployment Type

NetBox Cloud

NetBox Version

v4.3.2

Python Version

3.10

Steps to Reproduce

(Reproduced on demo.netbox.dev)

  1. Create/use a patch panel (with front and back ports) and a switch (with interfaces)
  2. Connect a free switch interface and a free patch panel front port with a (new) cable

Expected Behavior

The switch's list of interfaces and the patch panel's list of front ports should a) allow to trace the added cable and b) list its other endpoint.

Observed Behavior

(Note that I assume that the difference in unintended, and hence a bug.)
Tracing works on both sides, but the other end is only listed for the patch panel's list of front ports, see screenshot

Originally created by @bin-bern on GitHub (Jun 23, 2025). ### Deployment Type NetBox Cloud ### NetBox Version v4.3.2 ### Python Version 3.10 ### Steps to Reproduce (Reproduced on demo.netbox.dev) 1. Create/use a patch panel (with front and back ports) and a switch (with interfaces) 2. Connect a free switch interface and a free patch panel front port with a (new) cable ### Expected Behavior The switch's list of interfaces and the patch panel's list of front ports should a) allow to trace the added cable and b) list its other endpoint. ### Observed Behavior (Note that I _assume_ that the difference in unintended, and hence a bug.) Tracing works on both sides, but the other end is only listed for the patch panel's list of front ports, see screenshot
adam added the type: bug label 2025-12-29 21:43:25 +01:00
adam closed this issue 2025-12-29 21:43:25 +01:00
adam commented 2025-12-29 21:43:25 +01:00
Author
Owner
Copy Link

@bin-bern commented on GitHub (Jun 23, 2025):

Image

@bin-bern commented on GitHub (Jun 23, 2025): ![Image](https://github.com/user-attachments/assets/667b2cb7-cc12-4aa6-beea-5b89690af593)
adam commented 2025-12-29 21:43:26 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Jun 23, 2025):

Your screenshots are looking at two different columns. In the first one it's Connection and in the second one it's Link Peers. You can add the Link Peers column to the Interface table to see the same thing as you are seeing on the Front Port table. That column will only show you the direct peer for the cable, whereas the Connection column shows you the endpoint of the cable path. As front and rear ports are not path endpoint types, they do not have that column in their table. Both columns have their use cases, depending on whether you are interested in seeing just where a cable connects or the other end of a layer 1/2 connection that may span multiple cables and passive devices.

@sleepinggenius2 commented on GitHub (Jun 23, 2025): Your screenshots are looking at two different columns. In the first one it's `Connection` and in the second one it's `Link Peers`. You can add the Link Peers column to the Interface table to see the same thing as you are seeing on the Front Port table. That column will only show you the direct peer for the cable, whereas the `Connection` column shows you the endpoint of the cable path. As front and rear ports are not path endpoint types, they do not have that column in their table. Both columns have their use cases, depending on whether you are interested in seeing just where a cable connects or the other end of a layer 1/2 connection that may span multiple cables and passive devices.
adam commented 2025-12-29 21:43:26 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 23, 2025):

Yep, exactly what @sleepinggenius2 said. Thanks!

@jnovinger commented on GitHub (Jun 23, 2025): Yep, exactly what @sleepinggenius2 said. 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 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#11312
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?