Cisco Cisco IOS Software Release 12.0(16) Guide De Dépannage

Page de 2
Issue the dir [device ID] command for each available device, and look for a valid Cisco IOS®
software image:
rommon 3 > dir flash:
        File size            Checksum      File name 
  3407884 bytes (0x804b4c)    0x6ba0    c1000−y−mz.121−6 
rommon 4 > 
2. 
Try to boot from that image.
If the file is valid, this brings you back to normal operation mode.
rommon 5 > boot flash:c1000−y−mz.121−6
program load complete, entry point: 0x80008000, size: 0x804a30 
Self decompressing the image : ################################### 
########... 
♦ 
If none of the files are valid, you need to download a new one using one of the following
procedures:
Download using the Boot Image and a Trivial File Transfer Protocol (TFTP) Server
Since the 1000 Series Router has its boot image in ROM, it cannot be corrupted and
is always available. This procedure is faster than the Xmodem download.
See How To Upgrade from ROMmon Using the Boot Image for the detailed
instructions.
If you are unable to go to Rx−boot mode, the problem is probably hardware−related.
◊ 
Use Another Router to Get a Valid Cisco IOS Software Image into the PCMCIA
Card
If you have another similar router, or at least one other router which has a compatible
PCMCIA Flash card filesystem (see PCMCIA Filesystem Compatibility Matrix and
Filesystem Information), you can also use that Flash card to recover the router.
If both routers are identical (in the same series), you can use the Flash card
from the other router to boot the one you want to recover.
⋅ 
If both routers are different, but have a compatible PCMCIA Flash card
filesystem, you can use the other router to load a Cisco IOS software image
into a Flash card which you can then move to the router you are trying to
recover.
⋅ 
◊ 
♦ 
3. 
Related Information
Cisco Software Center (
 registered customers only
)
• 
Technical Support − Cisco Systems
• 
Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Jan 29, 2006
Document ID: 15075