mirror of
https://github.com/netbox-community/netbox.git
synced 2025-07-20 02:06:42 -06:00
Updated Frequently Asked Questions (markdown)
parent
353d80b4ca
commit
2a0e314c41
@ -1,7 +1,7 @@
|
||||
* [Why Doesn't NetBox Scan for IPs?](#why-doesnt-netbox-scan-for-ips)
|
||||
* [Why Does NetBox Require Every IP to Have a Mask?](#why-does-netbox-require-every-ip-to-have-a-mask)
|
||||
* [Why Can't I Connect a Virtual Circuit to an Interface?](#why-cant-i-connect-a-virtual-circuit-to-an-interface)
|
||||
* [How Can I Add New Interface Form Factors?](#how-can-i-add-new-interface-form-factors)
|
||||
* [How Can I Add New Interface Types?](#how-can-i-add-new-interface-types)
|
||||
* [Why Does NetBox Support Only Image Attachments?](#user-content-why-does-netbox-support-only-image-attachments)
|
||||
|
||||
# Why Doesn't NetBox Scan for IPs?
|
||||
@ -46,9 +46,9 @@ In this scenario, there are five **physical** circuits: One to each of the five
|
||||
|
||||
NetBox models only physical circuits, which can be terminated to physical interfaces on devices. While the ability to model virtual circuits would certainly be useful, it is impractical to account for the myriad technologies which might be used to establish a topology.
|
||||
|
||||
# How Can I Add New Interface Form Factors?
|
||||
# How Can I Add New Interface Types?
|
||||
|
||||
The set of available interface form factors is statically defined in NetBox; users cannot add arbitrary form factors. This is done to remove the potential for creating duplicate or illegitimate form factors that would degrade the data model. If there's a form factor you'd like to see added to NetBox, consider opening a [feature request](https://github.com/digitalocean/netbox/issues) detailing your use case. (However, bear in mind that only actual hardware interface types will be 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 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.
|
||||
|
||||
# Why Does NetBox Support Only Image Attachments?
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user