2.4.1.4 Packet Tracer – Troubleshooting PPP with Authentication

Last Updated on May 3, 2018 by Admin

2.4.1.4 Packet Tracer – Troubleshooting PPP with Authentication

Packet Tracer – Troubleshooting PPP with Authentication (Answer Version)

Answer Note: Red font color or Gray highlights indicate text that appears in the Answer copy only.

Topology

Addressing Table

Device	Interface	IP Address	Subnet Mask	Default Gateway
R1	G0/1	10.0.0.1	255.255.255.128	N/A
	S0/0/0	172.16.0.1	255.255.255.252	N/A
	S0/0/1	172.16.0.9	255.255.255.252	N/A
R2	G0/1	209.165.200.161	255.255.255.224	N/A
	S0/0/0	172.16.0.2	255.255.255.252	N/A
	S0/0/1	172.16.0.5	255.255.255.252	N/A
R3	G0/1	10.0.0.129	255.255.255.128	N/A
	S0/0/0	172.16.0.10	255.255.255.252	N/A
	S0/0/1	172.16.0.6	255.255.255.252	N/A
ISP	G0/1	209.165.200.162	255.255.255.224	N/A
PC1	NIC	10.0.0.10	255.255.255.128	10.0.0.1
PC3	NIC	10.0.0.139	255.255.255.128	10.0.0.129
Web Server	NIC	209.165.200.2	255.255.255.252	209.165.200.1

Objectives

Part 1: Diagnose and Repair the Physical Layer

Part 2: Diagnose and Repair the Data Link Layer

Part 3: Diagnose and Repair the Network Layer

Scenario

The routers at your company were configured by an inexperienced network engineer. Several errors in the configuration have resulted in connectivity issues. Your boss has asked you to troubleshoot and correct the configuration errors and document your work. Using your knowledge of PPP and standard testing methods, find and correct the errors. Make sure that all of the serial links use PPP CHAP authentication, and that all of the networks are reachable. The passwords are cisco and class.

Part 1: Diagnose and Repair the Physical Layer

Step 1: Diagnose and repair the cabling.

1. Examine the Addressing Table to determine the location of the all connections.
2. Verify cables are connected as specified.
3. Diagnose and repair any inactive interfaces.

R1(config-if)# interface g0/1
R1(config-if)# no shutdown
R1(config)# interface s0/0/0
R1(config-if)# no shutdown
R1(config-if)# interface s0/0/1
R1(config-if)# no shutdown

R2(config)# interface s0/0/0
R2(config-if)# no shutdown
R2(config-if)# interface s0/0/1
R2(config-if)# no shutdown

R3(config)# interface g0/1
R3(config-if)# no shutdown
R3(config-if)# interface s0/0/0
R3(config-if)# no shutdown
R3(config-if)# interface s0/0/1
R3(config-if)# no shutdown

Part 2: Diagnose and Repair the Data Link Layer

Step 1: Examine and set clock rates on the DCE equipment.

Examine the configuration of each router to verify that a clock rate has been set on appropriate interfaces. Set the clock rate of any serial interfaces that requires it.

R2(config)# interface s0/0/1
R2(config-if)# clock rate 64000

Step 2: Examine the encapsulation on the DCE equipment.

All of the serial interfaces should be using PPP as the encapsulation type. Change the encapsulation type to PPP for any interface that is set otherwise.

R1(config)# interface s0/0/0
R1(config-if)# encapsulation ppp

R2(config)# interface s0/0/1
R2(config-if)# encapsulation ppp

R3(config)# interface s0/0/0
R3(config-if)# encapsulation ppp

Step 3: Examine and set CHAP usernames and passwords.

Examine each link to verify that routers are logging into each other correctly. All CHAP passwords are set to cisco. Use the debug ppp authentication command if needed. Correct or set any usernames and passwords that need it.

R1(config)# username R3 password cisco
R1(config)# interface s0/0/0
R1(config-if)# ppp authentication chap
R1(config-if)# interface s0/0/1
R1(config-if)# ppp authentication chap

R2(config)# username R1 password cisco
R2(config)# no username R11
R2(config)# interface s0/0/1
R2(config-if)# ppp authentication chap

R3(config)# username R2 password cisco
R3(config)# interface s0/0/0
R3(config-if)# ppp authentication chap
R3(config-if)# interface s0/0/1
R3(config-if)# ppp authentication chap

Part 3: Diagnose and Repair the Network Layer

Step 1: Verify the IP addressing.

Check IP addresses against the Addressing Table and ensure that they are in the correct subnet with their connecting interface. Correct any IP addresses that overlap, are on the wrong interface, have the wrong subnet address, or are set to the host or broadcast address.

R1(config)# interface g0/0
R1(config-if)# no ip address
R1(config-if)# interface g0/1
R1(config-if)# ip address 10.0.0.1 255.255.255.128
R1(config-if)# interface s0/0/0
R1(config-if)# ip address 172.16.0.1 255.255.255.252

R2(config)# interface g0/1
R2(config-if)# ip address 209.165.200.161 255.255.255.224

R3(config)# interface g0/1
R3(config-if)# ip address 10.0.0.129 255.255.255.128
R3(config-if)# interface s0/0/1
R3(config-if)# ip address 172.16.0.6 255.255.255.252

Step 2: Verify full connectivity by tracing a path from PC1 and PC3 to the web server.