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

[PR #2744] [CLOSED] Add cable type for backplane connections #12428

New Issue
Closed
opened 2025-12-29 22:21:32 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:21:32 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/2744
Author: @kasimon
Created: 1/3/2019
Status: ❌ Closed

Base: develop ← Head: patch-2

📝 Commits (1)

  • db85023 Add cable type for backplane connections

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 netbox/dcim/constants.py (+2 -0)

📄 Description

When documenting bladecenters with blade servers in them, the network interface is located on the blade server (device) and is connected over the bladecenter backplane to the pysical port on the blade center chassis (device). This can be perfectly modeled with netbox 2.5's new cable resource, but the existing cable types do not apply to this use case. Having a "backplane" cable type would make it possible to better describe and document these connections.

Fixes: #2743

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/2744 **Author:** [@kasimon](https://github.com/kasimon) **Created:** 1/3/2019 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `patch-2` --- ### 📝 Commits (1) - [`db85023`](https://github.com/netbox-community/netbox/commit/db850239af9f3775c024df80c94283e9845d641a) Add cable type for backplane connections ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `netbox/dcim/constants.py` (+2 -0) </details> ### 📄 Description When documenting bladecenters with blade servers in them, the network interface is located on the blade server (device) and is connected over the bladecenter backplane to the pysical port on the blade center chassis (device). This can be perfectly modeled with netbox 2.5's new cable resource, but the existing cable types do not apply to this use case. Having a "backplane" cable type would make it possible to better describe and document these connections. ### Fixes: #2743 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:21:32 +01:00
adam closed this issue 2025-12-29 22:21:32 +01:00
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 pull-request
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#12428
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?