Week 7
Midterm Part 1 — Virtual LAN Design
In groups, design and document a complete virtual LAN in Packet Tracer.
Lesson recap
Real network engineers don't sit alone in a basement — they design with a team and they document everything. This week is half technical, half communication. You'll plan a topology together, defend your IP plan to teammates, build it in Packet Tracer, and write a report someone else could rebuild your network from. The grade isn't about how flashy the network is; it's about whether the documentation matches the .pkt file. If a teammate is sick and can't make it to class, your topology diagram and IP plan should be enough for the rest of the group to keep building.
Learning goals
- Plan a LAN topology with the team
- Document IP addressing plan
- Build the LAN in Packet Tracer
- Test all connectivity
- Produce a midterm report
Key terms
Topology Diagram
Visual map of the network — devices, links, IP addresses.
IP Plan
Assigned addresses for each device, usually in a table.
Group LAN
A team-built virtual LAN file.
Naming Convention
Consistent rule for hostnames (e.g. SW1, R1, PC-A) so diagrams match config.
Curated videos
How to Set Up a Simple Network in Cisco Packet Tracer
Breezy Codes
FREE CCNA 200-301 Course
David Bombal
Checkpoint checklist
Sign in to save your progress across devices.
- Group plan complete
- IP address table drafted
- LAN built in Packet Tracer
- All-device ping verified
- Midterm Part 1 report submitted
- Saved required evidence
- Answered the reflection questions
Pro tips from the instructor
- ★Decide the IP scheme on paper FIRST. Re-IPing a half-built topology is the #1 reason groups blow the deadline.
- ★Designate one person as 'documentation lead' — they own the diagram and the IP table while others build.
- ★Save the .pkt file as a new file every major milestone (v1, v2, v3) so you can roll back a broken change.
Try this — stretch exercises
Optional hands-on practice that goes beyond the workbook. Check items off as you complete them — progress saves in this browser.
0/1
- Add one realistic constraint to your design: 'sales must be on a separate subnet from engineering' or 'guest Wi-Fi can't reach internal servers.' Solve it.
Files to save this week
- 📁 Week07_MidtermPart1_LANDesign_GroupNumber.pkt
- 📁 Week07_MidtermPart1_Report_GroupNumber