FAKULTI TEKNOLOGI DAN KEJURUTERAAN

ELEKTRONIK DAN KOMPUTER

UNIVERSITI TEKNIKAL MALAYSIA MELAKA

DATA COMMUNICATION AND NETWORKING

BERT 2324 SEMESTER 2 SESI 2023/2024

LAB 5: CONFIGURING STATIC AND DYNAMIC ROUTING PROTOCOL

NO. STUDENTS' NAME MATRIC. NO.

1. ROSHA SHAHIRAH BINTI AHMAD SAFFEE B122310063

2. AINA BALQIS BINTI MUHAMMAD SYAFIQ B122310078

3. DANIA ALIESA BINTI ZULFIKAR ALI B122310127

PROGRAMME BERT 1/1

SECTION /
1/1
GROUP

DATE 20/5/2024

1. DR AHMAD FAUZAN BIN KADMIN

NAME OF
INSTRUCTOR(S)
2.

EXAMINER’S COMMENT(S) TOTAL MARKS

Rev Date Author(s) Description
.
No.

1.0 3 Feb 1. Gloria Raymond 1. Update to new UTeM logo

2020 Tanny 2. Update faculty's name
3. Change "course" to
"programme".
4. Remove verification stamp.

2.0 22 Jan 1. Nurulhalim Bin 1. Change content to reflect the

2021 Hassim use of Packet Tracer
simulation during Covid-19
remote learning mode.

3.0 15 1. Ahmad Fauzan Bin 1. Change the content to

March Kadmin laboratory hands-on for in-lab
2023 2. Nurulhalim Bin training.
Hasim
3. Gloria Raymond
Tanny
 Lab 5.1 - Configuring IPv4 Static and Default Routes
Topology

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

R1 G0/1 192.168.0.1 255.255.255.0 N/A

S0/0/1 10.1.1.1 255.255.255.252 N/A
R3 G0/1 192.168.1.1 255.255.255.0 N/A
S0/0/0 (DCE) 10.1.1.2 255.255.255.252 N/A
Lo0 209.165.200.225 255.255.255.224 N/A
Lo1 198.133.219.1 255.255.255.0 N/A
PC-A NIC 192.168.0.10 255.255.255.0 192.168.0.1
PC-C NIC 192.168.1.10 255.255.255.0 192.168.1.1

Objectives
Part 1: Set Up the Topology
Part 2: Configure Basic Device Settings and Verify Connectivity
Part 3: Configure Static Routes
 Configure a recursive static route.
 Configure a directly connected static route.
 Configure and remove static routes.
Part 4: Configure and Verify a Default Route

3
 Background / Scenario
A router uses a routing table to determine where to send packets. The routing table contains a set
of routes that describe which gateway or interface the router uses to reach a specified network.
Initially, the routing table contains only directly connected networks. To communicate with distant
networks, routes must be specified and added to the routing table.
In this lab, you will manually configure a static route to a specified distant network based on a next-
hop IP address or exit interface. You will also configure a static default route. A default route is a
type of static route that specifies a gateway to use when the routing table does not contain a path for
the destination network.
Note: The routers used with CCNA hands-on labs are Cisco 1941 Integrated Services Routers
(ISRs) with Cisco IOS Release 15.2(4) M3 (universalk9 image). The switches used are Cisco
Catalyst 2960s with Cisco IOS Release 15.0(2) (lanbasek9 image). Other routers, switches and
Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the commands
available and output produced might vary from what is shown in the labs. Refer to the Router
Interface Summary Table at this end of the lab for the correct interface identifiers.

Required Resources
Packet Tracer with the following equipment:
 2 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
 2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
 2 PCs ( with terminal emulation)
 Console cables to configure the Cisco IOS devices via the console ports
 Ethernet and serial cables as shown in the topology

Part 1: Set Up the Topology

Step 1: Cable the network as shown in the topology.

Part 2: Configure Basic Device Settings and Verify Connectivity

In Part 2, you will configure basic settings, such as the interface IP addresses, device access, and
passwords. You will verify LAN connectivity and identify routes listed in the routing tables for R1 and
R3.

Step 1: Configure the PC interfaces.

Step 2: Configure basic settings on the routers.

a. Configure device names, as shown in the Topology and Addressing Table.
b. Disable DNS lookup.
c. Assign class as the enable password and assign cisco as the console and vty password.
d. Save the running configuration to the startup configuration file.

4
Step 3: Configure IP settings on the routers.
a. Configure the R1 and R3 interfaces with IP addresses according to the Addressing Table.
b. The S0/0/0 connection is the DCE connection and requires the clock rate command. The R3
S0/0/0 configuration is displayed below.
R3(config)# interface s0/0/0
R3(config-if)# clock rate 128000

Step 4: Verify connectivity of the LANs.

a. Test connectivity by pinging from each PC to the default gateway that has been configured for
that host.

Figure 1: Verify connectivity by using the ping command from PC-A to its default gateway.

From PC-A, is it possible to ping the default gateway? = Yes

Figure 2: Verify connectivity by using the ping command from PC-C to its default gateway.

From PC-C, is it possible to ping the default gateway? = Yes

If the answer is no to any of these questions, troubleshoot the configurations and correct the
error.

5
 b. Test connectivity by pinging between the directly connected routers.

Figure 3: Verify connectivity by using the ping command from R1 to the S0/0/0 interface of R3.

From R1, is it possible to ping the S0/0/0 interface of R3? __________

If the answer is no to any of these questions, troubleshoot the configurations and correct the
error.

c. Test connectivity between devices that are not directly connected.

Figure 4: Verify connectivity by using the ping command from PC-A to PC-C, Lo0 & Lo1.

From PC-A, is it possible to ping PC-C? = NO

From PC-A, is it possible to ping Lo0? =NO
From PC-A, is it possible to ping Lo1? = NO
Were these pings successful? Why or why not?

6
= Router does not contain routes to distant networks

Step 5: Gather information.

a. Check the status of the interfaces on R1 with the show ip interface brief command.

Figure 5: Status of the interfaces on R1.

How many interfaces are activated on R1? = Two

b. Check the status of the interfaces on R3.

Figure 6: Status of the interfaces on R1.

How many interfaces are activated on R3? = Four

7
 c. View the routing table information for R1 using the show ip route command.

Figure 7: Routing table information for R1.

What networks are present in the Addressing Table of this lab, but not in the routing table for
R1?
192.168.1.0 , 198.133.219.0 , 209.165.200.224
d. View the routing table information for R3.

Figure 8: Routing table information for R3.

8
 What networks are present in the Addressing Table in this lab, but not in the routing table for
R3?
= 192.168.0.0
Why are all the networks not in the routing tables for each of the routers?
= Because the router are not configured with static or dynamic routing.

Part 3: Configure Static Routes

In Part 3, you will employ multiple ways to implement static and default routes, you will confirm that
the routes have been added to the routing tables of R1 and R3, and you will verify connectivity
based on the introduced routes.
Note: This lab provides minimal assistance with the actual commands necessary to configure static
routing. However, the required commands are provided in Appendix C. Test your knowledge by
trying to configure the devices without referring to the appendix.

Step 1: Configure a recursive static route.

With a recursive static route, the next-hop IP address is specified. Because only the next-hop IP
is specified, the router must perform multiple lookups in the routing table before forwarding packets.
To configure recursive static routes, use the following syntax:
Router(config)# ip route network-address subnet-mask ip-address
a. On the R1 router, configure a static route to the 192.168.1.0 network using the IP address of
the Serial 0/0/0 interface of R3 as the next-hop address. Write the command you used in the
space provided.
= R1(config)# ip route 192..168.1.0 255.255.255.0 10.1.1.2
b. View the routing table to verify the new static route entry.

Figure 9: Routing table information for R1 to verify new static route entry (recursive static route).

How is this new route listed in the routing table?

From host PC-A, is it possible to ping the host PC-C? = NO

These pings should fail. If the recursive static route is correctly configured, the ping arrives at
PC-C. PC-C sends a ping reply back to PC-A. However, the ping reply is discarded at R3
because R3 does not have a return route to the 192.168.0.0 network in the routing table.

9
Step 2: Configure a directly connected static route.
With a directly connected static route, the exit-interface parameter is specified, which allows the
router to resolve a forwarding decision in one lookup. A directly connected static route is typically
used with a point-to-point serial interface. To configure directly connected static routes with an exit
interface specified, use the following syntax:
Router(config)# ip route network-address subnet-mask exit-intf
a. On the R3 router, configure a static route to the 192.168.0.0 network using S0/0/0 as the exit
interface. Write the command you used in the space provided.
= R3(config)# ip route 192.168.0.0 255.255.255.0 s0/0/0
b. View the routing table to verify the new static route entry.

Figure 10: Routing table information for R3 to verify new static route entry (directly connected static
route).

How is this new route listed in the routing table?

= S 192.168.0.0/24 is directly connected, serial0/01
c. From host PC-A, is it possible to ping the host PC-C? = YES
This ping should be successful.

Step 3: Configure a static route.

a. On the R1 router, configure a static route to the 198.133.219.0 network using one of the static
route configuration options from the previous steps. Write the command you used in the space
provided.
= R1(config)# ip route 198.133.219.0 255.255.255.0 10.1.1.2
b. On the R1 router, configure a static route to the 209.165.200.224 network on R3 using the
other static route configuration option from the previous steps. Write the command you used in
the space provided.
= R1(config)# ip route 209.165.200.224 255.255.255.224 10.1.1.2

10
 c. View the routing table to verify the new static route entry.

Figure 11: Routing table information for R1 to verify new static route entry.

How is this new route listed in the routing table?

= S 198.133.219.0/24 [1/0] via 10.1.1.2
d. From host PC-A, is it possible to ping the R1 address 198.133.219.1? = YES
This ping should be successful.

Step 4: Remove static routes for loopback addresses.

a. On R1, use the no command to remove the static routes for the two loopback addresses from
the routing table. Write the commands you used in the space provided.
= R1(config)# no ip route 209.165.200.224 255.255.255.224
R1(config)# no ip route 198.133.219.0 255.255.255.0
b. View the routing table to verify the routes have been removed.

Figure 12: Routing table information for R1 to verify the routes have been removed.

How many network routes are listed in the routing table on R1? = Three
Is the Gateway of last resort set? = NO

11
Part 4: Configure and Verify a Default Route
In Part 4, you will implement a default route, confirm that the route has been added to the routing
table, and verify connectivity based on the introduced route.
A default route identifies the gateway to which the router sends all IP packets for which it does
not have a learned or static route. A default static route is a static route with 0.0.0.0 as the
destination IP address and subnet mask. This is commonly referred to as a “quad zero” route.
In a default route, either the next-hop IP address or exit interface can be specified. To configure a
default static route, use the following syntax:
Router(config)# ip route 0.0.0.0 0.0.0.0 {ip-address or exit-intf}
a. Configure the R1 router with a default route using the exit interface of S0/0/1. Write the
command you used in the space provided.
= R1(config)# ip route 0.0.0.0 0.0.0.0 s0/0/1
b. View the routing table to verify the new static route entry.

Figure 13: Routing table information for R1 to verify new static route entry (default route).

How is this new route listed in the routing table?

= S* 0.0.0.0/0 is directly connected, Serial0/0/1
What is the Gateway of last resort?
= 0.0.0.0

12
 c. From host PC-A, is it possible to ping the 209.165.200.225?

d. From host PC-A, is it possible to ping the 198.133.219.1?

Figure 14: Verify connectivity by using the ping command from PC-A to Lo0 and Lo1.

These pings should be successful.

Reflection
1. A new network 192.168.3.0/24 is connected to interface G0/0 on R1. What commands could be used
to configure a static route to that network from R3?
= Answer will vary. Ip route 192.168.3.0 255.255.255.00 10.1.1.1,
Ip route 192.168.3.0 255.255.255.0 s0/0/0
2. Is there a benefit to configuring a directly connected static route instead of a recursive static route?
= Config directly attached static route allows routing table to resolve exit interface in single search
instead of two searches as needed for recursive static route.
3. Why is it important to configure a default route on a router?
= Default route prevents the router from dropping packets to unknown destinations.

13
 Running Configuration from Router R1:
R1# show running-config

14
 Running Configuration from Router R3:
R3# show running-config

15
Lab 5.2 – Configuring Dynamic Routing Protocol (Packet
Tracer)
Topology

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

R1 G0/1 172.30.10.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.1 255.255.255.252 N/A
R2 G0/0 209.165.201.1 255.255.255.0 N/A
S0/0/0 10.1.1.2 255.255.255.252 N/A
S0/0/1 (DCE) 10.2.2.2 255.255.255.252 N/A
R3 G0/1 172.30.30.1 255.255.255.0 N/A
S0/0/1 10.2.2.1 255.255.255.252 N/A
S1 N/A VLAN 1 N/A N/A
S3 N/A VLAN 1 N/A N/A
PC-A NIC 172.30.10.3 255.255.255.0 172.30.10.1
PC-B NIC 209.165.201.2 255.255.255.0 209.165.201.1
PC-C NIC 172.30.30.3 255.255.255.0 172.30.30.1

16
17
 Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Configure and Verify RIPv2 Routing
 Configure RIPv2 on the routers and verify that it is running.
 Examine routing tables.
 Disable automatic summarization.
 Verify end-to-end connectivity.

Background / Scenario
Routing Information Protocol version 2 (RIPv2) is used for routing of IPv4 addresses in small
networks. RIPv2 is a classless, distance-vector routing protocol, as defined by RFC 1723.
Because RIPv2 is a classless routing protocol, subnet masks are included in the routing updates. By
default, RIPv2 automatically summarizes networks at major network boundaries. When automatic
summarization has been disabled, RIPv2 no longer summarizes networks to their classful address at
boundary routers.
In this lab, you will configure the network topology with RIPv2 routing, disable automatic
summarization, and use CLI commands to display, and verify RIP routing information.
Note: The routers used with CCNA hands-on labs are Cisco 1941 Integrated Services Routers
(ISRs) with Cisco IOS Release 15.2(4)M3 (universalk9 image). The switches used are Cisco
Catalyst 2960s with Cisco IOS Release 15.0(2) (lanbasek9 image). Other routers, switches, and
Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the commands
available and output produced might vary from what is shown in this lab. Refer to the Router
Interface Summary Table at the end of the lab for the correct interface identifiers.

Required Resources
 3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
 2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
 3 PCs (Windows 7, Vista, or XP with terminal emulation program, such as PuTTY)
 Console cables to configure the Cisco IOS devices via the console ports
 Ethernet and Serial cables as shown in the topology

Part 1: Build the Network and Configure Basic Device Settings

In Part 1, you will set up the network topology and configure basic settings.

Step 1: Cable the network as shown in the topology.

18
Step 2: Configure basic settings for each router and switch.
a. Disable DNS lookup.
b. Configure device names as shown in the topology.
c. Assign class as the privileged EXEC password.
d. Assign cisco as the console and vty passwords.
e. Configure a MOTD banner to warn users that unauthorized access is prohibited.
f. Configure the IP addresses listed in the Addressing Table for all interfaces.
g. Configure a description for each interface with an IP address.
h. Configure the clock rate, if applicable, to the DCE serial interface.
i. Copy the running-configuration to the startup-configuration.

Step 3: Configure PC IP Addressing.

Refer to the Addressing Table for IP address information of the PCs.

Step 4: Test connectivity.

At this point, the PCs are unable to ping each other.

Figure 15: Verify connectivity by using the ping command from PC-A to PC-C.

a. Each workstation should be able to ping the attached router. Verify and troubleshoot if
necessary.
b. The routers should be able to ping one another. Verify and troubleshoot if necessary.

19
Part 2: Configure and Verify RIPv2 Routing
In Part 2, you will configure RIPv2 routing on all routers in the network and then verify that the
routing tables are updated correctly. After RIPv2 has been verified, you will disable automatic
summarization, and verify end-to-end connectivity.

Step 1: Check status of interfaces

Check the status of the interfaces on each router with the command show ip interface brief.
Are all of the relevant interfaces on each router activated? = Yes

Step 2: View the routing table information for all routers.

View the routing table information for R1, R2 and R3 using the show ip route command.

Figure 16: Routing table information for R1.

Figure 17: Routing table information for R2.

20
 Figure 18: Routing table information for R3.

Step 3: Configure RIPv2 routing.

a. Configure RIPv2 on R1 as the routing protocol and advertise the appropriate connected
networks.
R1(config)# router rip
R1(config-router)# version 2
R1(config-router)# network 172.30.10.0
R1(config-router)# network 10.1.1.0
b. Configure RIPv2 on R2 and use the network statement to add the appropriate connected
networks.
c. Configure RIPv2 on R3 and use the network statements to add the appropriate connected
networks.

Note: The network command:

 Enables RIP on all interfaces that belong to this network. These interfaces will now both send and receive
RIP updates.
 Advertises this network in RIP routing updates sent to other routers every 30 seconds.

21
Step 4: Examine the current state of the network.
a. View the routing table to verify the new route entry for R1, R2 and R3.
Note: Routes learned through RIP are coded with an R in the routing table.

Figure 19: Routing table information for R1.

Figure 20: Routing table information for R2.

Figure 21: Routing table information for R3.

22
 b. Check connectivity between PCs.
From PC-A, is it possible to ping PC-B? =Yes
What is the success rate (in percentage %)? 100%
From PC-A, is it possible to ping PC-C? YES
What is the success rate (in percentage %)? 100%

Figure 22: Verify connectivity by using the ping command from PC-A to PC-B and PC-C.

From PC-C, is it possible to ping PC-B? YES

What is the success rate (in percentage %)? 100%
From PC-C, is it possible to ping PC-A? YES
What is the success rate (in percentage %)? 100%

23
 Figure 23: Verify connectivity by using the ping command from PC-C to PC-B and PC-A.

24
 c. Verify that RIPv2 is running on the routers.
You can use the debug ip rip, show ip protocols, and show running-config
commands to confirm that RIPv2 is running.
The show ip protocols command output for R1 is shown below.

R1# show ip protocols

Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 15 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
GigabitEthernet0/1 2 2
Serial0/0/0 2 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.30.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
10.1.1.2 120
Distance: (default is 120)

Note: The show ip protocols command can be used to view information about the routing processes that
are occurring on the router. This output can be used to verify most RIP parameters to confirm that:
 RIP routing is configured
 The correct interfaces send and receive RIP updates
 The router advertises the correct networks
 RIP neighbors are sending updates

When issuing the debug ip rip command on R1, the following information is provided to
confirm that RIPv2 is running. When you are finished observing the debugging outputs, issue the
undebug all or no debug ip rip command.

R1#debug ip rip
RIP protocol debugging is on

RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/1 (172.30.10.1)

RIP: build update entries
10.0.0.0/8 via 0.0.0.0, metric 1, tag 0
209.165.201.0/24 via 0.0.0.0, metric 2, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (10.1.1.1)
RIP: build update entries
172.30.0.0/16 via 0.0.0.0, metric 1, tag 0
RIP: received v2 update from 10.1.1.2 on Serial0/0/0
10.2.2.0/30 via 0.0.0.0 in 1 hops
209.165.201.0/24 via 0.0.0.0 in 1 hops

R1#undebug all
All possible debugging has been turned off
R1#

Note: Use the debug ip rip command to view the RIP messages being sent and received.
RIP updates are sent every 30 seconds so you may have to wait for debug information to be displayed.

25
 When issuing the show running-config command on R1, the following information is
provided to confirm that RIPv2 is running.

R1#show run
Building configuration...

Current configuration : 914 bytes

!
version 15.1
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname R1
!
!

!
interface Vlan1
no ip address
shutdown
!
router rip
version 2
network 10.0.0.0
network 172.30.0.0
!
ip classless
!
ip flow-export version 9
!
!

Step 5: Examine the automatic summarization of routes.

The LANs connected to R1 and R3 are composed of discontiguous networks. R2 displays two
equal-cost paths to the 172.30.0.0/16 network in the routing table. R2 displays only the major
classful network address of 172.30.0.0 and does not display any of the subnets for this network.
R2# show ip route
<Output omitted>
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.2/32 is directly connected, Serial0/0/0
C 10.2.2.0/30 is directly connected, Serial0/0/1
L 10.2.2.2/32 is directly connected, Serial0/0/1
R 172.30.0.0/16 [120/1] via 10.2.2.1, 00:00:23, Serial0/0/1
[120/1] via 10.1.1.1, 00:00:09, Serial0/0/0
209.165.201.0/24 is variably subnetted, 2 subnets, 2 masks
C 209.165.201.0/24 is directly connected, GigabitEthernet0/0
L 209.165.201.1/32 is directly connected, GigabitEthernet0/0

R1 displays only its own subnet for the 172.30.10.0/24 network. R1 does not have a route for the
172.30.30.0/24 subnet on R3.
R1# show ip route
<Output omitted>
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.1/32 is directly connected, Serial0/0/0
R 10.2.2.0/30 [120/1] via 10.1.1.2, 00:00:21, Serial0/0/0
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.30.10.0/24 is directly connected, GigabitEthernet0/1
L 172.30.10.1/32 is directly connected, GigabitEthernet0/1
R 209.165.201.0/24 [120/1] via 10.1.1.2, 00:00:21, Serial0/0/0

26
27
 R3 only displays its own subnet for the 172.30.30.0/24 network. R3 does not have a route for the
172.30.10.0/24 subnets on R1.
R3# show ip route
<Output omitted>
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
R 10.1.1.0/30 [120/1] via 10.2.2.2, 00:00:23, Serial0/0/1
C 10.2.2.0/30 is directly connected, Serial0/0/1
L 10.2.2.1/32 is directly connected, Serial0/0/1
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.30.30.0/24 is directly connected, GigabitEthernet0/1
L 172.30.30.1/32 is directly connected, GigabitEthernet0/1
R 209.165.201.0/24 [120/1] via 10.2.2.2, 00:00:09, Serial0/0/1

From debug ip rip command on R2, R1 and R3 is not sending any of the 172.30.0.0 subnets,
only the summarized route of 172.30.0.0, including the subnet mask (/16).

R2#debug ip rip
RIP protocol debugging is on

RIP: received v2 update from 10.2.2.1 on Serial0/0/1

172.30.0.0/16 via 0.0.0.0 in 1 hops
RIP: received v2 update from 10.1.1.1 on Serial0/0/0
172.30.0.0/16 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0 (209.165.201.1)
RIP: build update entries
10.0.0.0/8 via 0.0.0.0, metric 1, tag 0
172.30.0.0/16 via 0.0.0.0, metric 2, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (10.1.1.2)
RIP: build update entries
10.2.2.0/30 via 0.0.0.0, metric 1, tag 0
209.165.201.0/24 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/1 (10.2.2.2)
RIP: build update entries
10.1.1.0/30 via 0.0.0.0, metric 1, tag 0
209.165.201.0/24 via 0.0.0.0, metric 1, tag 0

Step 6: Disable automatic summarization.

a. The no auto-summary command is used to turn off automatic summarization in RIPv2.
Disable auto summarization on all routers. The routers will no longer summarize routes at major
classful network boundaries.
R1(config)# router rip
R1(config-router)# no auto-summary

R2(config)# router rip

R2(config-router)# no auto-summary

R3(config)# router rip

R3(config-router)# no auto-summary

28
Step 7: Examine the routing tables.
The LAN subnets connected to R1 and R3 should now be included in all three routing tables.

R2# show ip route

<Output omitted>
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.2/32 is directly connected, Serial0/0/0
C 10.2.2.0/30 is directly connected, Serial0/0/1
L 10.2.2.2/32 is directly connected, Serial0/0/1
172.30.0.0/16 is variably subnetted, 3 subnets, 2 masks
R 172.30.10.0/24 [120/1] via 10.1.1.1, 00:00:21, Serial0/0/0
R 172.30.30.0/24 [120/1] via 10.2.2.1, 00:00:04, Serial0/0/1
209.165.201.0/24 is variably subnetted, 2 subnets, 2 masks
C 209.165.201.0/24 is directly connected, GigabitEthernet0/0
L 209.165.201.1/32 is directly connected, GigabitEthernet0/0
--------------------------------------------------------------------------
R1# show ip route
<Output omitted>
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
C 10.1.1.0/30 is directly connected, Serial0/0/0
L 10.1.1.1/32 is directly connected, Serial0/0/0
R 10.2.2.0/30 [120/1] via 10.1.1.2, 00:00:12, Serial0/0/0
172.30.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.30.10.0/24 is directly connected, GigabitEthernet0/1
L 172.30.10.1/32 is directly connected, GigabitEthernet0/1
R 172.30.30.0/24 [120/2] via 10.1.1.2, 00:00:12, Serial0/0/0
R 209.165.201.0/24 [120/1] via 10.1.1.2, 00:00:21, Serial0/0/0

--------------------------------------------------------------------------
R3# show ip route
<Output omitted>
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
R 10.1.1.0/30 [120/1] via 10.2.2.2, 00:00:23, Serial0/0/1
C 10.2.2.0/30 is directly connected, Serial0/0/1
L 10.2.2.1/32 is directly connected, Serial0/0/1
172.30.0.0/16 is variably subnetted, 2 subnets, 2 masks
R 172.30.10.0/24 [120/2] via 10.2.2.2, 00:00:16, Serial0/0/1
C 172.30.30.0/24 is directly connected, GigabitEthernet0/1
L 172.30.30.1/32 is directly connected, GigabitEthernet0/1
R 209.165.201.0/24 [120/1] via 10.2.2.2, 00:00:09, Serial0/0/1

29
 a. Use the debug ip rip command on R2 to examine the RIP updates.
R2#debug ip rip
RIP protocol debugging is on

RIP: received v2 update from 10.2.2.1 on Serial0/0/1

172.30.30.0/24 via 0.0.0.0 in 1 hops
RIP: received v2 update from 10.1.1.1 on Serial0/0/0
172.30.10.0/24 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via GigabitEthernet0/0 (209.165.201.1)
RIP: build update entries
10.1.1.0/30 via 0.0.0.0, metric 1, tag 0
10.2.2.0/30 via 0.0.0.0, metric 1, tag 0
172.30.10.0/24 via 0.0.0.0, metric 2, tag 0
172.30.30.0/24 via 0.0.0.0, metric 2, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (10.1.1.2)
RIP: build update entries
10.2.2.0/30 via 0.0.0.0, metric 1, tag 0
172.30.30.0/24 via 0.0.0.0, metric 2, tag 0
209.165.201.0/24 via 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/0/1 (10.2.2.2)
RIP: build update entries
10.1.1.0/30 via 0.0.0.0, metric 1, tag 0
172.30.10.0/24 via 0.0.0.0, metric 2, tag 0
209.165.201.0/24 via 0.0.0.0, metric 1, tag 0

Step 8: Verify connectivity.

a. Simulate sending traffic to the PC-B by pinging from PC-A and PC-C to 209.165.201.2.
Were the pings successful? = YES

Figure 24: Verify connectivity by using the ping command from PC-A to PC-B.

Figure 25: Verify connectivity by using the ping command from PC- to PC-B.

b. Verify that hosts within the subnetted network can reach each other by pinging between PC-A
and PC-C.
Were the pings successful? = YES

30
 Figure 26: Verify connectivity by using the ping command from PC-A to PC-C.

Reflection
1. Why would you turn off automatic summarization for RIPv2?
=So the router will no longer summarize router at major classful network boundaries

31
 Running Configuration from Router R1:
R1# show running-config

32
33
 Running Configuration from Router R2:
R2# show running-config

34
 Running Configuration from Router R3:
R3# show running-config

35
 Router Interface Summary Table

Router Interface Summary

Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2

1800 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(F0/0) (F0/1)
1900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
2801 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
(F0/0) (F0/1)
2811 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(F0/0) (F0/1)
2900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
Note: To find out how the router is configured, look at the interfaces to identify the router type and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router
class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.
The table does not include any other type of interface, even though a specific router may contain one. An
example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be
used in Cisco IOS commands to represent the interface.

36
Appendix A: Initializing and Reloading a Router

Step 1: Connect to the router.

Console into the router and enter privileged EXEC mode using the enable command.
Router> enable
Router#

Step 2: Erase the startup configuration file from NVRAM.

Type the erase startup-config command to remove the startup configuration from nonvolatile
random-access memory (NVRAM).
Router# erase startup-config
Erasing the nvram filesystem will remove all configuration files! Continue?
[confirm]
[OK]
Erase of nvram: complete
Router#

Step 3: Reload the router.

Issue the reload command to remove an old configuration from memory. When prompted to
Proceed with reload, press Enter to confirm the reload. Pressing any other key will abort the reload.
Router# reload
Proceed with reload? [confirm]

*Nov 29 18:28:09.923: %SYS-5-RELOAD: Reload requested by console. Reload

Reason: Reload Command.

Note: You may receive a prompt to save the running configuration prior to reloading the router.
Respond by typing no and press Enter.
System configuration has been modified. Save? [yes/no]: no

Step 4: Bypass the initial configuration dialog.

After the router reloads, you are prompted to enter the initial configuration dialog. Enter no and press
Enter.
Would you like to enter the initial configuration dialog? [yes/no]: no

Step 5: Terminate the autoinstall program.

You will be prompted to terminate the autoinstall program. Respond yes and then press Enter.
Would you like to terminate autoinstall? [yes]: yes
Router>

37
Appendix B: Initializing and Reloading a Switch

Step 1: Connect to the switch.

Console into the switch and enter privileged EXEC mode.
Switch> enable
Switch#

Step 2: Determine if there have been any virtual local-area networks (VLANs) created.
Use the show flash command to determine if any VLANs have been created on the switch.
Switch# show flash

Directory of flash:/

2 -rwx 1919 Mar 1 1993 00:06:33 +00:00 private-config.text

3 -rwx 1632 Mar 1 1993 00:06:33 +00:00 config.text
4 -rwx 13336 Mar 1 1993 00:06:33 +00:00 multiple-fs
5 -rwx 11607161 Mar 1 1993 02:37:06 +00:00 c2960-lanbasek9-mz.150-
2.SE.bin
6 -rwx 616 Mar 1 1993 00:07:13 +00:00 vlan.dat

32514048 bytes total (20886528 bytes free)

Switch#

Step 3: Delete the VLAN file.

a. If the vlan.dat file was found in flash, then delete this file.
Switch# delete vlan.dat
Delete filename [vlan.dat]?

You will be prompted to verify the file name. At this point, you can change the file name or just
press Enter if you have entered the name correctly.
b. When you are prompted to delete this file, press Enter to confirm the deletion. (Pressing any
other key will abort the deletion.)
Delete flash:/vlan.dat? [confirm]
Switch#

Step 4: Erase the startup configuration file.

Use the erase startup-config command to erase the startup configuration file from NVRAM. When
you are prompted to remove the configuration file, press Enter to confirm the erase. (Pressing any
other key will abort the operation.)
Switch# erase startup-config
Erasing the nvram filesystem will remove all configuration files! Continue?
[confirm]
[OK]
Erase of nvram: complete
Switch#

38
Step 5: Reload the switch.
Reload the switch to remove any old configuration information from memory. When you are
prompted to reload the switch, press Enter to proceed with the reload. (Pressing any other key will
abort the reload.)
Switch# reload
Proceed with reload? [confirm]

Note: You may receive a prompt to save the running configuration prior to reloading the switch.
Type no and press Enter.
System configuration has been modified. Save? [yes/no]: no

Step 6: Bypass the initial configuration dialog.

After the switch reloads, you should see a prompt to enter the initial configuration dialog. Type no at
the prompt and press Enter.
Would you like to enter the initial configuration dialog? [yes/no]: no
Switch>

39
 Appendix C: Configuration Commands for Lab 4-1 Parts 2, 3, and 4
The commands listed in Appendix A are for reference only. This Appendix does not include all the
specific commands necessary to complete this lab.

Basic Device Settings

Configure IP settings on the router.
R3(config)# interface s0/0/0
R3(config-if)# ip address 10.1.1.2 255.255.255.252
R3(config-if)# clock rate 128000
R3(config-if)# no shutdown

Static Route Configurations

Configure a recursive static route.
R1(config)# ip route 192.168.1.0 255.255.255.0 10.1.1.2
Configure a directly connected static route.
R3(config)# ip route 192.168.0.0 255.255.255.0 s0/0/0
Remove static routes.
R1(config)# no ip route 209.165.200.224 255.255.255.224 serial0/0/1
or
R1(config)# no ip route 209.165.200.224 255.255.255.224 10.1.1.2
or
R1(config)# no ip route 209.165.200.224 255.255.255.224

Default Route Configuration

R1(config)# ip route 0.0.0.0 0.0.0.0 s0/0/1

40