A NetBox with nothing left empty
A source of truth is only useful if it is complete and connected. This demo models a multi-site operator end to end, from the building down to the MAC address on a single port, so any question about the infrastructure has one answer.
What is modeled, and where to see it live
Every card opens that part of the live NetBox in a new tab. The demo is read-only for visitors and resets every night, so feel free to explore.
Regions, sites and locations
Five data centers and 98 branch offices across North America and Europe, grouped by region and site group.
Open sites ↗Racks and elevations
Rack types, rack groups, reservations and front/rear pictures of the real hardware in every U position.
Open racks ↗Devices with full lifecycle
Every device has a serial, asset tag, purchase order, warranty date, support contract, lifecycle stage and last audit date.
Open devices ↗Cables and interfaces
Thousands of interfaces with MAC addresses, cables traced end to end, and the optics and power supplies inside each box.
Open cables ↗Power
Power panels, feeds and switched PDUs, with a power budget on every rack so capacity planning is a query, not a guess.
Open power ↗IP addressing
VRFs with route targets, aggregates, prefixes, VLANs, ASN ranges, VRRP gateways and DNS names, all assigned to real interfaces.
Open IPAM ↗Circuits and providers
Seventeen carriers with accounts, provider networks, diverse internet groups and data center interconnect virtual circuits.
Open circuits ↗VPNs
IKEv2 and IPsec policies, 98 branch-to-data-center tunnels with both ends terminated, and an EVPN overlay between data centers.
Open tunnels ↗Virtualization
vSphere and Proxmox clusters, VM types, virtual disks and the services each VM runs.
Open VMs ↗Wireless
Corporate, guest, IoT and voice networks assigned to the radios of every access point.
Open wireless ↗Journal and history
Firmware upgrades, failed drives, RMAs and audits recorded on each device, so its history travels with it.
Open journal ↗Automation data
Config contexts, config templates, export templates, custom links, saved filters and event rules ready for automation.
Open config contexts ↗Custom fields that matter to operations
NetBox ships the structure; the custom fields make it fit how a data center actually runs. These are filled on every device and rack.
| Field | Used for |
|---|---|
| Lifecycle stage | Receiving, burn-in, production, RMA, decommissioning |
| Purchase date and PO | Tracing any box back to its order |
| Warranty expires | Renewal planning; a saved filter lists the next 90 days |
| Support contract | Who to call and how fast they must respond |
| Last physical audit | Proving the record was checked on the floor |
| Asset label printed | Finding hardware that still needs a label |
| Rack power budget (kW) | Capacity planning per rack |
Ready-made views for the team
Saved filters and export templates turn the data into everyday tools.
- Saved filters: warranty ending soon, devices in RMA, missing labels, audit overdue.
- Export templates: asset label sheets, Ansible inventory, physical audit sheets, cable labels, DNS zone records.
- Custom links: every device page has buttons for monitoring, uptime, labels and audit history.
- Event rules: a new device in NetBox is pushed to LibreNMS and Uptime Kuma automatically.
Visitors can browse everything. Editing, and the pages that would show the private monitoring server, need a login.