Network documentation: diagrams, IP schema, change management, disaster recovery

CompTIA Network+ Preparation · lesson 17 of 30 · 25 min

Network Documentation

Accurate documentation is essential for troubleshooting, onboarding, audits, and disaster recovery. The Network+ exam tests knowledge of documentation types and their contents.

Physical Network Diagram — shows physical connections: cables, ports, rack locations, patch panels. Used for cabling troubleshooting.

Logical Network Diagram — shows IP addressing, VLANs, routing domains, and logical topology. Used for routing and connectivity troubleshooting.

IP Address Management (IPAM) — tracks IP address assignments, subnet allocations, and DHCP scopes. Prevents duplicate IPs and documents which device uses which address.

Network Baseline Documentation — records normal performance metrics (bandwidth utilization, latency, error rates) for comparison during troubleshooting.

Standard Operating Procedures (SOPs) — step-by-step procedures for common tasks (device replacement, VLAN provisioning, incident response).

Asset Inventory — tracks all network devices: make, model, serial number, firmware version, location, purchase date, warranty status.

Change Management

Change management controls how modifications are made to the network to minimize risk and unplanned outages. Key components:

Change Request — formal document describing the proposed change, reason, risk assessment, rollback plan, and implementation steps.

Change Advisory Board (CAB) — reviews and approves change requests. Ensures changes are tested and scheduled appropriately.

Change Window — scheduled maintenance period (typically nights/weekends) when changes are implemented to minimize user impact.

Rollback Plan — documented steps to revert the change if it causes problems. Must be tested before the change window.

Post-Implementation Review — verifies the change achieved its goal and documents lessons learned.

Why Change Management Matters

Studies show that 80% of network outages are caused by changes — not hardware failures. A formal change management process with testing, approval, and rollback plans dramatically reduces this risk.

High Availability and Disaster Recovery

High Availability (HA) — design that minimizes downtime through redundancy. Key metrics:

MTTR (Mean Time to Repair) — average time to restore service after a failure. Lower is better.

MTBF (Mean Time Between Failures) — average time between failures. Higher is better.

Availability % = MTBF / (MTBF + MTTR) × 100. “Five nines” = 99.999% = ~5 minutes downtime/year.

RTO (Recovery Time Objective) — maximum acceptable time to restore service after a disaster.

RPO (Recovery Point Objective) — maximum acceptable data loss measured in time (e.g., RPO of 4 hours means backups every 4 hours).

Redundancy strategies: Redundant power supplies, dual WAN links (active/active or active/standby), HSRP/VRRP for gateway redundancy, spanning tree for loop-free redundant paths, LACP EtherChannel for link aggregation.

Backup and Recovery

Full backup — complete copy of all data. Slowest to create, fastest to restore.

Incremental backup — backs up only data changed since the last backup (full or incremental). Fastest to create, slowest to restore (need full + all incrementals).

Differential backup — backs up all data changed since the last full backup. Moderate create time, faster restore than incremental (need full + latest differential only).

3-2-1 Rule — 3 copies of data, on 2 different media types, with 1 copy offsite.

Key Terms

Key Terms

Knowledge Check — 12 Questions

Network Operations — Documentation & DR

Which diagram shows IP addressing, VLANs, and routing domains?

  • Physical diagram
  • Logical diagram
  • Rack diagram
  • Wiring diagram

Answer: Logical diagram
Logical diagrams show IP addressing, VLANs, routing protocols, and logical topology — used for connectivity troubleshooting.

RTO is defined as:

  • Maximum acceptable data loss in time
  • Maximum acceptable downtime after a disaster
  • Average time between failures
  • Average time to repair
  • Answer: Maximum acceptable downtime after a disaster

RTO (Recovery Time Objective) defines how long the business can tolerate being down after a disaster. RPO is defined as:

  • Maximum acceptable downtime
  • Maximum acceptable data loss measured in time
  • Average time to repair
  • Backup frequency
  • Answer: Maximum acceptable data loss measured in time

RPO (Recovery Point Objective) defines how much data loss is acceptable — determines backup frequency.

Which backup type backs up only data changed since the last backup of any type?

  • Full
  • Differential
  • Incremental
  • Snapshot

Answer: Incremental
Incremental backups capture only changes since the last backup (full or incremental) — fastest to create, slowest to restore.

The 3-2-1 backup rule means:

  • 3 backups, 2 offsite, 1 encrypted
  • 3 copies, 2 different media, 1 offsite
  • 3 daily, 2 weekly, 1 monthly
  • 3 full, 2 differential, 1 incremental
  • Answer: 3 copies, 2 different media, 1 offsite

3-2-1: 3 copies of data, stored on 2 different media types, with 1 copy stored offsite. MTBF measures:

  • How long it takes to repair a failure
  • Average time between failures (reliability)
  • Maximum acceptable downtime
  • Backup frequency
  • Answer: Average time between failures (reliability)

MTBF (Mean Time Between Failures) measures device reliability — higher MTBF means fewer failures.

A rollback plan should be created and tested before implementing a network change.

  • True
  • False

Answer: True
A rollback plan must be ready before the change window — if the change fails, you need a tested way to revert quickly.

Which backup type requires the full backup plus only the most recent differential to restore?

  • Incremental
  • Differential
  • Full
  • Snapshot

Answer: Differential
Differential backups capture all changes since the last full — restore requires only the full + latest differential.

What is the purpose of a Change Advisory Board (CAB)?

  • Monitor network performance
  • Review and approve change requests
  • Respond to security incidents
  • Manage IP address assignments

Answer: Review and approve change requests
The CAB reviews proposed changes, assesses risk, and approves or defers them to appropriate change windows.

“Five nines” availability means _____ % uptime.

Answer: 99.999
99.999% availability = approximately 5.26 minutes of downtime per year.

IPAM is used to:

  • Monitor bandwidth usage
  • Track IP address assignments and subnet allocations
  • Configure routing protocols
  • Manage firewall rules
  • Answer: Track IP address assignments and subnet allocations

IPAM (IP Address Management) prevents duplicate IPs and documents which device uses which address.

Which availability metric should be minimized to improve uptime?

  • MTBF
  • MTTR
  • RTO
  • RPO

Answer: MTTR
MTTR (Mean Time to Repair) should be minimized — faster recovery = higher availability. MTBF should be maximized.


Previous lesson: Network monitoring: SNMP, syslog, NetFlow, SIEM, baseline metrics
Back to CompTIA Network+ Preparation
Next lesson: High availability: redundancy, HSRP/VRRP, link aggregation, load balancing