Static Routing Configuration For CCNA Students by Eng. Abeer Hosni
Static Routing Configuration For CCNA Students by Eng. Abeer Hosni
Static Routing
Configuration for
CCNA Students
By
Eng. Abeer Hosni
Lab1 (IPV4 static routing)
Objectives:
• Configure the network shown above so that PC1 can reach all other PCs in the
network using static routing.
• If you configure R1 to use its exit interface, figure out why this is not the
preferred way.
Configuration:
PC1> ip 10.0.0.100 255.255.255.0 10.0.0.1
PC2> ip 12.0.0.100 255.255.255.0 12.0.0.2
R1(config)#int f0/0
R1(config-if)#no shutdown
R1(config)#int f0/0
R1(config-if)#int f1/0
R2(config)#int f0/0
R2(config-if)#no shutdown
R2(config-if)#int f1/0
R2(config-if)#no shutdown
The network is not yet pingable since we haven’t configured static routing yet.
*10.0.0.1 icmp_seq=2 ttl=255 time=10.226 ms (ICMP type:3, code:1, Destination host unreachable)
*10.0.0.1 icmp_seq=3 ttl=255 time=10.247 ms (ICMP type:3, code:1, Destination host unreachable)
*10.0.0.1 icmp_seq=4 ttl=255 time=11.181 ms (ICMP type:3, code:1, Destination host unreachable)
*10.0.0.1 icmp_seq=5 ttl=255 time=9.350 ms (ICMP type:3, code:1, Destination host unreachable)
Since this is a broadcast network, in IPv4 it’s recommended to use next hop IP address instead of the
router exit interface.
The network is still not pingable since R2 doesn’t have a route back to the 10.0.0.0/24 network.
Verification:
R1#show ip route
<Output omitted>
R2#show ip route
<Output omitted>
R1#show arp
Protocol Address Age (min) Hardware Addr Type Interface
R1#show arp
Protocol Address Age (min) Hardware Addr Type Interface
R1 will ARP for each destination IP we want to reach using the next hop MAC address.
Objective:
Add loopback interfaces to R2, and then configure R1 to reach those interfaces in only one step.
Configuration:
R2(config)#int loopback 0
R2(config-if)#int loopback 1
R2(config-if)#int loopback 2
Verification:
R1#show ip route
<Output omitted>
R2#show ip route
<Output omitted>
Objectives:
Configure this network using static and default routes to be a pingable one.
Configuration:
R1(config)#int f0/0
R1(config-if)#no shutdown
R1(config-if)#int loopback 1
R2(config)#int f1/0
R2(config-if)#no shutdown
R2(config-if)#int f0/0
R2(config-if)#no shutdown
R3(config)#int f1/0
R3(config-if)#ip address 11.0.0.2 255.255.255.252
R3(config-if)#no shutdown
R3(config-if)#int loopback 3
Verification:
R1#show ip route static
<Output omitted>
<Output omitted>
!!!!!
Objective:
Configure R1 to reach the 2.2.2.2/32 network using its f1/0 interface. If it is down, R1 should use its
f0/0 interface to reach the network until the f1/0 interface is up again. Use static route configuration
to accomplish that.
Configuration:
R1(config)#int f0/0
R1(config-if)#no shutdown
R1(config-if)#int f1/0
R1(config-if)#no shut
R1(config-if)#int loopback 1
R2(config-if)#no shutdown
R2(config-if)#int f1/0
R2(config-if)#no shutdown
R2(config-if)#int loop 2
Verification:
R1#show run | include ip route ip route
2.2.2.2 255.255.255.255 11.0.0.2 ip route
2.2.2.2 255.255.255.255 10.0.0.2 5
* 11.0.0.2
!!!!!
R1(config)#int f1/0
R1(config-if)#shutdown
R1(config-if)#do show ip route 2.2.2.2
Routing entry for 2.2.2.2/32
* 10.0.0.2
Route metric is 0, traffic share count is 1
R1(config-if)#no shutdown
Routing entry for 2.2.2.2/32
* 11.0.0.2
Route metric is 0, traffic share count is 1
Hint:
The route back from R2 to R1 doesn’t have to be the same path that R1 takes to reach the
1.1.1.1/32 network.
Best Wishes
Abeer