Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Router(boot)# in a 6500

Hi, I have a 6506, in the first slot there is a WS-X6K-SUP1A-2GE with a MSFC

When i put session 15 the router boots like this:Router(boot)#

I want that it boots normally, how must I do?

Router(boot)#sh bootflash:

-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name

1 .. image E58D8560 1C8500 24 1606784 Mar 25 2000 21:30:40 c6msfc-boot-mz.120-7.XE1

2 .. image 38FCD6C4 8379A0 22 6747168 Mar 25 2000 21:31:10 c6msfc-js-mz.120-7.XE1

7636576 bytes available (8354208 bytes used)

Router(boot)#sh bootvar

BOOT variable = c6msfc-js-mz.120-7.XE1,1;

CONFIG_FILE variable does not exist

BOOTLDR variable = bootflash:c6msfc-boot-mz.120-7.XE1

Configuration register is 0x102

Router(boot)#sh start

Using 328 out of 126968 bytes

!

version 12.0

!

hostname Router

!

boot system flash c6msfc-js-mz.120-7.XE1

boot bootldr bootflash:c6msfc-boot-mz.120-7.XE1

!

ip subnet-zero

Many thanks in advance

3 REPLIES

Re: Router(boot)# in a 6500

With boot system, you also need to specify the flash partion.

My supervisor boot from its own flash-partition, called sup-bootflash.

Please try the following:

Move or copy the image to sup-bootflash

Alter your boot-parameters accordingly, i.e.:

boot system flash sup-bootflash:c6msfc-js-mz.120-7.XE1

Cisco Employee

Re: Router(boot)# in a 6500

The boot command you have is incorrect. The correct boot command would be

config terminal

boot system flash bootflash:c6msfc-js-mz.120-7.XE1

config-register 0x2102

end

write mem

At this time, if you reload, you should be good to go

Re: Router(boot)# in a 6500

In contradiction with the docs it appears that the correct value for the config reg is 0x102. There have been other postings regarding this issue and the conclusion was that: config-register 0x2102 is not correct.

config-register 0x102 is the correct setting for a 6509 supervisor.

regards,

Leo

258
Views
0
Helpful
3
Replies