ENGINEERING GUIDE ยท OPERATIONS

Network Documentation & Diagramming

A practical guide to physical and logical diagrams, IP schedules, port maps, cable records and operational standards.

The important bit: Good documentation lets another engineer understand the network without asking the original designer.

Types of documentation

A useful set includes physical topology, logical topology, IP and VLAN schedules, device inventory, rack layouts, port maps and key dependencies such as DHCP, DNS, authentication and firewall boundaries.

Physical diagrams

Show switches, firewalls, routers, APs, servers, patch panels and major links. Include useful port identifiers and link speeds where they matter.

Logical diagrams

Show VLANs, subnets, routing boundaries, security zones and major traffic flows without unnecessary physical detail.

Operational records

RecordUseful fields
IP scheduleSubnet, gateway, DHCP range, reservations and purpose.
VLAN scheduleVLAN ID, name, subnet and security purpose.
Port mapSwitch, port, endpoint, VLAN and speed.
Cable scheduleOrigin, destination, patch ports, media and identifier.
Device inventoryHostname, model, management address, role and location.

Standards

Use consistent device names, VLAN names, interface descriptions and diagram symbols. Keep documentation versioned and record an owner and review date. Where possible, derive records from authoritative sources such as switch configuration and LLDP/CDP.

Checklist

  1. Document physical topology.
  2. Document Layer 3 boundaries.
  3. Maintain VLAN and IP schedules.
  4. Maintain port and cable maps.
  5. Record management and monitoring dependencies.
  6. Record important firmware versions.
  7. Version changes and identify the owner.
  8. Review documentation after significant changes.

Related tools

Generate topology diagrams and use neighbour discovery data as a source for documentation.

Network Topology Diagram Generator โ†’   LLDP / CDP Neighbour Analyser โ†’