Replies: 1 comment 2 replies
-
Hi @zeridon |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am currently trying to model (faithfully) MX7000 chassis and it's various IOM's/etc.
Netbox itself is used for both rack, device, network information, so we need to model a rack with a chassis. Inside the chassy blades and IOM cards. On the dc/location level we need to track cabling between switches and the IOM's. On the device level we need to track both chassis, blade, iom. On the network level we need to track interfaces (on the IOM's? on the Blades?) addressess etc (but thats the easy part)
What is your advice in regards to Chassis and IOM (example) modeling.
My issue here is that the chassis is modeled with device bays for everything. The front chassis slots can be used for plugging servers (but also storage) blades.
The back slots are for power (correctly modeled), Networking fabric (in 2 redundant groups) and storage fabric in a redundant group. Total is 6 IOM's
The before mentioned device type models this as just device bays.
The IOMs usually have 25Gb virtual ports (for internal usage in the chassis) and external ports. Then to boot they are usually qsfp's or whatever (e.g. module bays). To top that ports can be broken out to multiple types :). And even more some ports can be dual purpose (e.g. interconnect, networking, fiber channel, etc).
And the fun does not stop here. Depending how you configure the chassis and the fabric group interfaces can show in the inserted blades.
So any advice would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions