Page 297

Identifying and Resolving Generic Router Problems

261

Instead of coming up with the normal prompt, the router is in boot mode,

which explains why no routing is taking place. When a router is in boot
mode, routing protocols do not work. This is the last key observation
needed, and it allows you to define the problem.

Here is the problem statement: Router B is in boot mode, it does not route

in this state, so Host Z cannot FTP to Host A. This statement lists the actual
problem, as well as the reported problem.

Propose Solutions

With the observations made, and a detailed and focused problem statement,
you can now move on to provide possible solutions to the problem. It is still
important to consider the observations when determining the next action.

You know that the router is in boot mode, but what causes a router to be

in boot mode? There are two simple reasons that a router may be in boot
mode: lack of IOS on the system flash or the router is not looking for the IOS
in the right location.

Let's look at the contents of Router B's flash. Then, look at the router's

version information.

Router_B(boot)#show flash

System flash directory:

File Length Name/status

1 4287696 c2500-i-l.112-15.bin

[4287760 bytes used, 4100848 available, 8388608 total]

8192K bytes of processor board System flash (Read/Write)

Router_B(boot)#

This shows one IOS image on the system flash. Now, you need to determine

which version of IOS is running on the router:

Router_B(boot)#show version

Cisco Internetwork Operating System Software

IOS (tm) 3000 Bootstrap Software (IGS-BOOT-R), Version
11.0(10c)XB1, PLATFORM SPECIFIC RELEASE SOFTWARE (fc1)

Compiled Wed 10-Sep-97 13:06 by phester

Image text-base: 0x01010000, data-base: 0x00001000

ROM: System Bootstrap, Version 11.0(10c)XB1, PLATFORM
SPECIFIC RELEASE SOFTWARE

www.sybex.com