Fex: Image update failed [/isan/plugin_img/fexth.bin]: File transfer error

Joris Deprouw · ‎02-23-2014

Hi all,

We have 2 cisco Nexus 5596 devices. We also have 24 fexes (N2K-C2248TP-1GE) connected with vpc to both devices.

We tried to upgrade the NX-OS from 5.1.3.N2.1 to 5.2.1.N1.7.

During the upgrade we got an error on fex 109. The other fexes gave no error.

2014 Feb 21 23:35:26 nex-5596 %$ VDC-1 %$ %SATCTRL-FEX109-2-SATCTRL_IMAGE: FEX109 Image update failed [/isan/plugin_img/fexth.bin]: File transfer error

2014 Feb 21 23:35:28 nex-5596 %$ VDC-1 %$ %SATCTRL-FEX122-2-SATCTRL_IMAGE: FEX122 Image update in progress.

2014 Feb 21 23:35:38 nex-5596 %$ VDC-1 %$ %SATCTRL-FEX123-2-SATCTRL_IMAGE: FEX123 Image update in progress.

2014 Feb 21 23:35:48 nex-5596 %$ VDC-1 %$ %SATCTRL-FEX124-2-SATCTRL_IMAGE: FEX124 Image update in progress.

2014 Feb 21 23:36:23 nex-5596 %$ VDC-1 %$ %SATCTRL-FEX101-2-SATCTRL_IMAGE: FEX101 Image update complete. Install pending

I have tried shutting down the power of fex 109 and restarting the upgrade. And I have tried executing the upgrade from the second 5596. But both without success.

When I do a sh fex 109 detail, I can see the following in the logs:

02/21/2014 23:33:28.586594: Module image preload in progress

02/21/2014 23:35:26.378579: Image preload failed.

Any ideas?

Thanks,

Best Regards,

Joris

Joris Deprouw · ‎02-28-2014

Hi All,

Most likely is this a L1 issue. Faulty fiber of sfp.

You can check this by doing “sh fex x transceiver detail”. You can see that the RX Power values for fex 1 are very low. This is probably the reason why the tftp session from N5k to fex 1 fails during the upgrade.

Fex 2 doesn’t show this issue.

Once we have replaced the fibers I'll know more and I'll post the results.

Best Regards,

joris

5596# sh fex 1 transceiver detail

Fex Uplink: 1

Fabric Port: Ethernet1/x

sfp is present

name is CISCO-FINISAR

type is Fabr

part number is x

revision is A

serial number is x

nominal bitrate is 10300 MBits/sec

Link length supported for 50/125mm fiber is 0 m(s)

Link length supported for 62.5/125mm fiber is 0 m(s)

cisco id is --

cisco extended id number is 4

SFP Detail Diagnostics Information

----------------------------------------------------------------------------

Alarms Warnings

High Low High Low

----------------------------------------------------------------------------

Temperature 33.92 C 75.00 C 5.00 C 70.00 C 10.00 C

Voltage 3.31 V 3.63 V 2.97 V 3.46 V 3.13 V

Current 7.85 mA 11.80 mA 4.00 mA 10.80 mA 5.00 mA

Tx Power -2.42 dBm 2.69 dBm -11.30 dBm -1.30 dBm -7.30 dBm

Rx Power -13.27 dBm -- 2.99 dBm -13.97 dBm -1.00 dBm -9.91 dBm

----------------------------------------------------------------------------

Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning

-

5596# sh fex 2 transceiver detail

Fex Uplink: 1

Fabric Port: Ethernet1/x

sfp is present

name is CISCO-FINISAR

type is Fabr

part number is x

revision is A

serial number is x

nominal bitrate is 10300 MBits/sec

Link length supported for 50/125mm fiber is 0 m(s)

Link length supported for 62.5/125mm fiber is 0 m(s)

cisco id is --

cisco extended id number is 4

SFP Detail Diagnostics Information

----------------------------------------------------------------------------

Alarms Warnings

High Low High Low

----------------------------------------------------------------------------

Temperature 33.34 C 75.00 C 5.00 C 70.00 C 10.00 C

Voltage 3.29 V 3.63 V 2.97 V 3.46 V 3.13 V

Current 7.84 mA 11.80 mA 4.00 mA 10.80 mA 5.00 mA

Tx Power -2.39 dBm 2.69 dBm -11.30 dBm -1.30 dBm -7.30 dBm

Rx Power -2.36 dBm 2.99 dBm -13.97 dBm -1.00 dBm -9.91 dBm

----------------------------------------------------------------------------

Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning

arickenbach · ‎03-28-2014

A bad fibre can really be a problem.

The same problem was solved with a correct fiber connection.