How to model BladeChassis -> Switch module (interfaces) -> Server module in device bay? #13497
-
|
Hi, I am using the Netbox version 3.5.4. Question: Explained a bit more: Thanks a lot! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Hi, I had a similar case in the past. in a similar context (server with added interface cards) i constructed the following model. i created 2 object types.
I added the server as a 'device type' with only the interfaces added to it that are fixed for that device (idrac/ilo, management interfaces,...). On top of that i have added module bays for every slot where you can add a physical module. Make sure to give every module bay a position value. This will help in a later stage with the naming when adding modules to the module bays. next i created a module type for my interface card. on that module type i've added the interfaces that are part of that module. To get some dynamic naming (in case you need to put multiple modules of the same type to the same device) i suggest naming the interfaces with the {module} placeholder. (e.g. Eth-{module}/0 ) This is the part where the position value of the module bay will come in play. When creating a server of that type, i can assign the necessary modules to the module bays. When adding the modules, you'll have the option to "replicate components". This option will add the interfaces of your module to the interfaces of your device, as if they are part of that device. When you remove the module, the interfaces will also be removed from the device since they are part of the module and not of the device directly. I hope this could answer your question. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Sorry for late answer. This is exactly what I was looking for. I found out that it probably is best to connect the device (module) interfaces (iLO, and all those you explained in your explanation) to the blade chassis switch interface with "Direct Attach Copper", and then connect the actual switch with normal cable. This way I think it is following normal world as much as possible. Thanks a lot for great explanation! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @PurplePetrus, Can you pl share the device-type & module-type yaml file for reference. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Just exported c7000 related device types and module types I am using. These are not the best I have noticed, but will tweak them one day. Currently they are just fine for my purpose. Blade System C7000 Onboard Administrator BL460c Gen10 Virtual Connect Flex-10/10D |
Beta Was this translation helpful? Give feedback.
-
|
Thanks mikasaari.. it's really useful. |
Beta Was this translation helpful? Give feedback.
Hi,
I had a similar case in the past.
in a similar context (server with added interface cards) i constructed the following model.
i created 2 object types.
I added the server as a 'device type' with only the interfaces added to it that are fixed for that device (idrac/ilo, management interfaces,...). On top of that i have added module bays for every slot where you can add a physical module. Make sure to give every module bay a position value. This will help in a later stage with the naming when adding modules to the module bays.
next i created a module type for my interface card. on that module type i…