[CCNAv6 S4] 2.4.1.4 Packet Tracer - Troubleshooting PPP with Authentication




Packet Tracer – Troubleshooting PPP with Authentication
Addressing Table


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.

a.     Examine the Addressing Table to determine the location of the all connections.

b.     Verify cables are connected as specified.

c.     Diagnose and repair any inactive interfaces.

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.

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.

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.

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.

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




Configuration R1:

enable
configure terminal
interface g0/1
 ip address  10.0.0.1 255.255.255.128
 no shutdown
interface Serial0/0/0
 ip address 172.16.0.1 255.255.255.252
 encapsulation ppp
 ppp authentication chap
 no shutdown
interface Serial0/0/1
 ppp authentication chap
 no shutdown
 exit
username R3 password  cisco
end
write memory
!

Configuration R2:

enable
configure terminal
interface GigabitEthernet0/1
 ip address 209.165.200.161 255.255.255.224
interface Serial0/0/0
 ip address 172.16.0.2 255.255.255.252
 no shutdown
interface Serial0/0/1
 encapsulation ppp
 ppp authentication chap
 no shutdown
 exit
username R3 password  cisco
username R1 password  cisco
end
write memory
!

Configuration R3:


enable
configure terminal
interface Serial0/0/1
 ip address 172.16.0.6 255.255.255.252
 encapsulation ppp
 ppp authentication chap
 no shutdown
interface Serial0/0/0
 encapsulation ppp
 ppp authentication chap
 no shutdown
interface g0/1
 ip address 10.0.0.129 255.255.255.128
 no shutdown
 exit
username R2 password  cisco
username R1 password  cisco
end
write memory
!

END !~!


Nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S4] 8.2.4.14 Packet Tracer - Troubleshooting Enterprise Networks 3

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

[CCNAv6 S2] 7.3.2.4 Packet Tracer - Troubleshooting Standard IPv4 ACLs