netbox v2.11.7 releases: IP address management and data center infrastructure management tool
NetBox is an open-source web application designed to help manage and document computer networks. Initially conceived by the network engineering team at DigitalOcean, NetBox was developed specifically to address the needs of network and infrastructure engineers. It encompasses the following aspects of network management:
- IP address management (IPAM) – IP networks and addresses, VRFs, and VLANs
- Equipment racks – Organized by group and site
- Devices – Types of devices and where they are installed
- Connections – Network, console, and power connections among devices
- Virtualization – Virtual machines and clusters
- Data circuits – Long-haul communications circuits and providers
- Secrets – Encrypted storage of sensitive credentials
While NetBox strives to cover many areas of network management, the scope of its feature set is necessarily limited. This ensures that development focuses on core functionality and that scope creep is reasonably contained. To that end, it might help to provide some examples of functionality that NetBox does not provide:
- Network monitoring
- DNS server
- RADIUS server
- Configuration management
- Facilities management
That said, NetBox can be used to great effect in populating external tools with the data they need to perform these functions.
NetBox was designed with the following tenets foremost in mind.
Replicate the Real World
Careful consideration has been given to the data model to ensure that it can accurately reflect a real-world network. For instance, IP addresses are assigned not to devices, but to specific interfaces attached to a device, and an interface may have multiple IP addresses assigned to it.
Serve as a “Source of Truth”
NetBox intends to represent the desired state of a network versus its operational state. As such, automated import of live network state is strongly discouraged. All data created in NetBox should first be vetted by a human to ensure its integrity. NetBox can then be used to populate monitoring and provisioning systems with a high degree of confidence.
Keep it Simple
When given a choice between a relatively simple 80% solution and a much more complex complete solution, the former will typically be favored. This ensures a lean codebase with a low learning curve.
|HTTP service||nginx or Apache|
|WSGI service||gunicorn or uWSGI|
|Live device access||NAPALM|
- #6455 – Permit /32 IPv4 and /128 IPv6 prefixes
- #6493 – Show change log diff for non-atomic (pre-2.11) changes
- #6564 – Add N connector type for pass-through ports
- #6588 – Add support for webp files as front/rear device type images
- #6589 – Standardize breadcrumb navigation for power panels and feeds
- #6553 – ProviderNetwork search should match on name
- #6562 – Disable ordering of secrets by assigned object
- #6563 – Fix filtering by location for cable connection forms
- #6584 – Fix ordering of nested inventory items
- #6602 – Fix deletion of devices with cables attached