This article describes the required steps to be taken when BIOS upgrade fails on QFX5120-32C switch

When we try to upgrade the BIOS version on the switch the below error is seen:

root@jtac-qfx5120-32c:RE:0% sh bioscpldupgradescript.sh

***************************************************************************

BIOS Upgrade Start Date: Sun Jan 19 05:04:49 UTC 2025

BIOS firmware upgrade started

Please wait for some time to complete Upgrade

BIOS firmware upgrade In Progress...Please do not restart/reboot device...

sh: /var/tmp/jfw_pkg_tmp/jfw_pkg/jfirmware_upgrade.py: No such file or directory

BIOS firmware upgrade completed

cat: /var/tmp/bios_upgrade_status: No such file or directory

[: -ne: unexpected operator

BIOS Upgrade is Successful

BIOS Upgrade End Date: Sun Jan 19 05:04:49 UTC 2025

***************************************************************************

CPLD Upgrade Start Date: Sun Jan 19 05:04:49 UTC 2025

CPLD firmware upgrade started

Please wait for some time to complete Upgrade

CPLD firmware upgrade In Progress...Please do not restart/reboot device...

sh: /var/tmp/jfw_pkg_tmp/jfw_pkg/jfirmware_upgrade.py: No such file or directory

CPLD firmware upgrade completed

cat: /var/tmp/cpu_cpld_upgrade_status: No such file or directory

[: -ne: unexpected operator

CPLD Upgrade is Successful

CPLD Upgrade End Date: Sun Jan 19 05:04:50 UTC 2025

***************************************************************************

In the /var/tmp directory below files were copied:

{master:0}

root@jtac-qfx5120-32c> file list /var/tmp 




/var/tmp:

.snap/

LOCK_FILE

alarmd.ts

bioscpldupgradescript.sh

qfx-5e-firmware-22.2R3-S3.18.tgz

rtsdb/

scgi_temp/

sd-upgrade/

test

uploads/

uwsgi_temp/

vi.recover/

The above error is seen while performing the BIOS upgrade if the copied file is qfx-5e-firmware-22.2R3-S3.18.tgz which is a firmware file and not a jfirmware file. In order to perform the BIOS and CPLD upgrade successfully on the QFX5120-32C switch it needs a qfx-5e-jfirmware-22.2R3-S3.18.tgz file which is available in the svl server.

2025-01-19 : Article Created

2025-01-21 : Article Validated