Static Routes Lab
Foundation Network with Multi-Layer Topology
90 minutes
Beginner
Packet Tracer
Lab Progress
0 / 8 sections
1
Objectives & Topology
10 minutes
Learning Objectives: Build a multi-layer network topology, configure IP addresses, implement static routes, and verify end-to-end connectivity.
Network Topology
[Internet - Simulated]
|
[Edge-Router]
(1.1.1.1)
|
10.0.0.0/30 (P2P)
|
+------------------+------------------+
| |
[Core-SW1] [Core-SW2]
(1.1.2.2) (1.1.3.3)
| |
+---+---+ +---+---+
| | | |
[Dist-SW1][Dist-SW2] [Dist-SW3][Dist-SW4]
(1.1.4.4) (1.1.5.5) (1.1.6.6) (1.1.7.7)
| | | |
[Acc-SW1][Acc-SW2] [Acc-SW3][Acc-SW4]
| | | |
PC1-2 PC3-4 Server1-2 Server3-4
Required Equipment
Routers
1x Router (1841, 2811, or 2901)
L3 Switches
6x Layer 3 (3560)
L2 Switches
4x Layer 2 (2960)
End Devices
4x PCs + 4x Servers
Tasks
- Review the topology diagram and identify all layers
- List all devices needed for this lab
- Identify the path a packet takes from PC1 to Server1
2
IP Addressing Scheme
10 minutes
Loopback Addresses (Router IDs)
| Device | Loopback0 | Purpose |
|---|---|---|
| Edge-Router | 1.1.1.1/32 |
Router ID |
| Core-SW1 | 1.1.2.2/32 |
Router ID |
| Core-SW2 | 1.1.3.3/32 |
Router ID |
| Dist-SW1 | 1.1.4.4/32 |
Router ID |
| Dist-SW2 | 1.1.5.5/32 |
Router ID |
| Dist-SW3 | 1.1.6.6/32 |
Router ID |
| Dist-SW4 | 1.1.7.7/32 |
Router ID |
Point-to-Point Links (/30 Networks)
| Link | Network | Device 1 IP | Device 2 IP |
|---|---|---|---|
| Edge ↔ Core-SW1 | 10.0.0.0/30 |
10.0.0.1 | 10.0.0.2 |
| Edge ↔ Core-SW2 | 10.0.1.0/30 |
10.0.1.1 | 10.0.1.2 |
| Core-SW1 ↔ Dist-SW1 | 10.0.2.0/30 |
10.0.2.1 | 10.0.2.2 |
| Core-SW1 ↔ Dist-SW2 | 10.0.3.0/30 |
10.0.3.1 | 10.0.3.2 |
| Core-SW2 ↔ Dist-SW3 | 10.0.4.0/30 |
10.0.4.1 | 10.0.4.2 |
| Core-SW2 ↔ Dist-SW4 | 10.0.5.0/30 |
10.0.5.1 | 10.0.5.2 |
Why /30 subnets? Point-to-point links only need 2 usable IPs. A /30 provides exactly 2 host addresses (and 1 network + 1 broadcast). This conserves IP space in enterprise networks.
End Device Networks
| Network | Subnet | Gateway | Connected To |
|---|---|---|---|
| Sales | 192.168.10.0/24 |
192.168.10.1 | Dist-SW1 |
| Engineering | 192.168.20.0/24 |
192.168.20.1 | Dist-SW2 |
| Servers | 192.168.30.0/24 |
192.168.30.1 | Dist-SW3 |
| Management | 192.168.40.0/24 |
192.168.40.1 | Dist-SW4 |
Tasks
- Identify all /30 subnets and their usable IP addresses
- Calculate the broadcast address for 10.0.0.0/30
- Understand why loopback addresses use /32 masks
3
Build Physical Topology
15 minutes
Device Placement & Naming
- Open Cisco Packet Tracer
- Add devices from the device panel
- Rename devices (Config tab → Display Name)
! Device Naming Convention:
Router → Edge-Router
Switch0 → Core-SW1
Switch1 → Core-SW2
Switch2 → Dist-SW1
Switch3 → Dist-SW2
Switch4 → Dist-SW3
Switch5 → Dist-SW4
Switch6 → Access-SW1
Switch7 → Access-SW2
Switch8 → Access-SW3
Switch9 → Access-SW4
Cable Connections
Edge Router Connections
Edge-Router GigabitEthernet0/0 → Core-SW1 GigabitEthernet0/1
Edge-Router GigabitEthernet0/1 → Core-SW2 GigabitEthernet0/1
Core to Distribution
Core-SW1 GigabitEthernet0/2 → Dist-SW1 GigabitEthernet0/1
Core-SW1 GigabitEthernet0/3 → Dist-SW2 GigabitEthernet0/1
Core-SW2 GigabitEthernet0/2 → Dist-SW3 GigabitEthernet0/1
Core-SW2 GigabitEthernet0/3 → Dist-SW4 GigabitEthernet0/1
Distribution to Access
Dist-SW1 GigabitEthernet0/2 → Access-SW1 GigabitEthernet0/1
Dist-SW2 GigabitEthernet0/2 → Access-SW2 GigabitEthernet0/1
Dist-SW3 GigabitEthernet0/2 → Access-SW3 GigabitEthernet0/1
Dist-SW4 GigabitEthernet0/2 → Access-SW4 GigabitEthernet0/1
Access to End Devices
Access-SW1 FastEthernet0/1 → PC1 FastEthernet0
Access-SW1 FastEthernet0/2 → PC2 FastEthernet0
Access-SW2 FastEthernet0/1 → PC3 FastEthernet0
Access-SW2 FastEthernet0/2 → PC4 FastEthernet0
Access-SW3 FastEthernet0/1 → Server1 FastEthernet0
Access-SW3 FastEthernet0/2 → Server2 FastEthernet0
Access-SW4 FastEthernet0/1 → Server3 FastEthernet0
Access-SW4 FastEthernet0/2 → Server4 FastEthernet0
Tasks
- Add all 11 network devices to Packet Tracer
- Rename all devices according to the naming convention
- Add 4 PCs and 4 Servers
- Connect all cables (verify green link lights)
4
Configure Edge Router
10 minutes
Basic Configuration
Router> enable
Router# configure terminal
! Set hostname
Router(config)# hostname Edge-Router
! Create loopback for Router ID
Edge-Router(config)# interface Loopback0
Edge-Router(config-if)# ip address 1.1.1.1 255.255.255.255
Edge-Router(config-if)# description Router ID
Edge-Router(config-if)# exit
! Configure interface to Core-SW1
Edge-Router(config)# interface GigabitEthernet0/0
Edge-Router(config-if)# ip address 10.0.0.1 255.255.255.252
Edge-Router(config-if)# description Link to Core-SW1
Edge-Router(config-if)# no shutdown
Edge-Router(config-if)# exit
! Configure interface to Core-SW2
Edge-Router(config)# interface GigabitEthernet0/1
Edge-Router(config-if)# ip address 10.0.1.1 255.255.255.252
Edge-Router(config-if)# description Link to Core-SW2
Edge-Router(config-if)# no shutdown
Edge-Router(config-if)# exit
! Save configuration
Edge-Router(config)# exit
Edge-Router# copy running-config startup-config
Verification
Edge-Router# show ip interface brief
Expected Output:
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 10.0.0.1 YES manual up up
GigabitEthernet0/1 10.0.1.1 YES manual up up
Loopback0 1.1.1.1 YES manual up up
Tasks
- Configure hostname as Edge-Router
- Create Loopback0 with IP 1.1.1.1/32
- Configure Gi0/0 with 10.0.0.1/30
- Configure Gi0/1 with 10.0.1.1/30
- Verify interfaces are up/up with show ip interface brief
5
Configure Core & Distribution
20 minutes
Core-SW1 Configuration
Switch> enable
Switch# configure terminal
Switch(config)# hostname Core-SW1
Core-SW1(config)# ip routing ! Enable Layer 3
Core-SW1(config)# interface Loopback0
Core-SW1(config-if)# ip address 1.1.2.2 255.255.255.255
Core-SW1(config-if)# exit
Core-SW1(config)# interface GigabitEthernet0/1
Core-SW1(config-if)# no switchport ! Convert to routed port
Core-SW1(config-if)# ip address 10.0.0.2 255.255.255.252
Core-SW1(config-if)# no shutdown
Core-SW1(config-if)# exit
Core-SW1(config)# interface GigabitEthernet0/2
Core-SW1(config-if)# no switchport
Core-SW1(config-if)# ip address 10.0.2.1 255.255.255.252
Core-SW1(config-if)# no shutdown
Core-SW1(config-if)# exit
Core-SW1(config)# interface GigabitEthernet0/3
Core-SW1(config-if)# no switchport
Core-SW1(config-if)# ip address 10.0.3.1 255.255.255.252
Core-SW1(config-if)# no shutdown
Core-SW1(config-if)# exit
Core-SW1# copy running-config startup-config
no switchport: This command converts a switch port from Layer 2 (switching) to Layer 3 (routing). Required on multilayer switches for routed interfaces.
Core-SW2 Configuration (Click to expand)
Switch(config)# hostname Core-SW2
Core-SW2(config)# ip routing
Core-SW2(config)# interface Loopback0
Core-SW2(config-if)# ip address 1.1.3.3 255.255.255.255
Core-SW2(config)# interface GigabitEthernet0/1
Core-SW2(config-if)# no switchport
Core-SW2(config-if)# ip address 10.0.1.2 255.255.255.252
Core-SW2(config)# interface GigabitEthernet0/2
Core-SW2(config-if)# no switchport
Core-SW2(config-if)# ip address 10.0.4.1 255.255.255.252
Core-SW2(config)# interface GigabitEthernet0/3
Core-SW2(config-if)# no switchport
Core-SW2(config-if)# ip address 10.0.5.1 255.255.255.252
Distribution Switch Configurations (Click to expand)
Dist-SW1: Loopback 1.1.4.4, Gi0/1: 10.0.2.2, VLAN1: 192.168.10.1
Dist-SW2: Loopback 1.1.5.5, Gi0/1: 10.0.3.2, VLAN1: 192.168.20.1
Dist-SW3: Loopback 1.1.6.6, Gi0/1: 10.0.4.2, VLAN1: 192.168.30.1
Dist-SW4: Loopback 1.1.7.7, Gi0/1: 10.0.5.2, VLAN1: 192.168.40.1
! Example for Dist-SW1:
Dist-SW1(config)# ip routing
Dist-SW1(config)# interface Vlan1
Dist-SW1(config-if)# ip address 192.168.10.1 255.255.255.0
Dist-SW1(config-if)# no shutdown
Tasks
- Configure Core-SW1 with all interfaces
- Configure Core-SW2 with all interfaces
- Configure all 4 Distribution switches with SVIs
- Enable ip routing on all Layer 3 switches
- Save configuration on all switches
6
Configure End Devices
10 minutes
PC Configuration
Click on each PC → Desktop tab → IP Configuration:
| Device | IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|
| PC1 | 192.168.10.10 |
255.255.255.0 | 192.168.10.1 |
| PC2 | 192.168.10.20 |
255.255.255.0 | 192.168.10.1 |
| PC3 | 192.168.20.10 |
255.255.255.0 | 192.168.20.1 |
| PC4 | 192.168.20.20 |
255.255.255.0 | 192.168.20.1 |
Server Configuration
| Device | IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|
| Server1 | 192.168.30.10 |
255.255.255.0 | 192.168.30.1 |
| Server2 | 192.168.30.20 |
255.255.255.0 | 192.168.30.1 |
| Server3 | 192.168.40.10 |
255.255.255.0 | 192.168.40.1 |
| Server4 | 192.168.40.20 |
255.255.255.0 | 192.168.40.1 |
Tasks
- Configure IP on all 4 PCs
- Configure IP on all 4 Servers
- Set correct default gateway on each device
- Verify with ipconfig command on each PC
7
Configure Static Routes
15 minutes
Key Concept: Static routes tell routers how to reach networks they don't directly connect to. The format is:
ip route [destination-network] [mask] [next-hop-ip]
Edge Router Static Routes
Edge-Router(config)# ip route 192.168.10.0 255.255.255.0 10.0.0.2
Edge-Router(config)# ip route 192.168.20.0 255.255.255.0 10.0.0.2
Edge-Router(config)# ip route 192.168.30.0 255.255.255.0 10.0.1.2
Edge-Router(config)# ip route 192.168.40.0 255.255.255.0 10.0.1.2
Core Switch Static Routes
! Core-SW1:
Core-SW1(config)# ip route 192.168.10.0 255.255.255.0 10.0.2.2
Core-SW1(config)# ip route 192.168.20.0 255.255.255.0 10.0.3.2
Core-SW1(config)# ip route 192.168.30.0 255.255.255.0 10.0.0.1
Core-SW1(config)# ip route 192.168.40.0 255.255.255.0 10.0.0.1
! Core-SW2:
Core-SW2(config)# ip route 192.168.10.0 255.255.255.0 10.0.1.1
Core-SW2(config)# ip route 192.168.20.0 255.255.255.0 10.0.1.1
Core-SW2(config)# ip route 192.168.30.0 255.255.255.0 10.0.4.2
Core-SW2(config)# ip route 192.168.40.0 255.255.255.0 10.0.5.2
Distribution Switch Default Routes
! Each distribution switch uses a default route to its core:
Dist-SW1(config)# ip route 0.0.0.0 0.0.0.0 10.0.2.1
Dist-SW2(config)# ip route 0.0.0.0 0.0.0.0 10.0.3.1
Dist-SW3(config)# ip route 0.0.0.0 0.0.0.0 10.0.4.1
Dist-SW4(config)# ip route 0.0.0.0 0.0.0.0 10.0.5.1
Default Route (0.0.0.0/0): The "gateway of last resort" - matches any destination not explicitly in the routing table. Distribution switches use this to send all traffic "up" to their core switch.
Tasks
- Add 4 static routes on Edge-Router
- Add 4 static routes on Core-SW1
- Add 4 static routes on Core-SW2
- Add default route on all 4 Distribution switches
- Save configuration on all devices
8
Verification & Testing
10 minutes
Verify Routing Tables
Edge-Router# show ip route
Expected to see:
C 1.1.1.1 is directly connected, Loopback0
C 10.0.0.0/30 is directly connected, GigabitEthernet0/0
C 10.0.1.0/30 is directly connected, GigabitEthernet0/1
S 192.168.10.0/24 [1/0] via 10.0.0.2
S 192.168.20.0/24 [1/0] via 10.0.0.2
S 192.168.30.0/24 [1/0] via 10.0.1.2
S 192.168.40.0/24 [1/0] via 10.0.1.2
Legend: C = Connected, S = Static, [1/0] = Admin Distance / Metric
Connectivity Tests
| From | To | Command | Expected |
|---|---|---|---|
| PC1 | Gateway | ping 192.168.10.1 |
Success |
| PC1 | PC2 (same net) | ping 192.168.10.20 |
Success |
| PC1 | PC3 (diff net) | ping 192.168.20.10 |
Success |
| PC1 | Server1 | ping 192.168.30.10 |
Success |
! Trace the path from PC1 to Server1:
PC1> tracert 192.168.30.10
Expected hops:
1 192.168.10.1 (Dist-SW1)
2 10.0.2.1 (Core-SW1)
3 10.0.0.1 (Edge-Router)
4 10.0.1.2 (Core-SW2)
5 192.168.30.10 (Server1)
Final Verification Checklist
- All interfaces show up/up status
- Routing tables show expected static routes
- PC1 can ping all other end devices
- Traceroute shows correct path
- Configuration saved on all devices
Reflection Questions
- Why do we need static routes? What happens without them?
- What's the difference between directly connected (C) and static (S) routes?
- Why do distribution switches use default routes instead of specific routes?
- How many hops does PC1 → Server1 take? Is this optimal?