How to Add Module Component to Modules and Represent Daughter Cards #12211
Replies: 1 comment 10 replies
-
Child devices and device bays are never meant to be used for items which extend a device (e.g. line cards). They are for independent devices like blade servers, or for physical partitioning of some rack space to take smaller-sized devices. See the warning notes here and here. Modules are what you should use for things like line cards. Module "components" means ports which the module provides to the device (e.g. interfaces, console ports, console server ports etc) Modules aren't hierarchical, but you can also attach "inventory items" to individual ports; these can be used to record things like SFPs. If you can be more specific about the actual product/vendor device that you are trying to model, and what its options and modules are, we might be able to suggest the best way to model it in Netbox. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How in NetBox we can add module component to modules and represent daughter cards just like installing child devices in devices bays of parent devices as I could not find any way to do so; however, there is workaround to define such module as child device which then can accept installation of daughter card/module but we have redundant devices added to the device count which are actually modules to accommodate installation modules within modules.
Beta Was this translation helpful? Give feedback.
All reactions