Darren, Sorry you are seeing this; I've never run into this one before. Just to make sure the coherence check isn't missing something, I would example the output of "show ver" and make sure the monitor, boot, app, and fpga code match the other modules in the router. The FPGA file names will differ based on module type, but the rest should match. I would also check the SFM Links to make sure they are all active (show sfm-links all errors), but I don't suspect this is really the cause. Do you have a spare slot you could try to move the module to an see if the problem follows?
Wilbur From: foundry-nsp [mailto:[email protected]] On Behalf Of Darren O'Connor Sent: Wednesday, July 24, 2013 4:16 AM To: Erich Hohermuth; [email protected] Subject: Re: [f-nsp] XMR LP running out of RAM #reload-check Checking for coherence... Done. Reload-check is fine. The line card is showing the right code version. The only difference is that this card was put into this system at a later date. Before the card was put into the system I had upgraded the card itself to the right code version in another XMR. How do I check the boot log of a line card? It would be good to look at that. > Date: Wed, 24 Jul 2013 12:01:52 +0200 > From: [email protected]<mailto:[email protected]> > To: [email protected]<mailto:[email protected]> > Subject: Re: [f-nsp] XMR LP running out of RAM > > Hi, > > This sounds strange to me too. I guess you allready did a > 'reload-check'. Could you do a 'show version' to check the versions on > the LP cards (hardware and software). Cause I had once some strange > issues after I upgraded a linecard directly from 2.4 -> 5.1. > > LP1 (the one which is affected) and LP2 (the one which is ok) > > Next thing what you can do is boot the lp in interactive mode an look > into the boot process if you see something weired (missmatch of monitor > or boot code). > > Regards > Erich
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
