Professional Documents
Culture Documents
Basic Router Troubleshooting: Hetal Presswala
Basic Router Troubleshooting: Hetal Presswala
Basic Router Troubleshooting: Hetal Presswala
Hetal Presswala
2 - Confidential
The show ip route Command
3 - Confidential
Examining the Routing Table
Dublin# show ip route
Networks being
advertised
Out
interface
5 - Confidential
Static Vs Dynamic Cont…
6 - Confidential
Need of Default route
Default routes are used when there isn’t a more specific entry in
routing table
7 - Confidential
How to Configure Default Route
8 - Confidential
Determining Route Source and Destination
9 - Confidential
Routing – Role of Layer 2 and Layer 3 Addressing
10 - Confidential
Determining Administrative Distance
AD measures the trustworthiness of the source of the route
information.
The lower the AD, the more trustworthy the source.
Different routing protocols have different default ADs.
When there are two paths available to a destination the path with the
lowest AD is used in the routing table.
11 - Confidential
Determining the Route Metric
Routing algorithms generate a number, called the metric value, for each
path through the network .
The metric value is used to determine the best route to a destination.
The various protocols base their metrics on different factors:
12 - Confidential
Viewing the Routing Table
Use the following commands to find the last
routing update:
show ip route
show ip route network
show ip route connected
show ip route static
show ip protocols
show ip rip database
13 - Confidential
Show ip route Command
14 - Confidential
Introduction to Network Testing
15 - Confidential
Structured Approach to Troubleshooting
16 - Confidential
Typical Layer 1 Errors
Broken cables
Disconnected cables
Cables connected to the wrong
ports
Intermittent cable connection
Wrong cables used for the task at
hand
Transceiver problems
DCE cable problems
DTE cable problems
Devices turned off
17 - Confidential
Layer 1 Troubleshooting – using show interfaces
Physical layer (line
status)
BHM#show interface s0 Up: has Layer 1
Serial0 is up, line protocol is up connectivity
< output omitted > Down: L1 problem
Last clearing of "show interface" counters never
Administratively
< output omitted > To reset: BHM# clear
counters down: disabled
Received 73 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0
abort
135 packets output, 7361 bytes, 0 underruns
0 output errors, 0 collisions, 37 interface resets
0 output buffer failures, 0 output buffers swapped out
54 carrier transitions
Bad line,
Faulty Line
bad
hardware, interruption
hardware
cable or s, faulty
noise hardware 18 - Confidential
Layer 1 Troubleshooting
The show interfaces – using show
serial interfaces
command
19 - Confidential
Layer 1 Troubleshooting – show controllers
20 - Confidential
Troubleshooting Using show controllers serial
The show controllers serial Command
21 - Confidential
Typical Layer 2 Errors
22 - Confidential
Troubleshooting Using show cdp neighbors
23 - Confidential
Troubleshooting Using show cdp neighborstail
24 - Confidential
Layer 2 Troubleshooting – show interfaces
25 - Confidential
Layer 2 Troubleshooting
If the interface is up and the line protocol is down, a
Layer 2 problem exists.
26 - Confidential
Show interfaces Command
27 - Confidential
Typical Layer 3 Problem
28 - Confidential
Layer 3 Troubleshooting Using Ping
29 - Confidential
Ping
vista# ping ScopeDelhi
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2
seconds: ‘!’ indicate a
..!!! successful echo
Success rate is 60 percent (3/5), ‘.’ indicate the
round-trip min/avg/max = 32/33/36 ms
application timed out
waiting for an echo
Extended ping
• provides extra facilities for ping
30 - Confidential
Troubleshooting Using traceroute Command
32 - Confidential
Troubleshooting
The show ipRouting Issues Command
protocols
33 - Confidential
Layer 7 Troubleshooting Using Telnet
34 - Confidential
Summary
35 - Confidential