Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Upgrade the NFX250 Software to NFX250 NextGen Software

NFX250 NextGen Software Upgrade Overview

Starting in Junos OS Release 19.1R1, the NFX250 devices support the NFX250 NextGen software architecture. This is a re-optimized architecture that enables you to use JCP as the single point of management to manage all the NFX250 components. For more information about the NFX250 NextGen architecture, see NFX250 NextGen Overview.


For documentation purposes, NFX250 devices that use the reoptimized architecture are referred to as NFX250 NextGen devices.

You can upgrade the software using a USB or through a CLI. This topic provides information about prerequisites and the procedure to upgrade through a CLI from NFX250 software architecture to NFX250 NextGen software architecture.


The upgrade procedure using a USB remains the same for all NFX Series devices.


To upgrade an NFX250 device, you must meet the following prerequisites:

Device-specific prerequisites

  • An NFX250 device with BIOS => CBDE_SFP_00.21_01.01

    To verify the BIOS version:

    For the BIOS information, see the BIOS Information section in the command output message.

    If the BIOS version is not CBDE_SFP_00.21_01.01, you can upgrade the BIOS:

    1. Download the BIOS from Downloads page.

    2. Copy and save the BIOS image to the /var/third-party directory.

    3. From the JDM CLI, access the hypervisor:

    4. Upgrade the BIOS:

      The system generates the following output:

    5. Reboot the device to load new BIOS.

      1. Exit from hypervisor shell:

      2. Reboot the device from JDM CLI.

  • An NFX250 NextGen configuration file with minimal or necessary configurations is required for remote management access to the device after migrating to NFX250 NextGen. This file is an input data for the request system software add clean-install package-name command.

Release-specific prerequisites

The NFX250 software must be compatible with the following releases:

  • NFX250 software running Junos OS Release 18.4R2 or later to accept the configuration by using the command:


    The clean-install command removes all contents on the hard disk. To avoid data loss, copy all important files, configuration files (JDM, JCP, vSRX, and third-party VNFs), log files, and VNF disk or image file, and save them in a secure location before you upgrade the device.

  • Releases prior to 18.4R2 must be upgraded to 18.4R2 or later.


    The NFX250 device will crash if you upgrade the NFX250 software image running Junos OS Release prior to 18.4R2 to a release that supports NFX250 NextGen software image.

    The NFX250 NextGen configuration must be compatible with the NFX250 NextGen software version. The configuration command syntax is not validated.


The NFX250 software architecture and NFX250 NextGen software architecture are different and the configurations are different for both the software.

Upgrade to NFX250 NextGen Software Architecture

Before you upgrade the NFX device:

  • Create backup of the configuration files (JDM, JCP, vSRX, and third-party VNFs), log files, VNF disk or image file, and other important files stored on the device.

  • Check the prerequisites.

To upgrade the NFX250 software architecture to NFX250 NextGen software architecture:

  1. Copy the configuration files that are required for in-band and out-of-band management and save it in the /var/third-party folder. The configuration file should be of the same format as the file format obtained by running the show configuration CLI command.
  2. Copy the NFX250 NextGen software image and save it in the /var/third-party/images folder.
  3. Initiate the software upgrade by using the following command:

    The device is formatted and the NFX250 NextGen software image is installed. The device loads the configurations and boots up the NFX250 Nextgen software image. You can access the device remotely through the in-band and out-of-band management.

  4. The device is now ready for additional configurations and third-party VNF onboarding.