[c-nsp] 6500/7600 boot issues

Anton Smith anton at huge.geek.nz
Thu Jun 7 17:32:19 EDT 2007


Hi Jon,

I also posted about this awhile ago, and it turned out to be the conf 
register. Once we changed it, it worked fine.

In our case, it would not boot from the sup addon flash, which was a bit 
of a bummer since we needed to use an IOS image that was larger than 64 meg.

A work mate found the conf reg thing, changed it, and now it works fine :).

Regards,
Anton


> Message: 5
> Date: Thu, 7 Jun 2007 15:40:39 -0400 (EDT)
> From: Jon Lewis <jlewis at lewis.org>
> Subject: [c-nsp] 6500/7600 boot issues
> To: cisco-nsp at puck.nether.net
> Message-ID: <Pine.LNX.4.61.0706071516481.3364 at soloth.lewis.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> 
> Several months ago, I posted about a 6509/sup7203bxl we have that won't 
> boot properly without manual help (being told to boot from the rom-mon 
> prompt, or fails-back to booting from sup-bootflash...depending on what 
> rom-mon code we use (upgraded to latest falls back to whatever is in 
> sup-bootflash, gold just sits at rom-mon waiting for an operator to tell 
> it to boot)).  I just noticed something I suspect may be the issue, but 
> I'm not sure how it happened or how to change it.
> 
> The config-register on the supervisor (as shown by rem com sw sh ver) is 
> 0x2142.  On all our other 6500s, both the msfc and sup conf-regs are 
> 0x2102.  How do you change the conf-reg on the supervisor?  Is it as 
> simple as
> rem com sw conf t
> conf-reg 0x2102
> exit
> reload
> 
> I'm a little hesitant to try this on a running router.
> 
> ----------------------------------------------------------------------
>   Jon Lewis                   |  I route
>   Senior Network Engineer     |  therefore you are
>   Atlantic Net                |
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________



More information about the cisco-nsp mailing list