[c-nsp] Image in slot0: vs. flash after reload

John Neiberger John.Neiberger at efirstbank.com
Wed Mar 15 09:30:04 EST 2006


I'd have to save the config for that to work. The problem with that is
that the image that is running at the moment is missing some features
that the startup config requires. If I add a boot variable and save,
I'll lose all the commands related to those features.

I still don't understand why the router booted to slot0: instead of
flash. If that is standard behavior, then why was it running the image
in flash before the reload?

John

>>> Atanas Yankov <xds at langame.net> 3/15/06 4:03:54 AM >>>
Simply write boot system slot0:c3640-jk9s-mz.122-31.bin the only thing

that you need to change is name of ios depend on what you have , yes
you 
a right there is no explicit command and you can't see in help context
? 
;))

br,
CCNP Atanas Yankov
Network Administrator
AngelSoft Ltd.


John Neiberger wrote:

>The really weird thing that I can't figure out is that I don't have
any
>"boot system" commands in the config, so why was it running the
correct
>image in flash before it reloaded? I don't understand how that could
>have happened. The router reloaded due to a software forced crash. I
>wonder if that somehow caused it to boot the wrong image? I can't
>imagine that a software forced crash would current the image in
flash.
>Is it possible that the image in flash isn't any good so the router
>automatically decided to try slot0:, even without the "boot system"
>commands?
>
>This is really baking my noodle. I need to figure out why it's
behaving
>this way before I do anything to it.
>
>Thanks!
>John
>--
>
>  
>
>>>>"Buhrmaster, Gary" <gtb at slac.stanford.edu> 3/14/06 3:22:38 PM >>>
>>>>        
>>>>
>That is consistent with my experience.  Not that I like
>it.  I am "guessing" that the presumption was that if
>you had a card in the slot, and there was an image there,
>it was the "newer" one, and the boot flash was the fallback.
>Same thing happens by the way) if you have firmware on 
>flash card.
>
>Thinking about where the 3640 was targeted (remote
>offices), it might have been because it would be
>easier to have updates shipped by flash card, or
>a backup image on a flash card.
>
>Gary
>
>  
>
>>-----Original Message-----
>>From: cisco-nsp-bounces at puck.nether.net 
>>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of John
>>    
>>
>Neiberger
>  
>
>>Sent: Tuesday, March 14, 2006 1:49 PM
>>To: cisco-nsp at puck.nether.net 
>>Subject: [c-nsp] Image in slot0: vs. flash after reload
>>
>>I had a 3640 reload and it booted to the image in slot0: 
>>instead of the
>>image in the on-board flash. Is this expected behavior if no "boot
>>system" statements are in the config? I would have expected it to
>>    
>>
>boot
>  
>
>>to on-board flash unless I specifically told it boot to the image in
>>slot0:, but that is not what happened. 
>>
>>Any thoughts?
>>
>>Thanks,
>>John
>>--
>>_______________________________________________
>>cisco-nsp mailing list  cisco-nsp at puck.nether.net 
>>https://puck.nether.net/mailman/listinfo/cisco-nsp 
>>archive at http://puck.nether.net/pipermail/cisco-nsp/ 
>>
>>    
>>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net 
>https://puck.nether.net/mailman/listinfo/cisco-nsp 
>archive at http://puck.nether.net/pipermail/cisco-nsp/ 
>
>
>  
>

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


More information about the cisco-nsp mailing list