REPORT PROJECT

DITS3623 NETWORK ROUTING

NAME : MUHAMMAD HAZIM BIN AMRAN

MATRIC NUMBER : D031910241

SECTION : S2G1
PROJECT : 16.3.2 LAB – TROUBLESHOOTING IPV4 AND IPV6 STATIC AND DEFAULT ROUTES
LECTURER : PN. KHADIJAH BINTI WAN MOHD GHAZALI

PRESENTATION LINK : https://www.youtube.com/watch?v=O02p_HzeRRg

BACKGROUND/SCENARIO
All the network devices in this Packet Tracer Physical Mode (PTPM) activity have been preconfigured
to include intentional errors that are preventing the network from routing as intended. Your task is
to evaluate the network, identify, and correct the configuration errors to restore full connectivity.
You may find errors with the route statements or with other configurations that impact the accuracy
of the route statements. Note: The static routing approach used in this activity is used to assess your
ability to configure different types of static routes only. This approach may not reflect networking
best practices.

OBJECTIVES

Part 1: Evaluate Network Operation

Part 2: Gather Information, Create an Action Plan, and Implement Corrections

ADDRESSING TABLE
Instructions

Part 1: Evaluate Network Operation

Use the ping and/or traceroute commands from the router to test the following criteria and record
the results.

Note: Use the PCs in the wiring closet to gain console access to networking devices in order to
explore and change the device configurations.

 Traffic from R1 to the 172.16.2.1 address on R2 uses the next hop 192.168.0.14.

i) Connect Console cable from R1 to PC1 and R2 to PC2 (RS 232 port)
ii) Make sure the Physical topology same with Logical Topology ( 2Router, 2 Switches, 4pc)

iii) recognize the addressing table with topology

172.16.2.1 is on R2 G0/1 interface

192.168.0.14 is on R2 G0/0/0 interface

iv) Open PC1 Terminal and run 2 command to see routes which is :

-We can see the routes :

we can see the default route is not specifying the subnet and using administrative distance 80, so we
need to remove the administrative distance

v) Run conf term command to enter configuration system and run no ip route 0.0.0.0 0.0.0.0
192.168.0.14 80 command to remove administrative distance. Then, run ip route 0.0.0.0 0.0.0.0
192.168.0.14 command to correct the route.
  Traffic from R1 to the 209.165.200.129 address on R2 uses the next hop 192.168.0.30

i) recognize the addressing table with topology

209.165.200.129 is on R2 G0/2 interface

192.168.0.30 is on R2 G0/0 interface

we need to change 192.168.0.3 to 192.168.0.30

ii) run no ip route 209.165.200.128 255.255.255.128 192.168.0.3 to delete the route. Then run ip
route 209.165.200.128 255.255.255.128 192.168.0.30 command to add route

iii) run end command

 When the G0/0/0 interface on R1 is shut down, traffic from R1 to the 172.16.2.1 address
on R2 uses the next hop 192.168.0.30.

i) recognize the addressing table with topology

172.16.2.1 is on R2 G0/1 interface

192.168.0.30 is on R2 G0/0 interface

ii) Open PC1 terminal and run show run command to see the route

iii) run conf term and no ip route 0.0.0.0 0.0.0.0 192.168.0.3 command to delete the route. Then, run
ip route 0.0.0.0 0.0.0.0 192.168.0.30 80 command to add new route with administrative distance. So,
when g0/0/0 is active, route 0.0.0.0 0.0.0.0 192.168.0.14 will work. Then, when g0/0/0 is not active,
the route will change to 209.165.200.128 255.255.255.128 192.168.0.30

iv) run end command

  Traffic from R2 to the 2001:db8:acad:171::1 address on R1 uses the next hop
2001:db8:acad::1.

i) open Terminal on PC2 and run enable and show run command to see the route

ii) recognize the addressing table with topology

2001:db8:acad:171::1 is on R1 G0/1 interface

2001:db8:acad::1 is on R1 G0/0/0 interface

iii) Run conf term command to enter configuration. Then, run no ipv6 route ::/0 2001:ab8:acad::1 90
command to remove the route with administrative distance. Next, run ipv6 route ::/0
2001:ab8:acad::1 command to add new route without administrative distance

 Traffic from R2 to the 2001:db8:acad:209::1 address on R1 uses the next hop

2001:db8:acad:16::1

i) recognize the addressing table with topology

2001:db8:acad:209::1 is on R1 G0/2 interface

2001:db8:acad:16::1 is on R1 G0/0 interface

we need to change db7 to db8

ii) run no ipv6 route 2001:db8:acad:209::/64 2001:db7:acad:16::1 command to delete the current
route. Then, run ipv6 route 2001:db8:acad:209::/64 2001:db8:acad:16::1 command to add new
route

iii) run end command

  When the G0/0/0 interface on R2 is shut down, traffic from R2 to the
2001:db8:acad:171::1 address on R1 uses the next hop 2001:db8:acad:16::1.

i) Open terminal on PC2 and recognize the addressing table with topology
2001:db8:acad:171::1 is on R1 G0/1 interface

2001:db8:acad:16::1 is on R1 G0/0 interface

ii) run show run command to show running configuration

we need to change 15::1 to 16::1

iii) run conf term command. Then, run no ipv6 route ::/0 2001:db8:acad:15::1 command to delete
the route. Next, run run ipv6 route ::/0 2001:db8:acad:16::1 80 command to add new route.

iv) run end command

v)run show run command

When g0/0/0 is active it will use route ::/0 2001:db8:acad::1. But when g0/0/0 is not active, it will
use route ::/0 2001:db8:acad:16::1 80
Part 2: Gather Information, Create an Action Plan, and Implement Corrections

a.For each criterion that is not met, gather information by examining the running configuration and
routing tables to develop a hypothesis for what is causing the malfunction.

= Already done at Part 1

b. Create an action plan that you think will fix the issue. Develop a list of all the commands you
intend to use to fix the issue, and a list of all the commands you need to revert the configuration,
should your action plan fail to correct the issue.

= List of commands :

enable : to turn on the privileged command

exit : return in global configuration mode

config term : set terminal line parameters

show run : show running system information

show ip route : configure the static route

no ip route : remove route

no shutdown : enables an interface

c. Execute your action plans one at a time for each criterion that fails, and record the fix actions

-ping PC2 from PC1 (ipv4)

75% SUCCESS, 25% LOSS

-ping PC3 from PC1 (ipv4)

100% SUCCESS

-ping PC4 from PC1 (ipv4)

75% SUCCESS, 25%LOSS

-ping PC2 from PC1 (ipv6)

100% SUCCESS

-ping PC3 from PC1 (ipv6)

100% SUCCESS

-ping PC4 from PC1 (ipv6)

100% SUCCESS
-shutdown g0/0/0 from R2

-ping PC2 from PC1 (IPv4, after shutdown g0/0/0)

100% SUCCESS

-ping PC3 from PC1(IPv4, after shutdown g0/0/0)

100% SUCCESS
-ping PC4 from PC1(IPv4, after shutdown g0/0/0)

100% SUCCESS

-ping PC2 from PC1 (IPv6, after shutdown g0/0/0)

100% SUCCESS

-ping PC3 from PC1(IPv6, after shutdown g0/0/0)

100% SUCCESS
-ping PC4 from PC1(IPv6, after shutdown g0/0/0)

100% SUCCESS