Friday, October 14, 2016

CCNAv3 Completed Packet Tracer 5.2.2.3

Greetings, and welcome to Seeseenayy.
You are visiting one of our many posts about packet tracer activities!

This post contains the answers to the 
CCNA3 Packet Tracer '5.2.2.3'

(above image is a preview of the packet tracer)

This post is split into two parts.
1. The download link of the completed packet tracer, and sometimes completed, or uncompleted PDFs or other files.

2. Tutorial. A text guide on how the packet tracer was completed, command-by-commandstep-by-step.

To view this post, and discover the answers to this activity, click on the following link if you have not done so already.


Downloads / Information
You may find the download to this packet tracer, or any other related file, directly below:


Tutorial

We're going to be diagnosing single-layer OSPFv2.
Like any diagnosing packet tracer, we'll be using show commands and our (more than likely) rudimentary comprehension. 

The following commands are the show commands used when diagnosing this packet tracer. Remember them-- they're important and have universal use for OSPF configuration and diagnosis!
-> show ip ospf int g0/0
-> show ip protocols
-> show ip int brief
-> show ip route 

If you need a refresh of the commands, or a summary of what they do, click here to head over to our IOS page.

To attempt to figure out what issues cause what, lets start out by doing the easiest: ping each device from the PC(s).
Go ahead and ping each PC to some device across the topology. Failure should indicate somewhere along the lines, an error occurred.

This is not a necessary step, but it is suggested so that you can develop a "habit".

There are three issues that were detected:

 1) There isn't a network connection to R3. 
 R1 has an incorrect network address to R2.
 FIX BY USING THE FOLLOWING:
   R1(config)#router ospf 1
   R1(config-router)#no network 172.16.10.4 0.0.0.3 area 0
   R1(config-router)#network 192.168.10.4 0.0.0.3 area 0
   R1(config-router)#exit
   R1(config)#

 2) Unable to ping the web server from PCs.
 PC1 and PC3 cannot ping the webserver. Blame R2, of course!
 FIX BY USING THE FOLLOWING:
   R2>en
   R2#conf t
   R2(config)#router ospf 1
   R2(config-router)#default-information originate 
   
 3) Hello interval on R3's S0/0/1 interface is incorrect.
 The hello interval on R3 (outbound S0/0/1) is incorrect. Ergo, the routes are unable to connect.
 FIX BY USING THE FOLLOWING:
   R3(config)#int S0/0/1
   R3(config-if)#ip ospf hello-interval 10
   R3(config-if)#exit

No comments:

Post a Comment

Feel free to comment if you have a question, commendation, or concern. We love to hear your feedback!

Please do not share links to external websites if it not relevant to discussion. We reserve our right to remove any content we deem advertising.