~/netref / Documentation & IPAM
##

Documentation & IPAM

A network you can't see is a network you can't fix. Keep these artifacts current and authoritative.

Physical / logical diagramsTopology, L2/L3, rack & cabling maps
IPAMTrack IPs, subnets, VLANs, DNS/DHCP scopes
BaselinesNormal performance to compare against
Asset inventoryDevices, firmware, serials, EOL dates
Runbooks / SOPsStep-by-step operational procedures
Change managementApprove, document, roll back changes
LabelingPorts, cables, racks to a standard

// practices

  • IPAM prevents IP conflicts & overlaps across sites
  • Aim for one source of truth — DDI = DNS + DHCP + IPAM
  • Document before & after every change (audit trail)
  • Site survey, MDF / IDF, patch panels go in physical docs
  • Versioned configuration backups are part of documentation

// change management

Request (RFC)
→
Review / CAB
→
Approve & schedule
→
Implement
→
Verify
→
Document / close
Every change needs a tested rollback plan and a maintenance window. Failed verify → roll back.