Step 3: Use troubleshooting tools to verify the configuration.Īt the default gateway router, use troubleshooting tools to verify the configuration with your own documentation. Remember to check switches in addition to the routers. Step 4: Document network symptoms and possible solutions.Īs you discover symptoms of the PC connectivity issue, add them to your documentation.Īnswer Note: The following is only one way the student might progress through this activity. The student can start from any PCs, except For this sample answer, we started at PC4. Problem 1: From PC4, you can access the default gateway, R2. Telnet to R2 and verify the routing table. R2 only has directly connected routes, so verify the current interface configuration using the show protocols or show ip interface brief command. Careful examination of the IP addresses will reveal that the S0/0/0 address is incorrect. The show ip protocols command reveals no problems with the EIGRP configuration on R2. Solution 1: Configure the correct IP address for the S0/0/0 interface on R2.

Problem 2: After EIGRP converges on R2, use the show ip route command to gather further information about possible problems. R2 has correct connected routes but only has two EIGRP routes. Missing routes include the four VLANs for R3, the R1 LAN, and the R4 LAN. Pinging R3 is successful, so telnet to R3. Because R2 is not receiving routes from R3, check the EIGRP configuration on R3 with the show ip protocols command. R3 is sending and receiving EIGRP updates and is advertising the correct network. However, automatic networks summarization is in effect. Therefore, R3 is only sending the classful 10.0.0.0/8 network in EIGRP periodic updates. Solution 2: Configure R3 with the no auto-summary command. Problem 3: Exit back to R3 and check the routing table. Routes are missing for the R1 and R4 LANs.

Ccna 4 chapter 8.3.1.2 packet tracer Pc#.

Ccna 4 chapter 8.3.1.2 packet tracer password#.

Ccna 4 chapter 8.3.1.2 packet tracer full#.Ccna 4 chapter 8.3.1.2 packet tracer update#.

Packet tracer 8.3.1.2 issue