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

Cannot add cable between patch panels -"All mid-span terminations must all be attached to the same device" #11719

New Issue
Closed
opened 2025-12-29 21:48:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:48:58 +01:00
Owner
Copy Link

Originally created by @JCrabtree911 on GitHub (Oct 13, 2025).

NetBox Edition

NetBox Community

NetBox Version

V4.4.1

Python Version

3.12

Steps to Reproduce

  1. Create a device with a dcim.consoleport
  2. Create a patch panel - PP1.01 - with dcim.frontports mapped 1:1 to dcim.rearports
  3. Create a patch panel - PX1.01 - with dcim.frontports mapped 1:1 to dcim.rearports
  4. Create serial patch panel - SP1.01 - with dcim.frontports mapped 1:1 to dcim.rearports
  5. Create cable which terminates 8 of the rear ports on SP1.01 to a single dcim.consoleserverport
    (black breakout cable)
  6. create a cable which terminates 1 rear port on PP1.01 to 1 rear port on PX1.01
    (green cable)
  7. create a cable which terminates the dcim.consoleport to one dcim.frontport on PP1.01
    (red)
  8. Attempt to create a cable which connects a dcim.frontport of PX1.01 to a dcim.frontport of SP1.01 THIS WILL FAIL
    (PINK)

The cable run, in terms of port types, should be

dcim.consoleport -> dcim.frontport -> dcim.rearport -> dcim.rearport -> dcim.frontport -> dcim.frontport -> dcim.rearport -> dcim.consoleserverport

Image

Expected Behavior

The expected behavior is that I have a complete cable run (span) from a console port to a console server port.

Observed Behavior

I initially attempted this via the REST API and it only returned a '500 Internal Server Error' without details. I then tried to add this cable manually via the usual web interface and received the error message "All mid-span terminations must all be attached to the same device"

I searched for that error message and found 1 bug report for a 3.x release (and 4.02) which doesn't relate to this type of connection. It's not clear from this error message what the problem even is. There is only 1 device connected to each end of every cable in the span. Some further testing revealed the problem to be the breakout cable. This is a common scenario where a device has a breakout port connected to a patch panel and should be supported, or should, at least, return a more useful error message

Originally created by @JCrabtree911 on GitHub (Oct 13, 2025). ### NetBox Edition NetBox Community ### NetBox Version V4.4.1 ### Python Version 3.12 ### Steps to Reproduce 1. Create a device with a dcim.consoleport 2. Create a patch panel - PP1.01 - with dcim.frontports mapped 1:1 to dcim.rearports 3. Create a patch panel - PX1.01 - with dcim.frontports mapped 1:1 to dcim.rearports 4. Create serial patch panel - SP1.01 - with dcim.frontports mapped 1:1 to dcim.rearports 5. Create cable which terminates 8 of the rear ports on SP1.01 to a single dcim.consoleserverport (black breakout cable) 6. create a cable which terminates 1 rear port on PP1.01 to 1 rear port on PX1.01 (green cable) 7. create a cable which terminates the dcim.consoleport to one dcim.frontport on PP1.01 (red) 8. Attempt to create a cable which connects a dcim.frontport of PX1.01 to a dcim.frontport of SP1.01 **THIS WILL FAIL** (PINK) The cable run, in terms of port types, should be dcim.consoleport -> dcim.frontport -> dcim.rearport -> dcim.rearport -> dcim.frontport -> dcim.frontport -> dcim.rearport -> dcim.consoleserverport <img width="1300" height="750" alt="Image" src="https://github.com/user-attachments/assets/16f72c45-74d0-4360-a7d5-74a7950a13b4" /> ### Expected Behavior The expected behavior is that I have a complete cable run (span) from a console port to a console server port. ### Observed Behavior I initially attempted this via the REST API and it only returned a '500 Internal Server Error' without details. I then tried to add this cable manually via the usual web interface and received the error message _"All mid-span terminations must all be attached to the same device"_ I searched for that error message and found 1 bug report for a 3.x release (and 4.02) which doesn't relate to this type of connection. It's not clear from this error message what the problem even is. There **is** only 1 device connected to each end of every cable in the span. Some further testing revealed the problem to be the breakout cable. This is a common scenario where a device has a breakout port connected to a patch panel and should be supported, or should, at least, return a more useful error message
adam added the type: bugnetboxtopic: cablingseverity: low labels 2025-12-29 21:48:58 +01:00
adam closed this issue 2025-12-29 21:48:58 +01:00
adam commented 2025-12-29 21:48:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 17, 2025):

AFAICT this works as expected on NetBox v4.4.8. This may have been addressed by work done under #20432 in v4.4.7.

Image
@jeremystretch commented on GitHub (Dec 17, 2025): AFAICT this works as expected on NetBox v4.4.8. This may have been addressed by work done under #20432 in v4.4.7. <img width="358" height="1184" alt="Image" src="https://github.com/user-attachments/assets/68d0cb5b-01d2-40d5-ad45-d62aa7b872f1" />
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 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#11719
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?