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 to rack connection #6378

New Issue
Closed
opened 2025-12-29 19:39:59 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:59 +01:00
Owner
Copy Link

Originally created by @AndMrzv on GitHub (Apr 19, 2022).

NetBox version

v3.1.10

Feature type

Data model extension

Proposed functionality

Allow whole Racks to be set as a connection point for Cables (instead of a specific Interface of a Device as it is now) as a connection point.

Use case

Having rented out racks you don't manage devices in them (a client plugs cables himself), you may not even have access inside of it. But the cables (network, power) going from your equipment into such racks are your responsibility, need to be managed and show the connection side.
Also it is nice to have cables managed when they are laid to yet empty racks (waiting to be filled with devices) or are still in the rack when the devices it was previously connected is taken out (now you have to delete the cable without one side from Netbox).

Database changes

No response

External dependencies

No response

Originally created by @AndMrzv on GitHub (Apr 19, 2022). ### NetBox version v3.1.10 ### Feature type Data model extension ### Proposed functionality Allow whole Racks to be set as a connection point for Cables (instead of a specific Interface of a Device as it is now) as a connection point. ### Use case Having rented out racks you don't manage devices in them (a client plugs cables himself), you may not even have access inside of it. But the cables (network, power) going from your equipment into such racks are your responsibility, need to be managed and show the connection side. Also it is nice to have cables managed when they are laid to yet empty racks (waiting to be filled with devices) or are still in the rack when the devices it was previously connected is taken out (now you have to delete the cable without one side from Netbox). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:39:59 +01:00
adam closed this issue 2025-12-29 19:40:00 +01:00
adam commented 2025-12-29 19:40:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2022):

Sorry but I have to reject this FR, as it would violate one of our core design tenets: replicate the real world. You cannot connect a cable to a rack in NetBox because you cannot connect a cable to a rack in reality.

You have two options under the current model:

  1. Create a dummy/unmanaged device in the rack that exists solely to terminate the far end of the cable.
  2. Forego modeling the cable and set mark_connected on the local interface to true.
@jeremystretch commented on GitHub (Apr 19, 2022): Sorry but I have to reject this FR, as it would violate one of our core design tenets: [replicate the real world](https://netbox.readthedocs.io/en/stable/#replicate-the-real-world). You cannot connect a cable to a rack in NetBox because you cannot connect a cable to a rack in reality. You have two options under the current model: 1. Create a dummy/unmanaged device in the rack that exists solely to terminate the far end of the cable. 2. Forego modeling the cable and set `mark_connected` on the local interface to true.
adam commented 2025-12-29 19:40:00 +01:00
Author
Owner
Copy Link

@AndMrzv commented on GitHub (Apr 20, 2022):

  1. Create a dummy/unmanaged device in the rack that exists solely to terminate the far end of the cable.
    Yes, this is exactly how we work around it now.

Replicating real world by dummies seems a bit strange to me but thank you for providing the explanation.

@AndMrzv commented on GitHub (Apr 20, 2022): > 1. Create a dummy/unmanaged device in the rack that exists solely to terminate the far end of the cable. Yes, this is exactly how we work around it now. Replicating real world by dummies seems a bit strange to me but thank you for providing the explanation.
adam commented 2025-12-29 19:40:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 20, 2022):

It's not strange at all. You know the cable connects to a device at the far end, you just don't know much about it, so you're limited in what you can model. Conversely, you know that the cable definitely doesn't connect to the rack itself.

@jeremystretch commented on GitHub (Apr 20, 2022): It's not strange at all. You know the cable connects to a device at the far end, you just don't know much about it, so you're limited in what you can model. Conversely, you know that the cable definitely _doesn't_ connect to the rack itself.
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: feature
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#6378
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?