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

Cabling breakout cables and uplinks in the DCIM #9298

New Issue
Closed
opened 2025-12-29 20:48:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:48:05 +01:00
Owner
Copy Link

Originally created by @fziegert on GitHub (Feb 27, 2024).

Change Type

Addition

Area

Features

Proposed Changes

Hello everyone,
so far I have only worked with rack tables and am looking at NetBox for the first time. I am enthusiastic about Netbox, but I need two functions for my work with Netbox:
At the moment I don't know how I can or should implement them:
My first problem is:
I have uplinks to suppliers at each of my sites where I can only get one cable into the rack. I can't see a counterpart here.
So far I have marked these ports, where the uplink is plugged in, as reserved in rack tables and added a note.
How do I do this with NetBox? As I have seen, I always have to select an opposing interface. Is it possible to implement this feature?

My second problem is with the breakout cables. I only use break-out cables in the DAC area. I've already found that you can use breakout cables and I think it's great! In our cabling it is sometimes the case that not all interfaces are used by the breakout cable. Sometimes the second or third cable is free and unfortunately I don't know how to implement this so that it is clear which of the individual breakout cables is plugged into which port.
It would be great if I could leave one cable (for example 2) free or give each part of the breakout cable its own label.

Can you help me if I have overlooked any functions or would it be possible to implement something like this? Thank you very much!

Originally created by @fziegert on GitHub (Feb 27, 2024). ### Change Type Addition ### Area Features ### Proposed Changes Hello everyone, so far I have only worked with rack tables and am looking at NetBox for the first time. I am enthusiastic about Netbox, but I need two functions for my work with Netbox: At the moment I don't know how I can or should implement them: My first problem is: I have uplinks to suppliers at each of my sites where I can only get one cable into the rack. I can't see a counterpart here. So far I have marked these ports, where the uplink is plugged in, as reserved in rack tables and added a note. How do I do this with NetBox? As I have seen, I always have to select an opposing interface. Is it possible to implement this feature? My second problem is with the breakout cables. I only use break-out cables in the DAC area. I've already found that you can use breakout cables and I think it's great! In our cabling it is sometimes the case that not all interfaces are used by the breakout cable. Sometimes the second or third cable is free and unfortunately I don't know how to implement this so that it is clear which of the individual breakout cables is plugged into which port. It would be great if I could leave one cable (for example 2) free or give each part of the breakout cable its own label. Can you help me if I have overlooked any functions or would it be possible to implement something like this? Thank you very much!
adam closed this issue 2025-12-29 20:48:05 +01:00
adam commented 2025-12-29 20:48:05 +01:00
Author
Owner
Copy Link

@a084ed22 commented on GitHub (Feb 27, 2024):

I have uplinks to suppliers at each of my sites

assuming these are connectivity providers, you likely want to register them as circuits.

@a084ed22 commented on GitHub (Feb 27, 2024): > I have uplinks to suppliers at each of my sites assuming these are connectivity providers, you likely want to register them as circuits.
adam commented 2025-12-29 20:48:05 +01:00
Author
Owner
Copy Link

@fziegert commented on GitHub (Feb 27, 2024):

assuming these are connectivity providers, you likely want to register them as circuits.
@a084ed22 Thank you very much! That definitely solves one of my problems!

@fziegert commented on GitHub (Feb 27, 2024): > assuming these are connectivity providers, you likely want to register them as circuits. @a084ed22 Thank you very much! That definitely solves one of my problems!
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
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#9298
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?