Skip to content

🛠 Project 07 — Network Documentation Package

Network Systems

View the live site — ijk37.com

Project 07: Network Documentation Package

Home All Projects Notes Quiz

Type: Design / documentation Modules: 02 (Infrastructure & Documentation) Difficulty: ⭐⭐


🎯 Objective

Produce the documentation package a technician would need to operate and troubleshoot a network — physical and logical diagrams, a rack elevation, an IP/asset inventory, a labeling scheme, and a change record.

Document a real network you have access to (home/lab), or the fictional Bright Retail office from Project 05.


📦 Deliverables

🔹 1. Physical network diagram

Show actual devices, ports, cable runs, and locations. Include MDF/IDF, patch panels, switches, APs, and the demarc/entrance facility.

🔹 2. Logical network diagram

Show IP addressing, subnets/VLANs, gateways, and how traffic flows (not physical cabling).

🔹 3. Rack elevation (rack diagram)

Document each device's U position in the rack (e.g., firewall U42, switch U40, patch panel U38, server U34–35, UPS U1–4). Total the rack units used.

🔹 4. IP / asset inventory (IPAM sheet)

A table of assigned addresses:

Device Role IP Subnet/VLAN MAC Location Firmware

🔹 5. Labeling scheme

Define a consistent scheme for cables, jacks, patch-panel ports, and racks (e.g., IDF2-PP1-P14 = IDF 2, patch panel 1, port 14). Explain how it speeds troubleshooting.

🔹 6. Change record + rollback plan

Write one change request for a realistic change (e.g., replacing the core switch), including reason/scope, risk, implementation steps, rollback plan, and approval line.


🧰 Tools


✅ Verification Checklist

  • Physical and logical diagrams are separate and each shows the right kind of information.
  • Rack elevation totals the U used and lists every mounted device.
  • IPAM sheet has no duplicate IPs and covers gateways/servers/infrastructure.
  • Labeling scheme is unambiguous and consistently applied on the diagrams.
  • Change record includes a rollback plan.

🚀 Stretch Goals

  • Capture a performance baseline (interface utilization at a normal time) to compare against later.
  • Add an SLA summary for the Internet link and define your MTTR target for a switch failure.

See also notes: [[02-03-network-documentation]], [[02-01-structured-cabling]], [[02-04-change-management]]