[c-nsp] 6500 hybrid - native conversion crashes

[Sukumar Subburayan]

First we (Cisco)  need to update our CatOS/IOS conversion documentation to 
mention that we need to autoboot RP and not set config-register to 0x0 and 
do manual boot.

So, this is not a workaround but working as expected. The documentation 
needs to be updated. I will follow up with the TAC Engineer and CCO 
documentation folks to get the conversion document updated.

In the  olden days (4 to 5 years ago) there used to be some autoboot 
issues and probably this and subsequent versions of the document 
originated from that, and they never updated it.

Even if the sup-bootflash:, is booted from a different filesystem you 
should be able read/boot from it. In most cases you would be able to even 
write to the linear flash. However, to be safe it is recommended to format 
with the new filesystem.

sukumar





On Sat, 14 Apr 2007, Church, Charles wrote:

> Sukumar,
>
> 	That worked perfectly!  I booted the SP, then:
>
> rommon 2 > BOOT=sup-bootflash:c6sup22-ps-mz.121-27b.E1.bin
> rommon 3 > priv
> rommon 5 > confreg
>
>           Configuration Summary
>   (Virtual Configuration Register: 0x0)
> enabled are:
> [ 0 ] break/abort has effect
> [ 1 ] console baud: 9600
> boot: ...... the ROM Monitor
>
> do you wish to change the configuration? y/n  [n]:  y
> enable  "diagnostic mode"? y/n  [n]:
> enable  "use net in IP bcast address"? y/n  [n]:
> enable  "load rom after netboot fails"? y/n  [n]:
> enable  "use all zero broadcast"? y/n  [n]:
> disable "break/abort has effect"? y/n  [n]:
> enable  "ignore system config info"? y/n  [n]:
> change console baud rate? y/n  [n]:
> change the boot characteristics? y/n  [n]:  y
>
> enter to boot:
> 0 = ROM Monitor
> 1 = the boot helper image
> 2-15 = boot system
> [0]:  2
>
>           Configuration Summary
>   (Virtual Configuration Register: 0x2)
> enabled are:
> [ 0 ] break/abort has effect
> [ 1 ] console baud: 9600
> boot: ...... image specified by the boot system commands or default to:
> cisco2-
> Cat6k-MSFC2
>
> do you wish to change the configuration? y/n  [n]:
>
> You must reset or power cycle for new config to take effect
> rommon 6 > reset
>
>> From here, the RP reset, then started autobooting, and didn't crash.
> Seems like an adequate workaround.  I'm still curious about the
> difference between the CatOS format of a filesystem, verses the IOS
> format.  From what I've read, when you convert the switch to native
> mode, the CatOS format of the sup-bootflash: and any external card
> should be inaccessible from the native IOS.  Yet I'm able to look at
> directories of those filesystems, and read/write files to them.  Is this
> a new feature of IOS or CatOS, or the ROMMONs?  I do see a warning about
> it:
>
> 00:00:49: %C6K_PLATFORM-SP-5-MISMATCH: 'sup-bootflash' device
> programming algori
> thm mismatch detected on SP (module: 1), formatting is recommended.
> 00:00:50: %C6K_PLATFORM-SP-5-MISMATCH: 'slot0' device programming
> algorithm mism
> atch detected on SP (module: 1), formatting is recommended.
>
> I guess I should probably just do it to be safe...
>
> My TAC case is SR 605801489, I'll update the engineer to the
> progress/workaround.
>
> Thanks again,
>
> Chuck
>
> -----Original Message-----
> From: Sukumar Subburayan [mailto:sukumars at cisco.com]
> Sent: Saturday, April 14, 2007 2:51 PM
> To: Church, Charles
> Cc: nsp
> Subject: Re: [c-nsp] 6500 hybrid - native conversion crashes
>
> Charles,
>
> Ignoring the convertion procedure for a second, can you confirm if you
> set the config register on RP to autoboot (0x2102) and then try booting
> the image from SP rommon, whether you see the same crash?
>
> We have seen issues with RP not booting at all  when autoboot is not set
> and user tried to manually boot the image from RP rommon.
>
> If you can unicast me the console login information for your lab setup,
> I can take a look.
>
> sukumar
>