Types of Network Documentation
Physical network diagram: shows the physical layout — actual devices, their locations, physical connections, and cable runs. Includes floor plans, rack elevations, and cable paths. Used by technicians for physical troubleshooting and moves/adds/changes. Logical network diagram: shows the logical topology — IP addresses, VLANs, routing domains, and how traffic flows. Used for troubleshooting connectivity issues and planning changes.
Rack diagrams (elevation diagrams): document what equipment occupies each rack unit (U) in a server/network rack. Essential for data center management — identifies available space, power consumption, and cable organization. Wiring diagrams / cable management: document cable runs, patch panel ports, and switch port assignments. Often called 'cable maps' or 'port maps.'
IP Address Management (IPAM): tracks IP address assignments across the network — which IPs are used, by which device, and their DHCP vs static status. Prevents IP conflicts and helps identify unused address space. IPAM tools: SolarWinds IPAM, BlueCat, phpIPAM (open source).
Standard Operating Procedures and Policies
SOPs (Standard Operating Procedures): documented step-by-step procedures for common tasks — replacing a failed switch, adding a new VLAN, deploying a new WAP. SOPs ensure consistency and reduce errors, especially when tasks are performed by different team members.
Network baseline documentation: records normal performance metrics (bandwidth utilization, latency, error rates, CPU/memory) captured during normal operations. Baselines are compared against current metrics to identify anomalies — a 20% CPU spike is only meaningful if you know the baseline is typically 15%. Baselines are captured after major changes to update the normal reference.
Asset inventory: a record of all network equipment — model, serial number, firmware version, purchase date, and warranty status. Critical for change management and replacement planning. Configuration backups: copies of device configurations stored securely and updated after changes — essential for disaster recovery.