Customizable Device Type > Interface > Form Factor #55

New Issue

adam · 2025-12-29T15:30:55+01:00

adam commented

2025-12-29 15:30:55 +01:00

Originally created by @topside844 on GitHub (Jun 28, 2016).

The 'Form Factor' list is missing "10GE (Copper)" and/or "100M/1G/10G (Copper)" types used on 10GBASE-T devices like Cisco's Nexus 93120TX switch.

This can be resolved by either making the Form Factor list customizable, or adding the necessary 10GBASE-T form factor (which is not available in 10GE SFP+ form factor due to limited SFP+ power).

Originally created by @topside844 on GitHub (Jun 28, 2016). The 'Form Factor' list is missing "10GE (Copper)" and/or "100M/1G/10G (Copper)" types used on 10GBASE-T devices like Cisco's Nexus 93120TX switch. This can be resolved by either making the Form Factor list customizable, or adding the necessary 10GBASE-T form factor (which is _not_ available in 10GE SFP+ form factor due to limited SFP+ power).

adam closed this issue

2025-12-29 15:30:56 +01:00

adam commented

2025-12-29 15:30:56 +01:00

@jeremystretch commented on GitHub (Jun 28, 2016):

Will add this and probably some others to the static list. Definitely want to avoid custom interface form factors since only a finite set exists in the real world.

@jeremystretch commented on GitHub (Jun 28, 2016): Will add this and probably some others to the static list. Definitely want to avoid custom interface form factors since only a finite set exists in the real world.

adam commented

2025-12-29 15:30:56 +01:00

@bellwood commented on GitHub (Jun 29, 2016):

Could I request Cisco "10GE X2 SFP" ... Cisco's 3750E's (and others) use this

@bellwood commented on GitHub (Jun 29, 2016): Could I request Cisco "10GE X2 SFP" ... Cisco's 3750E's (and others) use this

adam commented

2025-12-29 15:30:57 +01:00

@candlerb commented on GitHub (Feb 7, 2019):

Although this issue is long closed, I would like to a add a couple of points.

The set of connectors which exist in the real world, whilst mathematically "finite", is much larger than Netbox currently supports. Currently open requests for additions include #1865, #1941, #2865, and there have been many others which were accepted and closed.

A static list will never meet everyone's needs - but as it gets larger, it will leave users having to scroll through many which are irrelevant to their environment (example: many exotic stacking cables for vendors which you don't use)
I disagree with the assertion in #97 that making the list customisable "would introduce a significant performance hit.". This is premature optimisation. At worst, you read the table once into RAM at startup, and whenever an edit is made to the list - performance is then identical to today.

Device Roles and Manufacturers and Platforms are customisable, and performance doesn't suffer.
There are infrastructure connections which need to be modelled which are not IP interfaces - e.g. DAS (SATA/SAS), SAN (fibre channel). Netbox has special cases for "console" and "power" connections (aside: it would in any case be useful to select the form factor for power connectors). But everything else falls under "interface", which in turn means a wider list of form factors is required than those used for IP.

There is always "Other" plus interface description, but this does not work well in an environment where you have many interfaces of a very specific type (e.g. in my case, many RF 'F' connectors for satellite feeds)

@candlerb commented on GitHub (Feb 7, 2019): Although this issue is long closed, I would like to a add a couple of points. * The set of connectors which exist in the real world, whilst mathematically *"finite"*, is much larger than Netbox currently supports. Currently open requests for additions include #1865, #1941, #2865, and there have been many others which were accepted and closed. A static list will never meet everyone's needs - but as it gets larger, it will leave users having to scroll through many which are irrelevant to their environment (example: many exotic stacking cables for vendors which you don't use) * I disagree with the assertion in #97 that making the list customisable *"would introduce a significant performance hit.*". This is premature optimisation. At worst, you read the table once into RAM at startup, and whenever an edit is made to the list - performance is then identical to today. Device Roles and Manufacturers and Platforms are customisable, and performance doesn't suffer. * There are infrastructure connections which need to be modelled which are not IP interfaces - e.g. DAS (SATA/SAS), SAN (fibre channel). Netbox has special cases for "console" and "power" connections (aside: it would in any case be useful to select the form factor for power connectors). But everything else falls under "interface", which in turn means a wider list of form factors is required than those used for IP. There is always "Other" plus interface description, but this does not work well in an environment where you have many interfaces of a very specific type (e.g. in my case, many RF 'F' connectors for satellite feeds)

adam referenced this issue

2025-12-29 15:35:20 +01:00

Expand/close subnet by clicking on the arrow in prefixes view #145

adam referenced this issue

2025-12-29 16:20:40 +01:00

Toggle Expanding of Individual Prefixes - Improvement #299

adam referenced this issue

2025-12-29 16:25:44 +01:00

Can't expand each ip_prefix, only expand all #778

Sign in to join this conversation.