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

Rack Width property for devices #10024

New Issue
Closed
opened 2025-12-29 21:25:54 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:25:54 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Jul 30, 2024).

NetBox version

v4.0.8

Feature type

Data model extension

Proposed functionality

I'd like to have a new rack_width field on Device Types with options of 1/4, 1/3, 1/2, and full. Full is the default, and would continue the current behavior. If this is set to anything other than full, then allow installing multiple devices in the same RU, without needing a “child” designation, as long as the sum of their widths is less than 1.
The rack elevation view would show all devices with their names and photos, and you can click directly on each one.

Use case

Many rack-mount devices are less than a full 19" width. Some examples:

  • Mellanox SX6012 switch
  • Palo Alto PA-220 firewall
  • Phabrix QxL rasterizer
  • Leader LV5600 waveform monitor
  • QSC Qsys Core Nano processor
  • QSC SPA4-100 amplifier

These devices are usually designed with two different mounting options:

  1. Side by side in the same RU with a joiner plate.
  2. One by itself by rotating the rack ear 90 degrees to make it a half-width blank

Currently, modeling two devices in the same RU requires designating them as "children", and making up a bogus parent device. Even when installing one by itself, you still have to create the parent.

This would make the rack elevation view more useful, and reduce busy work of creating unnecessary parent devices.

Database changes

a new rack_width field on the DeviceType and Device.

External dependencies

none

Originally created by @llamafilm on GitHub (Jul 30, 2024). ### NetBox version v4.0.8 ### Feature type Data model extension ### Proposed functionality I'd like to have a new `rack_width` field on Device Types with options of 1/4, 1/3, 1/2, and full. Full is the default, and would continue the current behavior. If this is set to anything other than full, then allow installing multiple devices in the same RU, without needing a “child” designation, as long as the sum of their widths is less than 1. The rack elevation view would show all devices with their names and photos, and you can click directly on each one. ### Use case Many rack-mount devices are less than a full 19" width. Some examples: - Mellanox SX6012 switch - Palo Alto PA-220 firewall - Phabrix QxL rasterizer - Leader LV5600 waveform monitor - QSC Qsys Core Nano processor - QSC SPA4-100 amplifier These devices are usually designed with two different mounting options: 1. Side by side in the same RU with a joiner plate. 2. One by itself by rotating the rack ear 90 degrees to make it a half-width blank Currently, modeling two devices in the same RU requires designating them as "children", and making up a bogus parent device. Even when installing one by itself, you still have to create the parent. This would make the rack elevation view more useful, and reduce busy work of creating unnecessary parent devices. ### Database changes a new `rack_width` field on the DeviceType and Device. ### External dependencies none
adam added the type: feature label 2025-12-29 21:25:54 +01:00
adam closed this issue 2025-12-29 21:25:54 +01:00
adam commented 2025-12-29 21:25:54 +01:00
Author
Owner
Copy Link

@kmorin18 commented on GitHub (Jul 30, 2024):

I would recommend using shelves and add module with device bays to insert each device into :)

@kmorin18 commented on GitHub (Jul 30, 2024): I would recommend using shelves and add module with device bays to insert each device into :)
adam commented 2025-12-29 21:25:55 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 2, 2024):

Could you provide some examples of these joiner plates? Everything I have seen indicates that these go into custom shelves which would be modeled as a device.

@DanSheps commented on GitHub (Aug 2, 2024): Could you provide some examples of these joiner plates? Everything I have seen indicates that these go into custom shelves which would be modeled as a device.
adam commented 2025-12-29 21:25:55 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Aug 2, 2024):

Here's a drawing from QSC showing a half rack mounting option. It references the IEC60297-3-100 spec but I don't have access to that.

The joining plate is not shown there but it's mentioned in the manual.
Qsys FAQ

Mellanox sells a rail kit, which can be used to mount either 1 or 2 units. Rail kits and/or brackets are required for most equipment but are never modeled in Netbox. Palo Alto does something similar.

For comparison, Arista 710P is a 1U device which also requires an extra rack-mount bracket. I'm sure nobody would want to make this bracket a "parent".

@llamafilm commented on GitHub (Aug 2, 2024): Here's a [drawing](https://www.qsys.com/resource-files/productresources/dn/dsp_cores/core_nano/q_dn_core_nano_halfrack_2ddrawing.pdf) from QSC showing a half rack mounting option. It references the IEC60297-3-100 spec but I don't have access to that. The joining plate is not shown there but it's mentioned in the [manual](https://www.qsys.com/resource-files/productresources/dn/dsp_cores/q_dn_core_nano_8flex_usermanual.pdf). [Qsys FAQ](https://support.qsys.com/faq-%7C-faq-can-12-and-14-rack-1u-q-sys-devices-mount-side-by-side) Mellanox sells a [rail kit](https://docs.nvidia.com/networking/display/sn2000pub/SN2100/SN2010+Side+by+Side+Mounting+Rail+Kit), which can be used to mount either 1 or 2 units. Rail kits and/or brackets are required for most equipment but are never modeled in Netbox. [Palo Alto](https://docs.paloaltonetworks.com/hardware/pa-220-hardware-reference/install-the-pa-220-firewall/install-the-pa-220-firewall-in-an-equipment-rack/install-the-pa-220-firewall-using-the-pan-pa-220-rack-single#id8c951c90-edb5-445b-8085-a11c66c2ba0d) does something similar. For comparison, Arista 710P is a 1U device which also requires an extra [rack-mount bracket](https://www.arista.com/en/qsg-710p-series/710p-series-mounting-the-switch). I'm sure nobody would want to make this bracket a "parent".
adam commented 2025-12-29 21:25:55 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 10, 2024):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Aug 10, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:25:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2024):

As other have mentioned, the solution to modeling this in NetBox is to device a parent device type with device bays to house the child devices. NetBox's data model cannot support arbitrary device widths.

@jeremystretch commented on GitHub (Aug 10, 2024): As other have mentioned, the solution to modeling this in NetBox is to device a parent device type with device bays to house the child devices. NetBox's data model cannot support arbitrary device widths.
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#10024
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?