mirror of
https://github.com/netbox-community/netbox.git
synced 2026-03-21 20:18:38 -06:00
625c4eb5bb
Add an `enabled` boolean field to ModuleBay, ModuleBayTemplate, DeviceBay, and DeviceBayTemplate models. Disabled bays prevent component installation and display accordingly in the UI. Update serializers, filters, forms, and tables to support the new field. Fixes #20152
37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Module Bays
|
|
|
|
Module bays represent a space or slot within a device in which a field-replaceable [module](./module.md) may be installed. A common example is that of a chassis-based switch such as the Cisco Nexus 9000 or Juniper EX9200. Modules, in turn, hold additional components that become available to the parent device.
|
|
|
|
!!! note
|
|
If you need to model child devices rather than modules, use a [device bay](./devicebay.md) instead.
|
|
|
|
!!! tip
|
|
Like most device components, module bays are instantiated automatically from [module bay templates](./modulebaytemplate.md) assigned to the selected device type when a device is created.
|
|
|
|
## Fields
|
|
|
|
### Device
|
|
|
|
The device to which this module bay belongs.
|
|
|
|
### Module
|
|
|
|
The module to which this bay belongs (optional).
|
|
|
|
### Name
|
|
|
|
The module bay's name. Must be unique to the parent device.
|
|
|
|
### Label
|
|
|
|
An alternative physical label identifying the module bay.
|
|
|
|
### Position
|
|
|
|
The numeric position in which this module bay is situated. For example, this would be the number assigned to a slot within a chassis-based switch.
|
|
|
|
### Enabled
|
|
|
|
Whether this module bay is enabled. Disabled module bays are not available for installation.
|
|
|