6509 boots to Rmon

[jimmysands73_2]

Looking over a senior guys notes and attempting to help out.  We have 6509 upon reboot boots to RMON. From rmon we can boot no problem, but then if its rebooted, back to rmon. 

The config looked correct, but am trying to help, here is the relevant parts, if more needed, please let me know.

RTR-01#sh bootvar

BOOT variable = sup-bootflash:c6sup22-psv-mz.121-27b.E3.bin,1

CONFIG_FILE variable = bootflash:startup-config

BOOTLDR variable =

Configuration register is 0x2102

RTR-01#sh ver | inc reg
Configuration register is 0x2102

RTR-01#sh run | inc boot

boot system flash sup-bootflash:c6sup22-psv-mz.121-27b.E3.bin

boot config bootflash:startup-config

RTR-01#dir /all
%Error opening slot0:/ (No such device)
RTR-01#dir all
RTR-01#dir all-filesystems
Directory of sup-bootflash:/

    1  -rw-    24997392  Mar 29 2012 04:42:42 -07:00  c6sup22-psv-mz.121-27b.E3.bin

31981568 bytes total (6984048 bytes free)
Directory of const_nvram:/

    1  -rw-        2536                    <no date>  vlan.dat

129004 bytes total (126468 bytes free)
Directory of system:/

    2  dr-x           0                    <no date>  memory
    1  -rw-       30015                    <no date>  running-config
   11  dr-x           0                    <no date>  vfiles

No space information available
Directory of nvram:/

    1  -rw-       29970  Aug 09 2012 06:48:46 -07:00  startup-config
    2  ----          25                    <no date>  private-config
    3  -rw-       28946                    <no date>  underlying-config
    1  -rw-           0                    <no date>  ifIndex-table

391160 bytes total (361113 bytes free)
Directory of bootflash:/

    1  -rw-    13575464  Mar 29 2012 04:06:17 -07:00  c6msfc2-psv-mz.121-27b.E3.bin
    2  -rw-     1863420  Mar 29 2012 04:07:29 -07:00  c6msfc2-boot-mz.121-27b.E3.bin
   10  -rw-       29970  Aug 09 2012 06:48:46 -07:00  startup-config

31981568 bytes total (16344276 bytes free)

I left some non-relevant dir out of the above dir output.

I searched Ciscos site but am unable to discover why this is happening.  Any input would be appreciated.

Thanks!

[jimmysands73_2]

Its actully at 6506 if that matters.

cisco WS-C6506 (R7000) processor (revision 2.0) with 227328K/34816K bytes of memory.

The only idea I have gathered from reading other post is its set to autoboot:

At rommon prompt, type confreg….

Say no until you get to the bottom question…

At “ change the boot characteristics": answer yes…

Enter 2 to boot system as autoboot

Type "reset"

Any other ideas?

[Leo Laohoo]

Hi Jimmy,

Never played with a Sup 2 before so if it's OK with you, I'll take a "stab in the dark".

Can you post the bootup process?  I would like to see when the supervisor card goes into ROMmon.

[jimmysands73_2]

This I can not do as its my ticket at work.  I was just trying to learn something along the way.  Plus its a LAN rtr, so if I rebooted it alarms would go off everywhere......maybe the site is going to have a 'power' issue soon lol.  Oh wait, dual power supplies, one going to a UPS and other to house power, dual power failure!  So unfortunately I can not get a screen shot, I did email the assigned tech to see if its available. 

[Leo Laohoo]

Thanks Jimmy.  Looking forward to see the result of the *cough* power outage *cough*.

PS:  Make sure no one "trips" over the power cables, ok?  Take it from me, an expert in "tripping over" power cables in a data centre to the point that I've been banned.  LOL!

[Aninda Chatterjee]

Like Leo said, looking at the bootup process will be interesting. That might give us insight on which processor forced the ROMmon. Could you also post the complete show version output please?

Since you can boot the image correctly from ROMmon, that rules out a possible memory corruption issue or a corrupted image. This could be a case of mismatched config registers between the RP and the SP. Could you login to the SP and check what the config register has been set to?

[shain bharati]

try this

6500# remote command switch show boot

BOOT variable = sup-bootdisk:,1;

Configuration register is 0x2102

If configuration Register is not  0X2102 then execute command,

6500# confg t

6500(config)# config-register 0x2102

6500(config)#end

6500#write mem

6500#reload

Verify after reload:

6500#show bootvar

6500#Show Version

6500# remote command switch show boot

Regards,

Shain Bharati CCIE (R&S) #28837