I'm looking for a practical way to document physical infrastructure across several locations. We currently rely on Excel, diagrams, and photos, but that becomes difficult once there are many sites and nobody is sure which spreadsheet is current. Ideally, the system would track rack elevations and U positions, switches, patch panels, UPS and PDUs, servers, port-to-port cabling, serial numbers and asset details, rack and comms-room photos, IP and device information, and changes made when vendors replace equipment. What has worked well in real-world environments—Excel, Visio, NetBox, Device42, a custom system, or something else?
3 Answers
NetBox is probably the strongest option once spreadsheets stop scaling. It gives you a structured source of truth for racks, devices, IPAM, and cable connections. The setup takes some effort, and it only stays useful if someone owns the update process, but it is much easier to keep consistent across multiple sites than separate spreadsheets.
For field work, diagrams and photos can be more useful than a perfect database. We gave technicians a current rack photo or elevation with clearly marked cable endpoints and cable colors, which made remote installation work much easier. Visio can still be fine for diagrams if that is what the team already knows, but I would keep the authoritative device and connection data in a structured system rather than scattered files.
A good workflow is to pair NetBox with a simple documentation system for photos, floor plans, and site notes. You can link those pages to the relevant device records, while automation or monitoring scripts flag devices and connections that are missing from the documentation. That helps catch silent equipment swaps before the records become stale.
The main challenge is adoption. Even a great database becomes useless if vendors and internal staff do not update it after changes, so assigning ownership and making updates part of the change process matters more than the tool itself.