07-28-2009 11:08 AM - edited 03-06-2019 06:59 AM
I was following the procedures to convert CatOS to IOS on a 6500 with Sup-32. During one of the steps, after going into rommon 'priv' mode and doing a reset, it comes back with:
Warning: Rommon NVRAM is corrupted. Initialize the area to default values.
Cat6k-MSFC2A Platform
How does one initialize the are to default values? Is this a recoverable situation?
Solved! Go to Solution.
07-28-2009 12:04 PM
Jim,
I've seen that error before and before opening a TAC case and requesting for a RMA, can you try putting the Supervisor in another slot?
HTH,
__
Edison.
07-28-2009 11:35 AM
This is normally not good...
Try to re-purge the NVRAM from rommon if it lets you do it before it reloads again, if not, I was once able to put back the CatOS on it and re-did the conversion procedure. If not, RMA
rommon 2 > priv
!--- Press Enter or Return.
!--- You have entered ROMmon privileged mode.
!--- You see this output:
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon 3 > fill
!--- Press Enter or Return.
!--- Be sure to enter these parameters exactly:
!--- The first line is a "be" (no space) followed by six zeros ("000000").
!--- The next line is an "8" (no space) followed by four zeros ("0000").
Enter in hex the start address [0x0]: be000000
!--- Press Enter or Return.
Enter in hex the test size or length in bytes [0x0]: 80000
!--- Press Enter or Return.
Enter in hex the pattern to be written [0x0]: ffff
!--- Press Enter or Return.
Enter the operation size 'l'ong, 'w'ord, or 'b'yte []: l
!--- Press Enter or Return.
!--- After the NVRAM erase has completed, issue the reset command.
rommon 4 > reset
!--- Press Enter or Return.
System Bootstrap, Version 12.2(17r)SX3, RELEASE SOFTWARE(fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright(c) 2004 by cisco Systems, Inc.
!--- Output suppressed.
07-28-2009 11:50 AM
I'll try that once again - but that is how this all started. I went through the procedure:
be000000
80000
ffff
l
reset
.....and it was when the system started to reset that the error message popped up.
How did you get CatOS back on? Probably through a procedure as grueling as converting to IOS?
07-28-2009 11:59 AM
If you have the catos .bin file either on bootdisk: or disk0: you can try to load it from rommon.
rommon>dir (bootdisk: | disk0:)
rommon>boot (put the path here)
It sometimes work depending on the progress made on the conversion process.
07-28-2009 12:04 PM
Jim,
I've seen that error before and before opening a TAC case and requesting for a RMA, can you try putting the Supervisor in another slot?
HTH,
__
Edison.
07-28-2009 12:36 PM
Edison - you're the magic man today with that solution! I moved the sup to another slot and it booted to IOS perfectly. Then I moved it back and the same. All is well - thanks!
07-28-2009 12:40 PM
could you update which slots you used?
07-28-2009 12:59 PM
This was in a 6503-E and the sup-32 was in slot 1. Then I moved it to slot 2 at Edisons suggestion. Now it is back in slot 1.
07-28-2009 12:53 PM
just today? [pout]
glad to be of help and thanks for the rating :)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: