[nsp] Booting an MSFC from sup-slot0:
Brian
signal at shreve.net
Thu May 15 03:53:39 EDT 2003
I am working on a 6509 with dual Sup1A's and MSFC's. I am running into
some problems.
I am trying to have the MSFC boot the bootldr image from bootflash:,
but have the regular
IOS image come from sup-slot0:.
I am using Hybrid configuration, CatOS 6.3(7) and MSFC 12.1.13E6.
I can boot the regular IOS image from bootflash:, but not from slot0:
boot system flash sup-slot0: c6msfc-jsv-mz.121-13.E6
boot system flash bootflash: c6msfc-jsv-mz.121-13.E6
boot bootldr bootflash:c6msfc-boot-mz.121-13.E6
Is how I have it configured, this way, after sup-slot0: fails, I am
able to at
least have my IOS.
Some things I have tried and checked:
1. configuration register is 0x2102
2. having just one "boot system flash" line, that points to sup-slot0:,
and no boot line
for bootflash:, still has the same effect.
3. Just as shown above, the boot line for bootflash: comes 2nd.
4. I tried to "boot sup-slot0: c6msfc-jsv-mz.121-13.E6" from rommon>,
this does not work.
5. The IOS checksum / filesize, is correct.
6. Both Sup1A's/MSFC's exhibit the same behavior.
7. while on the MSFC, I can copy succesfully from sup-slot0: to
bootflash:
8. The flashcards in sup-slot0: are Cisco originals, freshly formatted
on the actual
6509 Sup's I am working on.
I was wondering if anyone had any ideas as to what could be my problem.
I read about a take issue with
regards to booting off of sup-slot0: (CSCdr35304) but that bug was long
ago fixed and should not be impacting me.
I used the format "boot system flash sup-slot0:<image name>" because
thats what I found in the Cat6500 Configuration Guide at
http://www.cisco.com/en/US/products/hw/switches/ps708/
products_configuration_guide_chapter09186a008007f29d.html
However, now doing some more searching, I find a conflicting document
on cisco.com that says to use "boot sup-slot0: system_image", that link
is:
http://www.cisco.com/en/US/partner/products/hw/switches/ps708/
products_configuration_guide_chapter09186a00800ebac2.html
Could it be that "boot sup-slot0:<image_name>" is really the correct
format, and that is why it wasn't working for me all along? There are
multiple documents on cisco that show both formats.
I appreciate any help anyone can give me.
Brian Feeny
CCIE #8036
More information about the cisco-nsp
mailing list