[f-nsp] NI-MLX-10Gx4 shown as "Invalid Module" maybe due to very old code on lp whlile chassis is on 5.3

[Niels Bakker]

Wilbur gives good advice; I'd like to add to it that the FPGA image 
comes in play in packet forwarding, and you're running into issues 
where the linecard's boot code cannot communicate with the management 
module.  Upgrade boot + monitor + LP image first, then do FPGAs after 
it has come up (and reboot the LP again to activate the new FPGA image).


	-- Niels.

* wsmith at brocade.com (Wilbur Smith) [Wed 24 Jul 2013, 22:31 CEST]:
>Gunther,
>Usually when this happens to me, I can still force the LP to boot 
>into "interactive mode" with the command I mentioned and then 
>manually powering on and off the LP ( power-off lp 4 , power-on lp 
>4). Since the MP's access to the LP uses a separate out-of-band 
>link, the MP should still be able to upgrade the LP if it is in 
>interactive mode.
>
>The MP uses a separate FPGA image to allow it to talk to the chassis 
>backplane; we call this the MBRIDGE image. I would make sure that 
>the MBRIDGE image is the recommended release for your version of 
>code and update if needed. The required version is listed in the 
>release notes for the specific release of code (just search for 
>mbridge). In rare cases, a patch release may need a newer FPGA or 
>MBRIDGE image to fix a problem, so make sure you check the release 
>notes for the exact release (5.3.0 vs. 5.3.0C).
>
>The error you are seeing when you tried to push the fpga code to the 
>LP is triggered because that LP is stuck in reboot. The MP can't 
>communicate with that LP to see if it needs the newer version; we 
>need to stop the reboot loop before we can update the LP. I 
>connected to one of my MLX routers in a lab and double-checked the 
>command you will need. Make sure you are using this command to 
>reboot a module in slot 4:
>
>SSH at EA_CORE-1#lp boot system interactive 4
>
>Let me know if this helps with your issue.
>
>Wilbur
>
>>From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Gunther Stammwitz
>>Sent: Tuesday, July 23, 2013 11:46 AM
>>To: foundry-nsp at puck.nether.net
>>Subject: [f-nsp] NI-MLX-10Gx4 shown as "Invalid Module" maybe due to very old code on lp whlile chassis is on 5.3
>>
>>Hello colleagues,
>>
>>I have more or less a similar problem. I have pushed a NI-MLX-10gX4 
>>into a chassis running 5300e and it didn't work: The module in slot 
>>4 is not even being recognized: it is an "invalid module".
>>
>>Most probably this is due to very old code on the lp while the 
>>chassis runs a newer code.
>>
>>#show mod
>>        Module                             Status      Ports  Starting MAC
>>M1 (left): NI-MLX-MR Management Module     Active
>>M2 (right):
>>F1: NI-X-SF  Switch Fabric Module         Active
>>F2: NI-X-SF  Switch Fabric Module         Active
>>F3:
>>S4: Invalid Module  CARD_STATE_REBOOT   0        xxx
>>(S4: Configured as NI-MLX-10Gx4 4-port 10GbE Module)
>>
>>I can neither access it with "rconsole 4" nor does "boot lp boot 
>>system interactive 4" help.
>>Power-off and power-on didn't help.
>>
>>Wilbur wrote that MP and LP cannot communicate and that the FPGA 
>>needs to be upgraded. I tried to do so, but "copy tftp lp 1.2.3.4 
>>lpfpga05300e.bin fpga-all 4" didn't work.
>>Copying FPGA images to the applicable slot(s), this may take several 
>>minutes... --> No FPGA image to be copied. :(
>>
>>Using copy tftp lp with individual-fpga-images doesn't work either, 
>>the system always claims that the fpga doesn't match.
>>
>>
>>Any idea how to get a LP with very old code working in a chassis 
>>running 5.3-code?
>>
>>You help is being appreciated.
>>
>>>Kind regards
>>Gunther
>

--