[c-nsp] 5500 Sup3

[Sean Granger]

Absolutely positive.
Nothing out of console or aux.

RAM is on the way regardless, but I figured it was worth asking around.
ESPECIALLY if it does nothing.

>>> Paul Howell <paul.howell at gmail.com> 01/25/05 16:52 PM >>>
Sean,

I have seen this happen before, but there was always a way to get in
the module via console when it is reseated.  Are you sure you are
using a straight-thru cable and not a roll over?  I hate to ask but it
is always good to  check.

Otherwise, I would attempt to put the extra ram in, just to save the module.  

Paul



On Tue, 25 Jan 2005 14:55:38 -0600, Sean Granger
<sgranger at randfinancial.com> wrote:
> I loaded CatOS 6.4.13 on a Sup III (E3) without verifying she had 64MB RAM.
> 
> After the reload, the module comes up red disabled and the standby Sup (Module 1) takes charge ... apparently not having synched the OS (thank god).
> Now, I can't get the other module to come back.
> 
> The current active standby module (running 5.5.20) isn't synching to it, says its STILL synchronizing when I attempt to force the switch and doesn't show Module 2 as being populated, yet when I see what a reset 2 does, the OS certainly sees it, prompting me correctly, "It is standby supervisor module. Reset disabled."
> 
> I'm not even getting any response out of the console when I reload to see if any helpful messages are coming out of it, but now the module is practically dead.
> 
> Anyone see behavior like this before out of these?
> How can I restore this module if I cant even get into ROMMON??
> Will putting in the extra 32MB of required RAM allow it to boot???
> 
> Any suggestions welcomed, Thanks!
> 
> _______________________________________________
> 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/
>