Form Factor on Interface Template #650

Closed
opened 2025-12-29 16:24:19 +01:00 by adam · 6 comments
Owner

Originally created by @fabio-git on GitHub (Jan 22, 2017).

I need to add different typos of form factor.

Is it possible to enable the possibility to add/rem/edit, please?

Originally created by @fabio-git on GitHub (Jan 22, 2017). I need to add different typos of form factor. Is it possible to enable the possibility to add/rem/edit, please?
adam closed this issue 2025-12-29 16:24:19 +01:00
Author
Owner

@NetBod commented on GitHub (Jan 23, 2017):

or could custom fields be enabled in the interface section, that way people could add a custom field and then create there own list of interface types. Just thinking........

@NetBod commented on GitHub (Jan 23, 2017): or could custom fields be enabled in the interface section, that way people could add a custom field and then create there own list of interface types. Just thinking........
Author
Owner

@jeremystretch commented on GitHub (Jan 23, 2017):

Form factors pertain to the physical manifestation of interfaces in the real world, of which there is a finite set. As such, form factors are hard-coded into NetBox. There should never be a reason for a user to add a custom interface form factor.

What are you planning to add? If it's a legitimate form factor that isn't in NetBox, we can add it.

@jeremystretch commented on GitHub (Jan 23, 2017): Form factors pertain to the physical manifestation of interfaces in the real world, of which there is a finite set. As such, form factors are hard-coded into NetBox. There should never be a reason for a user to add a custom interface form factor. What are you planning to add? If it's a legitimate form factor that isn't in NetBox, we can add it.
Author
Owner

@fabio-git commented on GitHub (Jan 23, 2017):

Uhmm, you are right. Thinking about you've said, how can we set up this need:
There are some devices/modules with "combo" interfaces (1000BASE-T + SFP).
Today is not possible to add eth0 for 1000BASE-T and SFP at same time, thats why I thought, first, the possibility to add a combo.

@fabio-git commented on GitHub (Jan 23, 2017): Uhmm, you are right. Thinking about you've said, how can we set up this need: There are some devices/modules with "combo" interfaces (1000BASE-T + SFP). Today is not possible to add eth0 for 1000BASE-T and SFP at same time, thats why I thought, first, the possibility to add a combo.
Author
Owner

@jeremystretch commented on GitHub (Jan 23, 2017):

Yeah, I know exactly what you mean. The combo ports are a pain to model. My solution has been to create the interface with the form factor of whichever physical port is being used (you can always change it later if needed).

@jeremystretch commented on GitHub (Jan 23, 2017): Yeah, I know exactly what you mean. The combo ports are a pain to model. My solution has been to create the interface with the form factor of whichever physical port is being used (you can always change it later if needed).
Author
Owner

@fabio-git commented on GitHub (Jan 23, 2017):

This is what I'm doing. But if you find a way to implement this combo it would be very nice, so I could create a device template exactly as it is.
Just to register some devices with combo interfaces: Edgerouter (Ubiquiti), Routerboard (Mikrotik), Catalyst switches (Cisco), Huawei routers, Datacom switches, etc.
Tks

@fabio-git commented on GitHub (Jan 23, 2017): This is what I'm doing. But if you find a way to implement this combo it would be very nice, so I could create a device template exactly as it is. Just to register some devices with combo interfaces: Edgerouter (Ubiquiti), Routerboard (Mikrotik), Catalyst switches (Cisco), Huawei routers, Datacom switches, etc. Tks
Author
Owner

@jeremystretch commented on GitHub (Jan 23, 2017):

AFAICT there's no great solution to this. Despite the presence of two physical ports on a device, it only sees a single interface internally. IMO it's best to simply ignore the presence of the nonfunctional port entirely.

@jeremystretch commented on GitHub (Jan 23, 2017): AFAICT there's no great solution to this. Despite the presence of two physical ports on a device, it only sees a single interface internally. IMO it's best to simply ignore the presence of the nonfunctional port entirely.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#650