Breakout Cable Cross Server #609

New Issue

MrUnknownDE · 2026-04-05T16:52:15+02:00

MrUnknownDE commented

2026-04-05 16:52:15 +02:00

Originally created by @BartZimmo on 1/12/2026

NetBox version

v4.5.0

Feature type

New functionality

Proposed functionality

Would it be possible to add functionality for breakout cables to be assigned over multiple interfaces from different devices + selecting the lane or position?
Maybe by add a new Cable profiles?
In most cases the cables splits in 2 or 4 cables. So 2 extra profiles would be good to start.

Use case

We use lots of breakout cables on our 100GbE switches.
We split a 100GbE port into 4 x 25/10GbE.
Each of the 4 breakout cables is connected to the first port of a server.
On a second switch, we have the same config.
With the difference that the 4 cables go to the second port of the same 4 servers.
With this config, we have redundancy over 2 switches.
As far as I know, we are currently limited to selecting only 1 device as a target.
We can select multiple interfaces of that target, but not the number/position/lane of the split cable.

If we use the NVIDIA Cumulus switches as an example, we would have the following config:
swp1 -> Physical port / Enable breakout config 4x
swp1s0, swp1s1, swp1s2, and swp1s3 -> Virtual Breakout ports.

Only the breakout config is done on swp1.
All other config like MTU and VLAN etc are done on the Virtual breakout ports.

With current NetBox limitations, I have 4 cables configured. One for each breakout port.
What does not match with the reality.

It would be great to have one cable in netbox:

The physical port is configured as the A side.
Each split cable can be assigned to an interface of choice, without limitation of 1 device.

We also need a way to link the interfaces on the switch, like partent/child, but on the split port level.

I have a few ideas how we can do this, but i would first like to know if this is planned or even considered.

Database changes

Extra Options for interface:

Category (Breakout).
- Enable Breakout/Split : True/False.
- Breakout lanes [required when Enable Breakout/split is true] : Choices 2 or 4.
- ** Optional ** Lane number starts at : 0 or 1. Depending on the manufacturer.
- Breakout parent interface: Select interface from list. [ Only show interfaces of the same device and have Enable Breakout/split as true.
- Breakout parent lane: Select free lane of the interface above.

External dependencies

No response

*Originally created by @BartZimmo on 1/12/2026* ### NetBox version v4.5.0 ### Feature type New functionality ### Proposed functionality Would it be possible to add functionality for breakout cables to be assigned over multiple interfaces from different devices + selecting the lane or position? Maybe by add a new Cable profiles? In most cases the cables splits in 2 or 4 cables. So 2 extra profiles would be good to start. ### Use case We use lots of breakout cables on our 100GbE switches. We split a 100GbE port into 4 x 25/10GbE. Each of the 4 breakout cables is connected to the first port of a server. On a second switch, we have the same config. With the difference that the 4 cables go to the second port of the same 4 servers. With this config, we have redundancy over 2 switches. As far as I know, we are currently limited to selecting only 1 device as a target. We can select multiple interfaces of that target, but not the number/position/lane of the split cable. If we use the NVIDIA Cumulus switches as an example, we would have the following config: swp1 -> Physical port / Enable breakout config 4x swp1s0, swp1s1, swp1s2, and swp1s3 -> Virtual Breakout ports. Only the breakout config is done on swp1. All other config like MTU and VLAN etc are done on the Virtual breakout ports. With current NetBox limitations, I have 4 cables configured. One for each breakout port. What does not match with the reality. It would be great to have one cable in netbox: - The physical port is configured as the A side. - Each split cable can be assigned to an interface of choice, without limitation of 1 device. We also need a way to link the interfaces on the switch, like partent/child, but on the split port level. I have a few ideas how we can do this, but i would first like to know if this is planned or even considered. ### Database changes 1. Extra Options for interface: - Category (Breakout). - - Enable Breakout/Split : True/False. - - Breakout lanes [required when Enable Breakout/split is true] : Choices 2 or 4. - - ** Optional ** Lane number starts at : 0 or 1. Depending on the manufacturer. - - Breakout parent interface: Select interface from list. [ Only show interfaces of the same device and have Enable Breakout/split as true. - - Breakout parent lane: Select free lane of the interface above. ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 16:52:15 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#609