NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-16 04:02:52 -06:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

Updated Frequently Asked Questions (markdown)

Jeremy Stretch 2021-11-10 11:35:19 -05:00
parent b7ad6b3349
commit f003fde1f3
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Frequently-Asked-Questions.md

@ -51,7 +51,15 @@ NetBox models only physical circuits, which can be terminated to physical interf
# How Can I Add New Interface Types?
The set of available interface types (previously referred to as "form factors" in early releases) is statically defined in NetBox. Users cannot add arbitrary form factors. This is because an interface type represents an actual classification that exists in the real world, such as 1000BASE-T or SFP+. Unless your organization manufactures custom network hardware, it is extremely unlikely that you'll need to define a new interface type. However, if you encounter a new commercially-available interface type that has not yet been added to NetBox, consider opening a [feature request](https://github.com/digitalocean/netbox/issues) to have it added.
The set of available interface types (previously referred to as "form factors" in early releases) is statically defined in NetBox. Users cannot add arbitrary types for interfaces (or other device components). There are several reasons for this:
1. An interface type represents an actual classification that exists in the real world, such as 1000BASE-T or SFP+. Unless your organization manufactures custom network hardware, it is extremely unlikely that you'll need to define a new interface type.
2. Allowing users to define arbitrary types would very likely lead to the creation of duplicate or redundant types.
3. Representing each type as a database object would impose a substantial performance penalty.
4. Allowing custom types would make the [device library](https://github.com/netbox-community/devicetype-library) much more difficult, if not impossible, to use.
5. Limiting types to the predefined set clearly conveys NetBox's scope as a source of truth for network infrastructure.
However, if you encounter a new commercially-available interface type that has not yet been added to NetBox, please consider opening a [feature request](https://github.com/netbox-community/netbox/issues) to have it added.
# Why Does NetBox Support Only Image Attachments?