Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support
Starting in Junos OS Release 24.1R1, in order to install VM Host image based on Linux WR LTS22, you have to upgrade the i40e NVM firmware to version 9.1 or later.
Starting in Junos OS Release 21.4 R1, in order to install VM Host image based on Linux WR LTS19, you have to upgrade the i40e NVM firmware to version 7.0 or later. . However, if the Junos OS version is upgraded to 21.4R1 or later using the standard Junos OS upgrade process, the i40e NVM firmware upgrade is done automatically during the upgrade process. The corresponding i40e driver version to support i40e NVM version 7.0 will be version 2.8.43 (or later).
i40e NVM version 6.01 is the prerequisite to install a LTS19 based image, else image installation will fail.
In Junos OS Release 24.1R1 and later, ssh is disabled by default on all the routers with VM Host support (except SRX).
The i40e NVM firmware downgrade is not supported if the Junos OS version running on the system is downgraded from Junos OS 21.4R1. Hence, it is required to install a Junos OS version which supports the corresponding i40e NVM firmware version installed in the Routing Engine.
Starting in Junos OS Release 22.3R1, when you upgrade your device from Junos OS version 18.2R1 to 22.3R1, the i40e NVM firmware is automatically upgraded from version 4.26 to version 7.0
Table 1 lists the Junos OS releases contain both i40e driver version 2.8.43 and i40e driver version 2.4.3 to support both i40e NVM firmware version 6.01 and i40e NVM firmware version 7.0. Hence, they could be used on the Routing Engine which is running i40e NVM firmware version 6.01 or 7.0.
For JUNOS images prior to the listed versions below, i40e NVM firmware version 7.0 is not supported.
19.3 |
19.4 |
20.1 |
20.2 |
20.3 |
20.4 |
21.1+ |
---|---|---|---|---|---|---|
19.3R2-S6 |
19.4R1-S4 |
20.1R2-S2 |
20.2R2-S3 |
20.3R1-S2 |
20.4R1-S1 |
21.1R1 and higher |
19.3R3-S2 |
19.4R2-S4 |
20.1R3 |
20.2R3 |
20.3R2 |
20.4R2 |
|
19.4R3-S2 |
20.3R2-S1 |
|||||
19.4R3-S3 |
20.3R3 |
|||||
20.3X75-D10 |
Starting in Junos OS Release 19.3R1, in order to install VM Host image based on Linux WRL9, you have to upgrade the i40e NVM firmware to version 6.01.
Table 2 lists the Junos OS releases which support i40e NVM firmware upgrade.
Platform |
15.x |
16.x |
17.x |
18.x |
19.x |
21.x |
---|---|---|---|---|---|---|
EX9208 |
15.1F6-S11 |
15.1F6-S11 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
|
PTX5000 |
15.1F6-S11 |
16.1R7 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
|
PTX3000 |
Not applicable |
Not applicable |
Not applicable |
18.2R3 / 18.3R3 / 18.4R2 |
19.1R2 / 19.2R1 |
|
MX240 / MX480 / MX960 / MX2010 / MX2020 |
15.1F6-S11 |
16.1R7 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
|
MX2008 |
Not applicable |
Not applicable |
Not applicable |
18.2R3 / 18.3R3 / 18.4R2 |
19.1R2 / 19.2R1 |
|
MX10016/MX10008 PTX10016/MX10008 |
Not applicable |
Not applicable |
Not applicable |
18.2R3 / 18.3R3 / 18.4R2 |
19.1R2 / 19.2R1 |
|
SRX5400/ SRX5600/ SRX5800 (Supported only on SRX5K-RE3-128G) |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
Not applicable |
21.4 |
The following Junos OS Releases support automatic i40e NVM firmware upgrade from version 4.26 to version 7.00. This allows you to upgrade devices directly from older Junos OS Releases like 18.2 to Junos OS Releases 21.4 and higher.
-
21.4R3-S5 and higher
-
22.1R3-S3 and higher
-
22.2R3-S1 and higher
-
22.3R3 and higher
-
22.4R3 and higher
-
23.1R2 and higher
-
23.2R2 and higher
-
23.3R1 and higher
-
23.4R1 and higher
You can install older Junos OS images on the Routing Engine with an upgraded i40e NVM firmware as it supports i40e 2.4.3 driver versions. If you install an older version of the VM Host image, which is not listed in Table 3, using USB, the Routing Engine does not start up properly. In such a case, you can reinstall the VMHost image with a version which supports the new i40e NVM firmware.
Table 3 lists the platforms with NVM-6.01 firmware support.
Platform |
i40e-1.1.23/ NVM-4.26 Support |
i40e-2.4.3/ NVM-6.01 Support |
||||
---|---|---|---|---|---|---|
EX9208 |
15.1F3 |
15.1F6-S11 |
16.1R7 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
PTX5000 |
15.1F3 |
15.1F6-S11 |
16.1R7 |
17.1R3/ 17.2R3 / 17.3R3/ 17.4R2 |
18.1R1 / 18.2R3 / 18.3R1 / 18.4R1 |
19.1R1 or later |
PTX3000 |
16.1R4 |
Not applicable |
16.1R7 |
17.3R3-S6 / 17.4R2-S7 |
18.2R3-S8 / 18.2R3 / 18.3R3 / 18.4R2 |
19.1R2/ 19.2R1 |
MX240/MX480/MX960 |
15.1F3 |
15.1F6-S11 |
16.1R7 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
MX2010/MX2020 |
15.1F5-S1 |
15.1F6-S11 |
16.1R7 |
17.1R3 / 17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
MX2008 |
15.1F7 |
Not applicable |
Not applicable |
17.2R3 / 17.3R3 / 17.4R2 |
18.1R1 / 18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
MX10016/MX10008 PTX10016/MX10008 |
18.2R1 |
Not applicable |
Not applicable |
Not applicable |
18.2R1 / 18.3R1 / 18.4R1 |
19.1R1 or later |
i40e-NVM upgrade is optional for the following platforms:
-
MX10003
-
PTX10002-XX
-
QFX1000, QFX10002
-
QFX5000
-
You must upgrade i40e NVM firmware only under the direction of a Juniper Networks support representative. Once you upgrade the NVM firmware, a downgrade action is not supported. For latest update, you can refer https://kb.juniper.net/.
-
You must implement this procedure with a router console access. Also, you have to perform power cycling of the routing Engine multiple times during the firmware upgrade process.
Before you begin upgrading the firmware, check the current firmware version of the i40e NVM.
user@host> show system firmware Part Type Tag Current Available Status version version Routing Engine 0 RE BIOS 0 0.53.1 OK Routing Engine 1 RE BIOS 0 0.43 0.53 OK Routing Engine 1 RE FPGA 1 28.0.0 41.0 OK Routing Engine 1 RE SSD1 3 0.0.0 OK Routing Engine 1 RE SSD2 3 0.0.0 OK Routing Engine 1 RE i40e-NVM 7 4.26 OK
If the value of Current version
is less than 6.01
, then you can use the following procedure for the i40e NVM firmware upgrade.
To upgrade i40e NVM firmware on routers with single Routing Engine:
On routers with dual Routing Engines, you must use the request chassis cb (offline | online) slot slot-number
to power cycle the Routing Engine. Thereby, you can avoid using an external power cycler and avoid abrupt power cycling of backup RE, which may cause file system errors.
To upgrade i40e NVM firmware on routers with dual Routing Engines:
You must disable GRES before proceeding with the upgrade procedure. However, if you disable GRES in the beginning of the procedure, the device needs more number of switchovers for upgrading both the Routing Engines. Hence, to reduce the number of switchovers, it is recommended to upgrade the secondary Routing Engine first and then upgrade the primary Routing Engine .
Upgrade the device with the Junos OS image version which supports i40e NVM firmware upgrade. See Table 2.
Copy and install the jfirmware-vmhost package to the device.
If the file has been obtained from JTAC, use FTP or SCP to load the firmware file on the device. Save the file in the
/var/tmp
directory.user@host> request vmhost software add /var/tmp/jfirmware-vmhost-x86-64-19.2R1.tgz
Upgrade the NVM firmware.
To initiate the upgrade, use the following command:
user@host> request system firmware upgrade re i40nvm Part Type Tag Current Available Status version version Routing Engine 1 RE i40e-NVM 7 4.26 6.01 OK Perform indicated firmware upgrade ? [yes,no] (no) yes Firmware upgrade initiated, use "show system firmware" after reboot to verify the firmware version
Monitor the upgrade status by using the
show system firmware
command. If the upgrade is initiated the output displaysPROGRAMMING (0%)
as the status. However, note that the statusPROGRAMMING (0%)
does not increment during the process.user@host> show system firmware Part Type Tag Current Available Status version version Routing Engine 0 RE BIOS 0 0.53.1 OK Routing Engine 1 RE BIOS 0 0.43 OK Routing Engine 1 RE FPGA 1 28.0.0 OK Routing Engine 1 RE SSD1 3 0.0.0 OK Routing Engine 1 RE SSD2 3 0.0.0 OK Routing Engine 1 RE i40e-NVM 7 4.26 6.01 PROGRAMMING (0%)
Switch to the backup Routing Engine by using the
request chassis routing-engine master switch
command to switch primary role to other RE (i.e, RE1).Note:This step is necessary, because in Step 6 you have to power cycle the Routing Engine which is undergoing the NVM upgrade (i.e, RE0) from RE1
user@host> request chassis routing-engine master switch Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The other routing engine becomes the master.
Reboot the device by using the
request vmhost reboot
command from the Routing Engine which is undergoing the NVM upgrade (i.e, RE0).user@host> request vmhost reboot
Monitor the console output. You may have to perform power recycle of the Routing Engine multiple times. When you are prompted for a power cycle on your console, use external power cycle for power cycling the Routing Engine. Or, you can use the command
request chassis cb slot slot offline
as described in Step 6.The following message is displayed on the console prompting you to perform a power cycle:
“Please Power Cycle your system now and run the NVM update utility again to complete the update. Failure to do so will result in an incomplete NVM update. Upgrade complete please power reboot You may notify to power reboot again after reboot if required”
From RE1, power cycle the RE0 using following command
request chassis cb slot slot offline
.To power off RE0, use the command
request chassis cb slot 0 offline
and to power on RE0, use the commandrequest chassis cb slot 0 online
.user@host> request chassis cb slot 0 offline Offline initiated, use "show chassis environment cb" to verify
user@host> request chassis cb slot 0 online Online initiated, use "show chassis environment cb" to verify
After a successful upgrade, verify the version of the firmware.
Note:The
Current version
is displayed as 6.1 instead of 6.01.user@host> show system firmware Part Type Tag Current Available Status version version Routing Engine 0 RE BIOS 0 0.53.1 OK Routing Engine 1 RE BIOS 0 0.43 OK Routing Engine 1 RE FPGA 1 28.0.0 OK Routing Engine 1 RE SSD1 3 0.0.0 OK Routing Engine 1 RE SSD2 3 0.0.0 OK Routing Engine 1 RE i40e-NVM 7 6.1 6.01 OK
Note:In case, you have run the
request vmhost snapshot
command with a Junos OS image which does not support i40e NVM firmware upgrade, (if the SSD recovery snapshot has a Junos OS version older than the Junos OS versions mentioned in Table 3) we recommend you to take a snapshot using therequest vmhost snapshot
command again. Hence, in case of a recovery process, the SSD recovery snapshot will have a Junos OS image which supports NVM 6.01.Similarly, while upgrading i40e NVM on RE1, power cycle RE1 from RE0.
user@host> request chassis cb slot 1 offline Offline initiated, use "show chassis environment cb" to verify
user@host> request chassis cb slot 1 online Online initiated, use "show chassis environment cb" to verify
You need to perform this step only if the image you downloaded does not contain debugfs based mechanism to stop LLDP.
Download the lldp-patch-for-i40e-upgrade.tgz package. Copy and install the file in the /var/tmp/ directory on each Routing Engine.
user@host> request vmhost software add /var/tmp/lldp-patch-for-i40e-upgrade.tgz Verified lldp-patch-for-i40e-upgrade signed by PackageDevelopmentEc_2018 method ECDSA256+SHA256 [ re_name = RE-PTX-2X00x8 ] Pushing script(s) to host ... Install the script(s) under host-os.... Script(s) copy done
user@host>show version | match lldp lldp-patch-for-i40e-upgrade
Reboot the device by using the
request vmhost reboot
command. The upgrade process is complete when the Routing Engine comes back online.user@host> request vmhost reboot
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.