[f-nsp] ServerIron CPU crash

Fabio Mendes fabio.mendes at bsd.com.br
Tue Nov 29 06:04:18 EST 2011


Hi Chris, thank you for your answer.

The problem was a hardware issue.

BTW, I don't know about you guys, but in the last couple of months we had A
LOT of problems with brocade/foundry hardware, specially with SuperX
management modules.

It looks like the hardware just reach its expiration date =D.

Boy, it has been a huge pain in the ass for us and our customers...




2011/11/26 Chris Good <chris at g2.nu>

> Fabio Mendes wrote:
> > My question is, if any of you have faced this, was the problem caused by
> > hardware, software or misconfiguration ?
>
> If it is a new acquisition and the WSMs aren't showring their code version
> then it may be that you have a code mismatch between the WSM and management
> card.
>
> If that is the case set the WSMs to come up manually:
>
> wsm boot interactive
>
> You can then boot the code via tftp:
>
> wsm boot tftp tftp_server_ip wsm-code-ver.bin
>
> If that does the trick then download the code to the primary/secondary as
> appropriate:
>
> wsm copy tftp flash tftp_server_ip wsm-code-ver.bin primary
> wsm copy tftp flash tftp_server_ip wsm-code-ver.bin secondary
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20111129/ed651527/attachment.html>


More information about the foundry-nsp mailing list