
mays at win
Apr 2, 2012, 11:46 AM
Post #9 of 12
(1155 views)
Permalink
|
> And what is the boot process stating? i.e. when it is booting, does it try and load 124-13b and fail, or simply load 123-22? I have been doing most of this work remote from the site, though I may travel to the site and reboot with a plug into the console port to answer this question. > Is this a case where a bootldr file is needed? Does the ROMMON understand the disk1: filesystem? Again, I haven't gotten much chance to see what the ROMMON thinks, as this is a production system in a remote facility. I do note however that we have two other 7200's that load IOS fine from disk0, but your question led me to look at the Boot info. The other two are running -- ROM: System Bootstrap, Version 12.2(1r) [dchih 1r], RELEASE SOFTWARE (fc1) BOOTLDR: 7200 Software (C7200-BOOT-M), Version 12.0(24)S, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) The system that won't load 12.4 from disk0: is -- ROM: System Bootstrap, Version 12.1(20000710:044039) [nlaw-121E_npeb 117], DEVELOPMENT SOFTWARE BOOTLDR: 7200 Software (C7200-IS-M), Version 12.3(22), RELEASE SOFTWARE (fc2) I tried verifying the file as suggested. gw1.armplc#verify disk1:c7200-is-mz.124-13b.bin %Filesystem does not support verify operations gw1.armplc# _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
|