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

Allow half/Quarter sized modules in a chassis #10905

New Issue
Closed
opened 2025-12-29 21:37:33 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:37:33 +01:00
Owner
Copy Link

Originally created by @benkhesa1 on GitHub (Mar 17, 2025).

NetBox version

4.2.1

Feature type

Change to existing functionality

Proposed functionality

Hi All,

 I'm try to model an ARUBA 6410v2 chassis in Netbox that has 2 half size management modules (R0X31A):

Image

Regards,

Use case

If I try to use module bay, then it'll take all the 1U size. If I try to use device bay, then I can't address/view this device as part of the chassis: Device bay requires it's their identity (name, IP,...) and can't use the one of the chassis. Virtual chassis are not also useful as they're often used for switch in stack. So far, I used this type https://github.com/netbox-community/devicetype-library/blob/master/device-types/HPE/Aruba-6410-v2.yaml . I have the same issue also modeling the PSUs: this chassis has 4 in 1U.

So can we allow different width size modules in a chassis. If this change implies a lot of work, then what's the best solution to represent this device in netbox.

Database changes

No response

External dependencies

No response

Originally created by @benkhesa1 on GitHub (Mar 17, 2025). ### NetBox version 4.2.1 ### Feature type Change to existing functionality ### Proposed functionality Hi All, I'm try to model an ARUBA 6410v2 chassis in Netbox that has 2 half size management modules (R0X31A): ![Image](https://github.com/user-attachments/assets/c73bb2a9-7e3d-4f7b-ab84-0aa96cdb0476) Regards, ### Use case If I try to use module bay, then it'll take all the 1U size. If I try to use device bay, then I can't address/view this device as part of the chassis: Device bay requires it's their identity (name, IP,...) and can't use the one of the chassis. Virtual chassis are not also useful as they're often used for switch in stack. So far, I used this type https://github.com/netbox-community/devicetype-library/blob/master/device-types/HPE/Aruba-6410-v2.yaml . I have the same issue also modeling the PSUs: this chassis has 4 in 1U. So can we allow different width size modules in a chassis. If this change implies a lot of work, then what's the best solution to represent this device in netbox. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:37:33 +01:00
adam closed this issue 2025-12-29 21:37:33 +01:00
adam commented 2025-12-29 21:37:34 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Mar 20, 2025):

This idea has been proposed in the past and rejected as not supportable. For setups like the one described, there are two devices within a full-width 1U chassis and would need to be modeled as such, with the mounting bracket as the device containing the sub-devices (in the 2 device bays in this case). That gives you all the geometry and labeling necessary.

@bctiemann commented on GitHub (Mar 20, 2025): This idea has been proposed in the past and rejected as not supportable. For setups like the one described, there are two devices within a full-width 1U chassis and would need to be modeled as such, with the mounting bracket as the device containing the sub-devices (in the 2 device bays in this case). That gives you all the geometry and labeling necessary.
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#10905
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?