Sup720 Bootvar

[jpl861]

Hey Guys,

Just want to ask a quick question.

I'm trying to boot this IOS on a 6506-E, s72033-adventerprisek9_wan-mz.122-33.SXI8.bin.

This is what I see in bootvar.

sh bootvar

BOOT variable = disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin,1;disk0:s72033-ipservicesk9-mz.122-18.SXF8.bin,1;

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby not ready to show bootvar

I want to remove SXF8 and leave SXI8 alone.

I removed both IOS file names in boot system and added the SXI8 again and saved. So this would be the output after.

sh bootvar

BOOT variable = disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin,1;

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby not ready to show bootvar

But after a switch restart, this would be the output of show bootvar again.

sh bootvar

BOOT variable = disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin,1;disk0:s72033-ipservicesk9-mz.122-18.SXF8.bin,1;

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Is there anything I need to check? This is an old engine and I'm not sure if someone modified the variables of the RP.

Thanks in advance.

[Reza Sharifi]

Hi,

Remove the boot variable you don't want:

config t

no boot system disk0:s72033-ipservicesk9-mz.122-18.SXF8.bin,1

Now do a "sh boot" you should only have one statament for SX18 version.

HTH

[jpl861]

I did that and saved. After saving, only SXI8 will appear in show bootvar.

But after a switch restart, the SXF8 will be there again.

[Reza Sharifi]

Can you post the output of "dir disk0:"

or

dir

[jpl861]

dir disk0:

Directory of disk0:/

    1  -rw-   118699876  Mar 13 2013 13:44:26 +00:00  s72033-adventerprisek9_wan-mz.122-33.SXI8.bin

512106496 bytes total (393404416 bytes free)

[cmarva]

2 possibilities that I can think of.

1- the sp boot variable is not syncing to the rp boot variable when you do a wri mem. To see this, from the console do a

    sho boot (this is the rp)

    remote command switch sho boot (this is the sp)

they should match. If they do not, even after repeated saves, that leads to possibility 2.

2 - what are your rp and sp rommon versions? Seems like I recall a bug similar to this that was fixed in a rommon

    update.

chris

[jpl861]

Thanks Chris!

That's what I am suspecting as well as I haven't checked before I left the data center. Like I said, this is an old card that we just reused. When I first configured the switch and set the proper variables, it always goes to rommon mode when i restart even if the boot variable is correct. I found out that it was forced to boot in rommon all the time so i had to change it from 0 to 2 and that fixed the restart problem.

But right now I'm not sure where this would lead me as the bootvar is always different. Here's the bootvar of the remote command.

remote command switch show bootvar

BOOT variable = disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin,1;

CONFIG_FILE variable does not exist

BOOTLDR variable does not exist

Configuration register is 0x8002 <----- This is not what I see in my other Sup720s.

show boot

BOOT variable = disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin,1;

CONFIG_FILE variable =

BOOTLDR variable =

Configuration register is 0x2102

Standby not ready to show bootvar

[cmarva]

ok, that leads somewhere......the sp config register is not sync'd even though the boot variable is.

from the console,

remote login switch

conf t

config-register 0x2012

ctrl-z

ctrl-c ctrl-c ctrl-c to get back to the rp console

wri mem

then do a remote comm sw sh bootv and see if it says it will be 2102 next reload. If so, then all you should have to do is reload and it should boot to the right code.

If this is not production, then you can play around a little. Not sure what 8002 is but I've never seen that as a setting, even after conversion from hybrid to native.  I'd still look at making sure the rp and sp rommons are updated (if they are not).

good luck, chris

[jpl861]

Hi Chris,

Thank you so much for your feedback.

Is there any way I can do this over SSH? I'm not going back to the data center any time this week and I don't have console access.

I cannot do a conf t over remote command on the sp.

Thanks,

John

[cmarva]

oops, me and my big mouth. Give this a try.......

if you have ssh access to it, then just ssh to it,

conf t

config-register 0x2102

ctrl-z

wri mem

then do remote comm sw sh bootv and see if it is now showing 0x2102.

this will be from the rp, but the sp register might sync when you do the wri mem. If it does, you should be good upon a reboot. If the registers don't sync, then I think the only other way will be to break the bootup.

[jpl861]

I have done that. Remove sxf8 and retained sxi8, saved, and the show bootvar displays it correctly in the RP. But when I restart the switch, the RP's bootvar will rollback to the old settings. I think the only way to fix this is via ctrl+break.

[paul driver]

Hello

Try clearing the whole bootvariable and re-adding ios in order of preference reload.

en

conf t

no boot system

boot system flash disk0:s72033-adventerprisek9_wan-mz.122-33.SXI8.bin

boot system flash disk0:s72033-ipservicesk9-mz.122-18.SXF8.bin

wr

sh bootvar

res

Paul

Please don't forget to rate any posts that have been helpful.

Thanks.

[jpl861]

Got this response from TAC.

There is a bug CSCsv03353 related to rommon software, more info you can find here:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsv03353

This problem is cosmetic. "show bootvar" returns the boot variable for the routing processor while it is the one on the switching processor that determines the image to boot.

I upgraded the ROMMON software and the problem cleared.