mirror of
https://github.com/netbox-community/netbox.git
synced 2025-07-16 12:12:53 -06:00
796b9e84af
* 10500 add ModularComponentModel * 10500 add ModularComponentModel * 10500 add to forms * 10500 add to serializer, tables * 10500 template * 10500 add docs * 10500 check recursion * 10500 fix graphql * 10500 fix conflicting migration from merge * 10500 token resolution * 10500 don't return reverse * 10500 don't return reverse / optimize * Add ModuleTypeModuleBaysView * Fix replication of module bays on new modules * Clean up tables & templates * Adjust uniqueness constraints * Correct URL * Clean up docs * Fix up serializers * 10500 add filterset tests * 10500 add nested validation to Module * Misc cleanup * 10500 ModuleBay recursion Test * 10500 ModuleBay recursion Test * 10500 ModuleBay recursion Test * 10500 ModuleBay recursion Test * Enable MPTT for module bays * Fix tests * Fix validation of module token in component names * Misc cleanup * Merge migrations * Fix table ordering --------- Co-authored-by: Jeremy Stretch <jstretch@netboxlabs.com>
32 lines
1.0 KiB
Markdown
32 lines
1.0 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.
|