Nexus module N77-F348XP-23 firmware problems

[Tomasz Truty]

H,

I hope you had great Christmas time! I'm currently working on the new Nexus lab and I have one challenge. 

I'm trying to get 1/10 Gbps Ethernet Module up and running. Do you know where firmware is located for this modules and how to set boot variable for it? What I get so far:

show module:

Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
1 48 1/10 Gbps Ethernet Module N77-F348XP-23 ok
2 48 1/10 Gbps Ethernet Module N77-F348XP-23 powered-dn !! this one I'm having problem with
3 0 Supervisor Module-2 N77-SUP2E active *
4 0 Supervisor Module-2 N77-SUP2E ha-standby

when I'm trying to power it on by entering 

(config)# no poweroff module 2

I'm getting following logs:

2015 Dec 16 00:38:23 xxx %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number JAE19290A6J) Module-Type 1/10 Gbps Ethernet Module Model N77-F348XP-23
2015 Dec 16 00:38:23 xxx %PLATFORM-2-MOD_PWRUP: Module 2 powered up (Serial number JAE19290A6J)
2015 Dec 16 00:38:23 xxx %PLATFORM-5-MOD_STATUS: Module 2 current-status is MOD_STATUS_POWERED_UP
2015 Dec 16 00:40:02 xxx %BIOS_DAEMON-SLOT2-5-BIOS_DAEMON_LC_PRI_BOOT: System booted from Primary BIOS Flash
2015 Dec 16 00:40:05 xxx %FW_APP-SLOT2-2-FIRMWARE_IMAGE_LOAD_ERROR: Firmware extraction and load error: Flash and software firmware images are bad
2015 Dec 16 00:40:06 xxx %MODULE-2-MOD_FAIL: Initialization of module 2 (Serial number: JAE19290A6J) failed
2015 Dec 16 00:40:06 xxx last message repeated 1 time
2015 Dec 16 00:40:06 xxx %PLATFORM-2-MOD_PWRDN: Module 2 powered down (Serial number JAE19290A6J)
2015 Dec 16 00:40:06 xxx %PLATFORM-5-MOD_STATUS: Module 2 current-status is MOD_STATUS_CONFIGPOWERED_DOWN
2015 Dec 16 00:40:06 xxx %PLATFORM-5-MOD_STATUS: Module 2 current-status is MOD_STATUS_POWERED_DOWN

I take the problem is with firmware, but I can't locate the path for it. There is no boot variable set for either module 1 nor 2, but module 1 booted without issues.

xxx# show boot module 1
No module boot variable set
xxx# show boot module 2
No module boot variable set

I can see bin files under
xxx# cd bootflash://module-4/
bootflash://module-4/20150808_221923_poap_7580_init.log bootflash://module-4/vdc_3
bootflash://module-4/20151211_010151_poap_8037_init.log bootflash://module-4/vdc_4
bootflash://module-4/20151211_015441_poap_7723_init.log bootflash://module-4/vdc_5
bootflash://module-4/lost+found bootflash://module-4/vdc_6
bootflash://module-4/n7700-s2-dk9.6.2.12.bin bootflash://module-4/vdc_7
bootflash://module-4/n7700-s2-kickstart.6.2.12.bin bootflash://module-4/vdc_8
bootflash://module-4/scripts bootflash://module-4/vdc_9
bootflash://module-4/vdc_2

but I'm not able to set boot variable to module, I can see sup-1 and sup-2 only

xxx(config)# boot system bootflash://module-4/n7700-s2-dk9.6.2.12.bin ?
<CR>
sup-1 Enter sup-1 to configure the 1st sup
sup-2 Enter sup-2 to configure the 2nd sup

I hope you would be able to help! 

Happ New Year as well! :)

[Wes Austin · Accepted solution]

Hello,

Did you get these linecards at the same time? I see that module 1 is same model and not having issues. Have you opened a TAC SR for the same? I have seen some similar instances where these messages could be result of bad hardware, but you may want to open a TAC case to investigate further.

HTH,

Wes

[Tomasz Truty]

Hi Wes,

Thank you for quick answer!

Yes both cards where delivered at the same time, but only one booted correctly. I didn't open a TAC SR yet, as agreement is still processing... It looks to me as something very basic missing like boot path or IOS .bin file. Is there anything else I could check before opening SR / hardware replace? Nexus architecture is still something new for me

Thanks!

[Chris Frasch]

Hello Tomasz,

I was wondering if you ever got this to work or not? I am seeing the same error on same type of cards.

Thanks,

Chris

******* I worked with TAC and it is a confirmed bug. You will have to either upgrade to 7.x track or work with TAC and get a specific file to upgrade module. *******