cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12483
Views
0
Helpful
3
Replies

Configuration register is 0x2101 on supervisor720

jkwakman
Level 1
Level 1

Last night I've upgraded a catlyst 6509 (non-redundant), during the upgrade I run into the problem that the 6509 only wants to boot from sup-bootflash, and that it took an old image from sup-bootflash.

I deleted this old image and then the node came into rommon mode.

There I did the boot command and refered to the correct image on disk1:

Now the boot succeeded. Just in time before I run out of my maintenance window.

I did some investigation and looked into the supervisor (using attach 5 and remote command switch show boot) and detected that it's configuration register is on 0X2101 (This is because I run into problems a week ago because of a corrupt flash disk and changed this in rommon mode , without changing it back, I'm afraid I'm not totally known with the 6509)

Question is now how can I change the configuration register back to 0x2102 without any service interruption (It will cost me quit some goodwill if I have to boot the node for the third time in three weeks)??

(Or is it only possible in rommon mode?)

regards, Jack 

1 Accepted Solution

Accepted Solutions

No Probs Jack,

You may wanna close this thread for it to be useful in future.

Thanks,

Nik

HTH,
Niko

View solution in original post

3 Replies 3

nkarpysh
Cisco Employee
Cisco Employee

Hello Jack,

You can changed that in conf t mode:

config-register 0x2102

It will not be immediately applied though. Doing "show ver" you will see that conf-reg is still old value but in brackets it will state that it will change on next reload. So next reload will change config and Sup will boting with the new one. BTW don't forget to "write mem" to synch those changes with standby SUP if you have one.

Before doing reload you can first of all check the boot variable on the Supervisor:

show bootvar

It will show the current confreg and what is more important the image it will try to autoboot on next reload. If nothing specified than it will try the top most image on sup-bootflash: which you experienced on last reload.

You can manually configure prefered image with

boot system  flash FILE_LOCATION

E.G.

boot system flash disk0:image_name.bin

Do then "wr mem" and check that boot variable reflect the correct boot up image  doing "show bootvar".

Hope this helps,

Nik

HTH,
Niko

Nikolav

thanks,

regards,

Jack Kwakman

Tele2 Nederland B.V

From: nkarpysh

To: jkwakman

Date: 03/14/2012 11:50 AM

Subject: - Re: Configuration register

is 0x2101 on supervisor720

Home

Re: Configuration register is 0x2101 on supervisor720

created by Nikolay Karpyshev in LAN, Switching and Routing - View the full

discussion

Hello Jack,

You can changed that in conf t mode:

config-register 0x2102

It will not be immediately applied though. Doing "show ver" you will see

that conf-reg is still old value but in brackets it will state that it

will change on next reload. So next reload will change config and Sup will

boting with the new one. BTW don't forget to "write mem" to synch those

changes with standby SUP if you have one.

Before doing reload you can first of all check the boot variable on the

Supervisor:

show bootvar

It will show the current confreg and what is more important the image it

will try to autoboot on next reload. If nothing specified than it will try

the top most image on sup-bootflash: which you experienced on last reload.

You can manually configure prefered image with

boot system flash FILE_LOCATION

E.G.

boot system flash disk0:image_name.bin

Do then "wr mem" and check that boot variable reflect the correct boot up

image doing "show bootvar".

Hope this helps,

Nik

Reply to this message by going to Home

Start a new discussion in LAN, Switching and Routing at Home

                • IMPORTANT NOTICE ********

This e-mail (including any attachments) may contain information that is

confidential or otherwise protected from disclosure and it is intended

only for the addressees. If you are not the intended recipient, please

note that any copying, distribution or other use of information contained

in this e-mail (and its attachments) is not allowed. If you have received

this e-mail in error, kindly notify us immediately by telephone or e-mail

and delete the message (including any attachments) from your system.

Please note that e-mail messages may contain computer viruses or other

defects, may not be accurately replicated on other systems, or may be

subject of unauthorized interception or other interference without the

knowledge of sender or recipient. Tele2 only send and receive e-mails on

the basis that Tele2 is not responsible for any such computer viruses,

corruption or other interference or any consequences thereof.

No Probs Jack,

You may wanna close this thread for it to be useful in future.

Thanks,

Nik

HTH,
Niko
Review Cisco Networking for a $25 gift card