10.2.2.3 Packet Tracer Troubleshooting Single Area OSPFv2 Instructions

10.2.2.3%20Packet%20Tracer%20-%20Troubleshooting%20Single-Area%20OSPFv2%20Instructions

10.2.2.3%20Packet%20Tracer%20-%20Troubleshooting%20Single-Area%20OSPFv2%20Instructions

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 2

Download10.2.2.3 Packet Tracer - Troubleshooting Single-Area OSPFv2 Instructions
Open PDF In BrowserView PDF
Packet Tracer – Troubleshooting Single-Area OSPFv2
Topology

Addressing Table
Device

Interface

IP Address

Subnet Mask

Default Gateway

G0/0

172.16.1.1

255.255.255.0

N/A

S0/0/0

172.16.3.1

255.255.255.252

N/A

S0/0/1

192.168.10.5

255.255.255.252

N/A

G0/0

172.16.2.1

255.255.255.0

N/A

S0/0/0

172.16.3.2

255.255.255.252

N/A

S0/0/1

192.168.10.9

255.255.255.252

N/A

S0/1/0

209.165.200.225

255.255.255.224

N/A

G0/0

192.168.1.1

255.255.255.0

N/A

S0/0/0

192.168.10.6

255.255.255.252

N/A

S0/0/1

192.168.10.10

255.255.255.252

N/A

PC1

NIC

172.16.1.2

255.255.255.0

172.16.1.1

PC2

NIC

172.16.2.2

255.255.255.0

172.16.2.1

PC3

NIC

192.168.1.2

255.255.255.0

192.168.1.1

R1

R2

R3

Scenario
In this activity, you will troubleshoot OSPF routing issues using ping and show commands to identify errors in
the network configuration. Then, you will document the errors you discover and implement an appropriate
solution. Finally, you will verify end-to-end connectivity is restored.

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.

Page 1 of 2

Packet Tracer – Troubleshooting Single-Area OSPFv2

Troubleshooting Process
1. Use testing commands to discover connectivity problems in the network and document the problem in
the Documentation Table.
2. Use verification commands to discover the source of the problem and devise an appropriate solution
to implement. Document the proposed solution in the Documentation Table.
3. Implement each solution one at a time and verify if the problem is resolved. Indicate the resolution
status in the Documentation Table.
4.

If the problem is not resolved, it may be necessary to first remove the implemented solution before
returning to Step 2.

5. Once all identified problems are resolved, test for end-to-end connectivity.

Documentation Table
Device

Identified Problem

Proposed Solution

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.

Resolved?

Page 2 of 2
Source Exif Data: 
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : Yes
Tagged PDF                      : Yes
Signing Date                    : 2013:07:22 13:39:09-07:00
Signing Authority               : ARE Acrobat Product v8.0 P23 0002337
Document Usage Rights           : FullSave
Annotation Usage Rights         : Create, Delete, Modify, Copy, Import, Export
Form Usage Rights               : Add, FillIn, Delete, SubmitStandalone
Signature Usage Rights          : Modify
XMP Toolkit                     : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:14:39
Create Date                     : 2013:07:22 13:33:15-07:00
Creator Tool                    : Microsoft® Word 2010
Modify Date                     : 2013:07:22 13:39:09-07:00
Metadata Date                   : 2013:07:22 13:39:09-07:00
Format                          : application/pdf
Creator                         : Betty Staerk
Producer                        : Microsoft® Word 2010
Document ID                     : uuid:6b619a3f-2c50-42f9-a053-121d76eeb648
Instance ID                     : uuid:4ef3d012-2467-4cd3-b319-c9bb75c9826f
Has XFA                         : Yes
Page Count                      : 2
Language                        : en-US
Author                          : Betty Staerk
EXIF Metadata provided by EXIF.tools

Navigation menu