cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
250
Views
0
Helpful
11
Replies
Highlighted
Beginner

6500 in rommon

hello dears 

i'm facing a problem my cisco is on rommon now and i'm using 1 supervisor with multiple IOS images 
i need a guide to select the image that i want and when reloading or power cycling the router it wont go in rommon or it wont load another image 
your urgent feedback is highly appreciated 

THANKS

11 REPLIES 11
Highlighted
Beginner

and when i try this command  its says sup-bootdisk is not a bootable device

rommon 11 > boot sup-bootdisk:s72033-adventerprise-mz.151-2.SY7.bin

sup-bootdisk: Not a bootable device

Highlighted

try list files :

 

from rommon >

 

dir bootflash:

dir slot0:

follow below guide to boot fix :

 

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/17050-14.html

 

 

BB

 

BB
*** Rate All Helpful Responses ***
Highlighted

Download Completed! Booting the image. Self decompressing the image : ########################################################################################################################################################################################################################################## [OK] Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706 Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISE-M), Version 15.1(2)SY7, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2016 by Cisco Systems, Inc. Compiled Sun 13-Mar-16 07:31 by prod_rel_team Image text-base: 0x40106558, data-base: 0x449C5540 *Jul 17 19:02:39.799: %SYS-SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jul 17 19:02:39.799: %OIR-SPSTBY-6-CONSOLE: Changing console ownership to switch processor *Jul 17 19:02:39.887: %SYS-SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jul 17 19:02:40.015: %SYS-SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jul 17 19:02:39.887: %OIR-SPSTBY-6-CONSOLE: Changing console ownership to switch processor *Jul 17 19:02:41.803: %SYS-SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jul 17 19:02:40.227: %SYS-SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jul 17 19:02:41.803: %SYS-SPSTBY-5-SWITCHOVER: Switchover requested by Reset Process. Reload Reason: Reason unspecified. *Jul 17 19:02:41.803: %OIR-SPSTBY-6-CONSOLE: Changing console ownership to switch processor *Jul 17 19:02:42.271: %SYS-SPSTBY-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. *Jul 17 19:02:42.271: %SYS-SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jul 17 19:02:42.271: %OIR-SPSTBY-6-CONSOLE: Changing console ownership to switch processor *Jul 17 19:02:42.611: %SYS-SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. *Jul 17 19:02:42.467: %SYS-SPSTBY-5-SWITCHOVER: Switchover requested by PF Redun Status. Reload Reason: Reason unspecified. System Bootstrap, Version 8.5(2) Copyright (c) 1994-2007 by cisco Systems, Inc. Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
Highlighted

it ssys slot0 and sup-bootdisk are not a bootable devices any ideas 

best regards

Highlighted

Hello Omar2,

It sounds like you may have a sup720 or something similar. They have two CPU's and two sets of flash storage. Bootdisk is for route processor (RP) flash storage and sup-bootdisk is for switch processor (SP) flash storage.

When sup first boots up it boots SP first, then switches to RP and finishes booting. But SP only sees its own flash storage as "bootdisk" during bootup and while in rommon. You can see available storage locations in rommon with "dev" command. Try checking for bootdisk directory when in rommon and running "dir" command for that directory to see images you can use.
Highlighted

hello matt Directory of bootflash: 2 46256548 -rw- s72033-ipbase-mz.122-33.SXH3a.bin 7755 33554432 -rw- sea_log.dat 4874 47198628 -rw- s72033-ipbasek9-mz.122-33.SXH5.bin 9623 5602 -rw- debuginfo_20150803-002857 14223 105945484 -rw- s72033-adventerprise-mz.151-2.SY7.bin 1034 33554432 -rw- sea_console.dat 9805 2269 -rw- diaginfo_mod1_20160627-145111 9806 2269 -rw- diaginfo_mod1_20160627-145642 9807 2269 -rw- diaginfo_mod1_20160627-150215 9808 2269 -rw- diaginfo_mod1_20160627-215949 9809 2269 -rw- diaginfo_mod1_20160627-220519 9810 2269 -rw- diaginfo_mod1_20160627-221049 9811 2269 -rw- diaginfo_mod1_20160627-232208 9812 2269 -rw- diaginfo_mod1_20160801-103325 9813 2269 -rw- diaginfo_mod1_20160814-083807 9814 2269 -rw- diaginfo_mod1_20160814-084338 9815 2269 -rw- diaginfo_mod1_20160814-084906 1244 63248 -rw- crashinfo_20180222-122702 9820 2269 -rw- diaginfo_mod1_20180716-013459 9821 2269 -rw- diaginfo_mod1_20180716-014031 9822 2269 -rw- diaginfo_mod1_20180716-015505 9823 2269 -rw- diaginfo_mod1_20180716-020037 9824 2269 -rw- diaginfo_mod1_20180716-020608 9825 2269 -rw- diaginfo_mod1_20180716-021651 9826 2269 -rw- diaginfo_mod1_20180716-022223 9827 2269 -rw- diaginfo_mod1_20180716-022750 9828 2269 -rw- diaginfo_mod1_20180716-212027 9829 11196 -rw- sup-bootdisk:s72033-adventerprise-mz.151-2.SY7.bin rommon 5 > boot sup-bootdisk:s72033-adventerprise-mz.151-2.SY7.bin sup-bootdisk: Not a bootable device rommon 6 > dir slot0: bad device name (device not supported) usage: dir the device cant load from the slot 0 or supboot disk and idk how to make it load from them any ideas best regards
Highlighted

Hello Omar2,

 

From there you need to use the command "boot bootflash:filename" to boot an image.

 

It looks like the module is failing some diagnostics, with might not be a good sign. Can you do the following and let me know the output.

 

From rommon run the command "priv". This unlocks secret rommon commands.

 

Then run "cat bootflash:diaginfo_mod1_20180716-212027". This command should show the output of the diaginfo file, which may contain results of diagnostic failures seen during bootup.

Highlighted

rommon 8 > cat bootflash:diaginfo_mod1_20180716-212027 Initializing ATA monitor library... Module 1 : CEF720 48 port 10/100/1000mb Ethernet Serial # : SAD092003YK Software : 15.1(2)SY7 Online Diagnostic Result : MAJOR ERROR Online Diagnostic Level when Module 1 came up = Minimal Test Results: (. = Pass, F = Fail, U = Unknown) 1 . TestLoopback : Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U 2 . TestTxPathMonitoring : . 3 . TestSynchedFabChannel : U 4 . TestL3VlanMet : U 5 . TestIngressSpan : U 6 . TestEgressSpan : U 7 . TestAsicMemory : U 8 . TestEobcStressPing : U 9 . TestFirmwareDiagStatus : F 10. TestAsicSync : U 11. TestUnusedPortLoopback : Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U 12. TestOBFL : . 13. TestErrorCounterMonitor : U 14. TestPortTxMonitoring : Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 ---------------------------------------------------------------------------- U U U U U U U U U U U U U U U U U U U U U U U U 15. TestLtlFpoeMemoryConsistency : U 16. TestRwEngineOverSubscription : U
Highlighted

Hello Omar2,

 

Thanks for the output.

 

There is major diagnostic error seen during bootup. the TestFirmwareDiagStatus is failing. Any chance that this supervisor can be replaced?

Highlighted

yes i have 3 supervisors , currently there are 2 attached to the core and the third one is not what should i do ? 

Highlighted

Hello Omar2,

You can try booting the other images in bootflash and see if the supervisor will boot up.

However, if the major diagnostic errors continue to occur, then the supervisor may need to be replaced due to hardware failure.
Content for Community-Ad