-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Dell MX9116n and MX7116n #3344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Dell MX9116n and MX7116n #3344
Conversation
Created the Dell MX9116n Fabric switch for the Dell MX7000 chassis
Created the Dell MX7116n Fabric Expander Module for the Dell MX7000 chassis
Remove whitespace
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this is a network card this should probably be modeled as a module
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Harry, the MX9116n is a switch which can be put in a Dell MX7000 chassis. I moddeled it as a Child device because it's a device with it's own IP, management and configuration. Because we also have the HPE Synergy systemes I moddeled them the same: e.g. https://github.com/netbox-community/devicetype-library/blob/master/device-types/HPE/Virtual-Connect-SE-40Gb-F8-Module-for-Synergy.yaml
Please advise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HI @connect-cloud
Thank you for the information. Okay yes this should stay as a device type if it has it own management. For Devices we are asking for the following fields to be populated if possible:
weight
and associated weight unit
airflow
No description provided.