[prev in list] [next in list] [prev in thread] [next in thread]
List: foundry-nsp
Subject: Re: [f-nsp] XMR LP running out of RAM
From: Wilbur Smith <wsmith () brocade ! com>
Date: 2013-07-24 21:47:27
Message-ID: 72FD3E9D470B0547B4A50ACA988B43860FC1E37416 () BRM-EXCH-4 ! corp ! brocade ! com
[Download RAW message or body]
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:foundry-nsp-bounces@puck.nether.net] On Behalf Of Darren \
O'Connor
Sent: Wednesday, July 24, 2013 4:16 AM
To: Erich Hohermuth; foundry-nsp@puck.nether.net
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: erich@hoh.ch<mailto:erich@hoh.ch>
> To: darrenoc@outlook.com<mailto:darrenoc@outlook.com>
> 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
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Darren,<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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? <o:p></o:p></span></p><p class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Wilbur<o:p></o:p></span></p><p \
class=MsoNormal><span \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div \
style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p \
class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> foundry-nsp \
[mailto:foundry-nsp-bounces@puck.nether.net] <b>On Behalf Of </b>Darren \
O'Connor<br><b>Sent:</b> Wednesday, July 24, 2013 4:16 AM<br><b>To:</b> Erich \
Hohermuth; foundry-nsp@puck.nether.net<br><b>Subject:</b> Re: [f-nsp] XMR LP running \
out of RAM<o:p></o:p></span></p></div></div><p \
class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal \
style='margin-bottom:12.0pt'><i><span \
style='font-family:"Calibri","sans-serif"'>#reload-check<br>Checking for \
coherence...<br>Done.</span></i><span \
style='font-family:"Calibri","sans-serif"'><br><br>Reload-check is fine. <br><br>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.<br><br>How do \
I check the boot log of a line card? It would be good to look at \
that.<br><br><br><br><o:p></o:p></span></p><div><p class=MsoNormal><span \
style='font-family:"Calibri","sans-serif"'>> Date: Wed, 24 Jul 2013 12:01:52 \
+0200<br>> From: <a href="mailto:erich@hoh.ch">erich@hoh.ch</a><br>> To: <a \
href="mailto:darrenoc@outlook.com">darrenoc@outlook.com</a><br>> Subject: Re: \
[f-nsp] XMR LP running out of RAM<br>> <br>> Hi,<br>> <br>> This sounds \
strange to me too. I guess you allready did a<br>> 'reload-check'. Could you do a \
'show version' to check the versions on<br>> the LP cards (hardware and software). \
Cause I had once some strange<br>> issues after I upgraded a linecard directly \
from 2.4 -> 5.1.<br>> <br>> LP1 (the one which is affected) and LP2 (the one \
which is ok)<br>> <br>> Next thing what you can do is boot the lp in \
interactive mode an look<br>> into the boot process if you see something weired \
(missmatch of monitor<br>> or boot code).<br>> <br>> Regards<br>> \
Erich<o:p></o:p></span></p></div></div></div></body></html>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
--===============3560616022864578852==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic