Implementing Network Infrastructure
using Cisco Packet Tracer
Introduction
In today’s interconnected world, a solid understanding of network infrastructure is more crucial
than ever. Gaining hands-on experience with network design and implementation can be a
significant hurdle due to the cost and complexity of physical hardware. This is where Cisco
Packet Tracer comes in. This powerful simulation tool provides a virtual environment to design,
configure, and troubleshoot network topologies, offering an invaluable sandbox for learning and
experimentation. In this post I will implement a network infrastructure for a project scenario with
Cisco Packet Tracer.
Project Scenario
Company: WongKito Solutions — A growing technology consulting firm
Current Situation: WongKito has outgrown their basic network setup and needs a professional,
scalable network infrastructure to support their expanding operations.
Company Structure
Headquarters (Jakarta): 11 employees
• Sales Department: 6 employees
• IT Department: 3 employees
• HR Department: 2 employees
Branch Office (Palembang): 9 employees
• Sales Department: 4 employees
• Temporary contractors/guests: 5 concurrent users
Business Requirements Document
Primary Requirements:
R1 — Network Segmentation
• Separate network segments for each department for security and performance
• Sales, IT, HR departments must have isolated broadcast domains
• Guest network must be completely isolated from corporate resources
• Inter-departmental communication should be controllable
R2 — Automatic IP Management
• All end-user devices must receive IP addresses automatically
• IP address management should be centralized where possible
• Reserved IP ranges for servers and network equipment
• DNS services must be provided to all users
R3 — Site-to-Site Connectivity
• Both locations must communicate seamlessly
• Branch office must access headquarters resources
• Routing must be dynamic and automatically adapt to network changes
• Network convergence time should be minimized during outages
R4 — Internet Access
• All corporate users must have internet access
• Internet access should be centralized through headquarters
• Public IP addresses must be conserved using address translation
• External users should not be able to access internal resources directly
R5 — Security Policies
• Guest users cannot access any corporate network resources
• HR department requires restricted access (can communicate out, limited inbound access)
• All inter-network communication must be logged and controllable
• Network access should be controlled at multiple layers
R6 — Scalability and Redundancy
• Network design must support future growth (50% expansion)
• Single points of failure should be minimized where possible