[nsp] Recoving from a bodged 6500 IOS conversion

[Martin Taylor]

Simon,

	The first time the box boots during the conversion it needs an image
on the "bootflash:" (the one on the MFSC, 1 or 2 seem to function the same
during boot process.) After you create a config and store it in NVRAM: it
knows to explode the MFSC boot image out of the Sup image automaticly. I
painfully waded through this process breaking nearly everything that could
be broke. I ended up borrowing a bootflash from another box for the initial
boot and then putting the blank bootflash back in after the conversion was
complete (while it was powered off of course.) The same idea holds true if
you do a "wr erase" on a Layer3 Cat6k, during that initial reload it needs
the c6mfsc2-boot.... type image to come, after that it does care.

Hope that helps,

marty

Marty Taylor - Backbone Network Engineer 	marty at internap.com
Internap Network Services			Work:  404.302.9751
250 Williams Street NW				Cell:  678.778.7274
Suite E-100						Pager: 888.831.3979
Atlanta, GA 30303

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Simon Lockhart
Sent: Thursday, January 09, 2003 2:51 PM
To: Stephen J. Wilcox
Cc: cisco-nsp at puck.nether.net
Subject: Re: [nsp] Recoving from a bodged 6500 IOS conversion

On Thu Jan 09, 2003 at 06:02:43PM +0000, Stephen J. Wilcox wrote:
> you want the sup image on the sup-bootflash and the msfc image on 
> the bootflash
> 
> you seem to have the sup image on the bootflash and no msfc image

No, looking from the ROMMON on each, I believe it sees the sup-bootflash: as

just bootflash: on the sup, and similarly on the msfc.

But, I may be wrong... It seems to do the right thing on the Sup1A tho.

Simon
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/