CCNA Discovery 2 - Chapter 9

Troubleshooting

Working at a Small-to-Medium Business or ISP –
Chapter 9

Version 4.1 © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 1

Objectives
 Use the OSI model as a framework for troubleshooting
network problems.
 Identify and correct problems with hardware and operation at
Layer 1 and Layer 2.
 Troubleshoot IP addressing problems, including subnet
mask, host range errors, DHCP and NAT issues.
 Identify and correct problems with RIPv2 configuration and
implementation.
 Explain possible causes of problems occurring with user
applications and how to recognize symptoms of DNS
failures.
 Create a plan to prepare to take the ICND1 examination in
order to obtain a CCENT certification.
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 2

Troubleshooting Methodologies and Tools
 Knowledge of the features, functions and devices of
each OSI or TCP/IP layer supports efficient
troubleshooting


Three troubleshooting approaches:
 Top-down
 Bottom-up
 Divide-and-conquer


Helpful network diagrams:
 Physical network topology
 Logical network topology


Additional troubleshooting tools:
 Documentation and baseline tools
 Management system tools
 Knowledge bases
 Protocol analyzers


Hardware troubleshooting tools:
 Cable testers
 Digital multimeters
 Portable network analyzers


Troubleshooting Layer 1 and Layer 2 Issues
 Layer 1 problems are related to the type of technology
used
 Layer 1 problems can result in loss of connectivity or
degraded network performance


 Layer 2 specifies data format and network access
 Network analyzers can diagnose Layer 2 issues


 Observe console messages during the boot sequence
 Use Cisco IOS CLI show commands to verify
operational status
 When boot problems cause a network outage, use
substitution to restore service


Five common bootup errors:
 POST failure
 Corrupt flash image
 Corrupt or missing configuration file
 Memory error
 Module error


Common issues causing up/down or down/down outputs:
 Loose or incorrectly terminated cables
 Damaged interface or cable
 Improper encapsulation configuration


Use output from the show interfaces command to help
identify media errors:
 Excessive noise
 Excessive collisions
 Excessive runts
 Late collisions


Troubleshooting LAN connectivity on switches:
 Observe port LEDs
 Verify cables
 Verify configuration
 Verify duplex settings


Troubleshooting WAN connectivity issues:
 Use show interfaces serial output
 Know the type of modem or CSU/DSU being used


Troubleshooting Layer 3 IP Addressing Issues
 Many Layer 3 problems are due to poorly designed and
configured IP addressing schemes
 Determine the host range in order to troubleshoot


Problems resulting from poor Layer 3 planning:
 Overlapping subnets
 Misconfigured subnet masks
 Insufficient addresses available through DHCP


DHCP issues:
 Physical connectivity
 Server misconfiguration
 Address conflicts


NAT issues:
 Incorrect designation of inside and outside interfaces
 Pool misconfiguration
 No route to the Internet for translated addresses


Troubleshooting Layer 3 Routing Issues
Common routing issues:
 Manual route entry errors
 Routing protocol configuration errors
 Failures at lower OSI layers


 The routing table indicates connected, dynamic, static
and default routes


Issues related to RIP:
 Version mismatch
 Incorrect or missing network statements


Tools for troubleshooting dynamic routing issues:
 TCP/IP utilities
 Debug commands


Troubleshooting Layer 4 and Upper Layer Issues
Traffic filtering issues:
 Firewall misconfiguration
 Incorrect port assignment


 Basic connectivity must be
eliminated as the source of the
problem
 Check with the ISP to ensure
that the problem does not lie
with the remote network


 Upper layer issues can exist
even with full network
connectivity
 Check application configuration
with specific problems
 Encryption or compression
mismatch may be an issue
 Make sure browser plug-ins have
been updated
 If more than one application is
affected, a DNS server issue
may be the problem

 Telnet provides troubleshooting access, but is an
insecure protocol
 SSH is a more secure method for remote device
access


Preparing for Cisco Certification
 ICND1 exam (640-822) includes topics on networking
fundamentals
 Pass ICND1 to achieve CCENT certification


What certification exams measure:
 Knowledge: facts recalled from memory
 Skills: interacting with Cisco networking devices
 Abilities: scenario-based or simulation tasks


 Make the commitment
 Create a study plan
 Practice test taking


 Visit the testing center
 Become familiar with the test format
 Use exam tutorials and practice tests
 Practice Packet Tracers and labs


Summary
 Networking models provide a framework for efficient
troubleshooting.
 Good troubleshooting involves using a methodology,
such as top-down, bottom-up, or divide-and-conquer.
 The majority of Layer 3 problems result from poor or
incorrect addressing schemes.
 Firewall misconfiguration can result in problems with
upper layer protocols.
 Success on certification tests depends on building
knowledge, skills, and abilities.


CCNA Discovery 2 - Chapter 9

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to CCNA Discovery 2 - Chapter 9 (20)

More from Irsandi Hasan (20)

Recently uploaded (20)

CCNA Discovery 2 - Chapter 9