-
|
Dear community, I've been searching a bit on how to deal with this situation, but i feel like this might be a bit of a niche situation. Hence why I'm opening this discussion here. I have the following situation. Most network devices will have a fixed port configuration, however this is not necessarily the case for all such as with a Cisco ASR-9902 for example. Here's some documentation It allows the operator to 'slice' the port configuration. This router has two NPUs and when i use the following slicing commands, it will result in the port numbers below: interfaces as a result: The bottom four HundredGigE interfaces are part of slice 1, whereas the rest is a result of the config of slice0. There are a whole bunch of variations possible. Thanks for your advice. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I had something similar with Nexus C36180YC switches, where a QSFP28 can be either 1 x 40G/100G or 4 x 10G/25G. They call this breakout, and it can either be configured globally, or port-by-port ("dynamic breakout"). For example, in the config, Ethernet1/49 vanishes, and is replaced with Ethernet1/49/1, Ethernet1/49/2, Ethernet1/49/3, Ethernet1/49/4. So in Netbox, I just did exactly the same: delete the QSFP28 interface, and add four SFP28 interfaces. I did this at the level of the device instance, not the device type. (It's perfectly fine to add and remove interfaces on a device instance; the device gets a copy of the interface templates at the time it is instantiated, and any subsequent changes to the device type do not affect any existing device instances) This meant that my breakout cables appeared as four cables, instead of one cable. I could instead have kept the Ethernet1/49, and created Ethernet1/49/1..4 as virtual interfaces with Ethernet1/49 as their parent. This models the physical breakout cable more accurately (one termination at one side and 4 terminations at the other), but it loses the ability to trace from each individual interface to its peer. EDIT: It looks like your ASR might be slightly different. As far as I can see, there's a fixed set of physical ports, but depending on how you configure the slicing, some ports may be active or inactive. You could model that by putting all the physical ports in the device type, and then when you change the slicing config, mark the unused ports as "disabled". (Or you could remove them, but then it's harder to put them back if you change your mind on the config) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your feedback. It's indeed not exactly like a breakout, but I'm guessing also not too far from it. Thanks :) |
Beta Was this translation helpful? Give feedback.
-
|
Cool. If you want to use "enabled" for admin shutdown, then there are other ways you could mark unused interfaces (tags, custom field, label, description). And if you don't change the slicing often (which I doubt you will) then simply deleting them is not so bad. You can recreate them from the interface templates on the device type using this script - or write your own custom script to handle slicing. |
Beta Was this translation helpful? Give feedback.
I had something similar with Nexus C36180YC switches, where a QSFP28 can be either 1 x 40G/100G or 4 x 10G/25G. They call this breakout, and it can either be configured globally, or port-by-port ("dynamic breakout").
For example, in the config, Ethernet1/49 vanishes, and is replaced with Ethernet1/49/1, Ethernet1/49/2, Ethernet1/49/3, Ethernet1/49/4.
So in Netbox, I just did exactly the same: delete the QSFP28 interface, and add four SFP28 interfaces. I did this at the level of the device instance, not the device type. (It's perfectly fine to add and remove interfaces on a device instance; the device gets a copy of the interface templates at the time it is instantiated, and any subsequent…