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 2022-10-03 09:46:09 -04:00
parent 6e07e40dc2
commit 036379e52b
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Frequently-Asked-Questions.md

@ -1,5 +1,6 @@
* [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)
* [Is There a Maximum Number of Objects I can Define?](#is-there-a-maximum-number-of-objects-i-can-define)
* [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 Types?](#how-can-i-add-new-interface-types)
* [Why Does NetBox Support Only Image Attachments?](#user-content-why-does-netbox-support-only-image-attachments)
@ -42,6 +43,10 @@ Omitting the mask from the IP address model would require us to make dangerous i
Treating an IP address and its subnet mask as an atomic unit ensures a much greater degree of efficiency and accuracy.
# Is There a Maximum Number of Objects I can Define?
NetBox does not enforce any firm caps on the number of objects of any type created in NetBox. The only real limitation is the size of the PostgreSQL database which powers NetBox, and this is very unlikely to become a concern for real-world use. Despite NetBox being in use by many thousands of organizations globally for many years, we have yet to receive any reports of users encountering problems concerning the number of objects defined.
# Why Can't I Connect a Virtual Circuit to an Interface?
It's important to understand the difference between physical and virtual circuits. Suppose you have five sites arranged in a hub-and-spoke topology. The hub site has a point-to-point virtual circuit to each of its spoke sites; spoke-to-spoke traffic must pass through the hub. The virtual circuits are configured as 802.1Q-tagged subinterfaces on the hub site's router.