8th February 2012

IOS: ROMMON on the C6500/Sup720 – Lesson Learned

Recently, one of my Supervisor 720 goes into a permanent reboot cycle. I was able to break it into ROMMON mode, but I couldn’t get it to ‘stick’ the boot settings.

Finally….

Finally, one of the other guys came and looked over my shoulder and pointed out that I was making two mistakes. Here is the correct syntax:

rommmon 2 > BOOT=bootdisk:s72033-advipservicesk9_wan-vz.122-18.SXF14.bin
rommon 3 > set
PS1=rommon ! >
LOG_PREFIX_VERSION=1
SLOTCACHE=cards;
ACL_DENY=0
PF_REDUN_CRASH_COUNT=0
RANDOM_NUM=17402343563
CRASHINFO=crashinfo_FAILED
RET_2_RTS=10:05:02 UTC Thu Jun 26 2008
RET_2_RCALTS=1214421319203
BSI=0
?=0
BOOT=bootdisk:s72033-advipservicesk9_wan-vz.122-18.SXF14.bin
rommon 4 > sync

The first mistake is that the BOOT command in the first line must be in capitals.

The second mistake I made was that I didn’t to sync the configuration register. In my defense, I have never had to do this before, but, there you go.

In turns out that the Supervisor 720 is quite different from earlier Supervisor Modules and you need to make sure that

  1. you purchase Compact Flash modules
  2. you need to put a second copy of IOS on the compact flash as well as on the sup-bootflash:

Cisco documentation

Surprisingly, the Cisco documentation seem to make any mention of this.

Typical session

rommon 1 > set
PS1=rommon ! >
SLOTCACHE=cards;
SWITCH_NUMBER=0
LOG_PREFIX_VERSION=1
ACL_DENY=0
RANDOM_NUM=1293932989
BOOT=bootdisk:/sys/s72033/base/s72033-adventerprisek9_wan-vm,12;bootflash:s72033-advipservicesk9_wan-mz.122-18.SXF14.bin,12;bootflash:s72033-boot-mz.122-33.SXH2a.bin,12;
?=0
CRASHINFO=bootflash:crashinfo_20080623-092644
RET_2_RTS=10:26:45 BST Mon Jun 23 2008
TYFIB_BLOCK_ALLOC=
NT_K=0:0:0:0
CV=bootdisk:/sys/s72033/base/s72033-adventerprisek9_wan-vm
RET_2_RCALTS=
BSI=0
PF_REDUN_CRASH_COUNT=0
rommon 2 > dir
usage: dir
rommon 3 > dir bootflash:

Initializing ATA monitor library…
Directory of bootflash:

2 127331492 -rw- s72033-adventerprisek9_wan-vz.122-33.SXH2a.bin
15546 33554432 -rw- sea_log.dat
19642 0 drw- sys
25801 80828964 -rw- s72033-advipservicesk9_wan-mz.122-18.SXF14.bin
45869 311265 -rw- crashinfo_ios-base-20080623-070329
rommon 4 > BOOT=bootdisk:s72033-advipservicesk9_wan-mz.122-18.SXF14.bin
rommon 5 > sync
rommon 6 > reset

This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net - twitter: @etherealmind | All rights reserved
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • Ben Johnson

    Bugger! Wish I had’ve seen this BEFORE this morning. Oh well, glad you posted it anyway. Now I know what I’ll be doing next Tuesday morning.

    I made exactly the same mistake; didn’t capitalise the “BOOT” keyword. Live and learn :)

    Twitter: @silverbenz

  • Perrinweb

    Thanks!  I had to sit here and watch this 6513 restart for two hours with failed autoboot before I decided to search for this post!  Thank you!

    • http://etherealmind.com Etherealmind

      No problem.