interface specific settings

[Jason Guy]

Hi All,

We are using netbox for a variety of things, including configuration of devices with automation. One question that came up was the lack of interface-specific parameters for ethernet interfaces. Sure we can specify some of the layer1 aspects, like interface type (1000base-T, 10Gbase-SR, etc). However there are other interface parameters that seem applicable:

- when dealing with twisted pair 10/100/1000, specify the intended speed/duplex/autoneg for the link.

- similar issues occur when using a SFP28, where it may need to autoneg, or statically be set to 10G.

- when working with QSFP28's, we also have to consider the FEC algorithm. 

I am thinking about multi-vendor environments, where it is not always safe to assume the link defaults. I realize some of this can be solved with local config context, but I also think this is part of planning, provisioning, and ultimately monitoring. It would be nice if there were some optional fields added to the interface structure to allow a user to include these layer1 options for completeness.

I started implementing it, and realized it would require a migration to add the fields to the database, however I am not entirely sure if that would break each time I re-sync with upstream. I can deal with that, but is this something that would be a good pull request? 

Cheers,

Jason

[wjhi nz]

We are looking for similar functionality

Custom fields have been discussed for interfaces, but unfortunately rejected.

https://github.com/digitalocean/netbox/issues/1254

[Jeremy Stretch]

Remember that NetBox is not intended to function as a complete CMDB: Some sets of data are best stored elsewhere.

> when dealing with twisted pair 10/100/1000, specify the intended speed/duplex/autoneg for the link

This sort of attribute is only applicable to a subset of interface types; it wouldn't make sense to add as a field on the Interface model. And typically you'll specify speed and duplex in the config templates, if at all.

> similar issues occur when using a SFP28, where it may need to autoneg, or statically be set to 10G.

This distinction is implied by the interfaces you define on the device. For instance, if you have a single 40GE interface on a Juniper device, you'd create et-0/0/0 in NetBox.  If it was channelized as 4x10GE, you'd create four separate interfaces named et-0/0/0:0 through et-0/0/0:3.

> when working with QSFP28's, we also have to consider the FEC algorithm.

Another item that's best stored in the configuration template, or perhaps in the config context of the parent device.

Jeremy

--
You received this message because you are subscribed to the Google Groups "NetBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To post to this group, send email to netbox-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/d08fe20a-5fea-4885-a4bb-3ff07db75d5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.