Cisco 2600XM Series Przewodnik Instalacji Pobierz pdf (Strona 6)

point. Hangs are not necessarily hardware issues and most of the time, they are a software issue. If your router

is experiencing a router hang, refer to Troubleshooting Router Hangs.

Router Reboot/Reload

When the router reboots, it returns to a normal state. A "normal state" means that the router is functional,

passing traffic, and that you are able to gain access to the router. To check why the router rebooted, issue the

show version command and look at the output (see example below):

Router# show version

Router uptime is 20 weeks, 5 days, 33 minutes

System returned to ROM by power−on

Router Crashes

When we refer to a "system crash", we mean a situation where the system has detected an unrecoverable error

and has restarted itself. A crash can be caused by software problems, hardware problems, or both. This section

deals with hardware−caused crashes and crashes that are software−related, but may be mistaken for hardware

problems.

IMPORTANT: If the router is reloaded after the crash (for example, through a power−cycle or the reload

command), important information about the crash will be lost, so try to collect show technical−support and

show log output, as well as the crashinfo file (if possible) before reloading the router!

Refer to Troubleshooting Router Crashes for more information regarding this issue.

Bus Error Crashes

The system encounters a bus error when the processor tries to access a memory location that either does not

exist (a software error) or does not respond properly (a hardware problem). A bus error can be identified by

looking at the output of the show version command provided by the router (if not power−cycled or manually

reloaded).

Here are two examples of bus error crashes:

Router uptime is 2 days, 21 hours, 30 minutes

System restarted by bus error at PC 0x30EE546, address 0xBB4C4

System image file is "flash:igs−j−l.111−24.bin", booted via flash

.........

At the console prompt, the following error message might also be seen during a bus error:

*** System received a Bus Error exception ***

signal= 0xa, code= 0x8, context= 0x608c3a50

PC = 0x60368518, Cause = 0x20, Status Reg = 0x34008002

For more information regarding this issue, refer to Troubleshooting Bus Error Crashes.

Continuous/Boot Loop

The router may experience a continuous loop that could be due to a hardware issue. A continuous loop never

lets you gain access to the router (for example, you won't be able to log in to enable mode, and so on), and the

router continues to give scrolling error messages until it is powered off. Below are examples and

Cisco − Hardware Troubleshooting for the Cisco 2600 Series Router

1 2 3 4 5 6 7 8 9 10 11 ... 15 16

Brak uwag

Cisco 2600XM Series Przewodnik Instalacji Strona 6