Cisco - Hardware Troubleshooting for Cisco 1700 Series Routers
There are two main types of watchdog timeouts. The first type is usually caused by a software problem
and is reported in the router console logs as:
%SYS-2-WATCHDOG: Process aborted on watchdog timeout
The second type of watchdog timeout is usually due to a hardware problem and is reported in one or
both of these two ways:
The show version command output shows:
System returned to ROM by watchdog timer expired
The console logs show:
*** Watch Dog Timeout ***
Refer to
Troubleshooting Watchdog Timeouts
Router Is Dropping Packets
Packet losses caused by hardware problems are fairly easy to identify. The following section uses the
output of the show interfaces command to identify packet losses.
Cyclic Redundancy Check (CRC) and Frame Errors
If CRC errors or frame errors are constantly increasing on the interface, this usually indicates a hardware
problem.
router#show interface ethernet 0
Ethernet0/0 is up, line protocol is up
...
121 input errors, 102 CRC, 19 frame, 0 overrun, 0 ignored
An exception to this is when CRC and frame errors are found on channelized interfaces; they can
indicate clocking problems as well. The fault that is causing the errors can be anywhere between two
connected interfaces: on cables, intermediate devices, or on interfaces themselves. Troubleshooting
techniques differ slightly for different interface types.
Ethernet Interfaces
For Ethernet interfaces, troubleshooting differs between a shared environment (devices connected
through a hub or with a coaxial cable) and a switched environment (devices connected to a switch).
In a switched environment, there are only three components that could cause the error:
cable
local interface (port)
remote interface (port)
http://kbase:8000/paws/servlet/ViewFile/17959/hwts_1700_17959.xml?convertPaths=1
to further troubleshoot this issue.
Page 9 of 12
01/10/2004
페이지 인쇄