Description

This article provides information regarding the steps to migrate from vSRX2.0 to vSRX3.0.

Symptoms

The new vSRX3.0 architecture is a streamlined virtual machine (VM) using FreeBSD 12.x / Junos OS as operating system. In vSRX3.0, the Routing Engine and the Packet Forwarding Engine run on FreeBSD 12.x or later version as single VM for improved performance and scalability. The vSRX3.0 uses DPDK to process the data packets in the data plane.

You must deploy a new vSRX Virtual Firewall VM to migrate from the legacy vSRX2.0 to the new vSRX3.0. You do so by downloading a supported vSRX Virtual Firewall image from Juniper Support page and installing it on your server.

Use the following steps to migrate to vSRX3.0 :
  1. Check vSRX Virtual Firewall Version
  2. Pre-Migration Checklist
  3. Migration Procedure
  4. Post-Migration Tasks

Solution

  1. Check vSRX Virtual Firewall Version :
           Check if your vSRX Virtual Firewall instance has vSRX2.0 or vSRX3.0 using the show version command
           [ Note: In the output, the field Model: vsrx with letters srx in lowercase represents vSRX2.0 whereas the field Model: vSRX with letters SRX in uppercase represents vSRX3.0 ]

      2. Pre-Migration Checklist :
  1. Check Junos OS version on your vSRX Virtual Firewall instance.
  2. Save the active configuration without any uncommitted changes. 
user@host-01> show configuration | save /var/tmp/filename.txt
  3. Check your license requirements. You might need a new license key, or you can re-apply the existing one. 
  • If you require new license keys, obtain them from the Juniper Agile Licensing (JAL) portal (https://license.juniper.net/licensemanage/)
  • If you can re-apply the existing license key, save a copy of license file using the following steps:
    • Display license keys installed on your vSRX Virtual Firewall from the operational mode using the command show system license keys 
    • Copy license keys or save license keys to a file or URL using the command request system license save filename | url 
             4. Backup any other files on the vSRX2.0 VM, which you might require on the new vSRX3.0 VM (such as IPsec VPN certificates and scripts)
                 (if applicable).
             5. Ensure you have your server/host OS ready and setup the required virtual networks and storage pool in the host OS.
             6. Power-off your vSRX2.0 VM before you start deploying the new vSRX3.0 VM.

     3. Migration Procedure :
         
          Use the following steps to migrate from vSRX2.0 to vSRX3.0 :
  1. Navigate to the Juniper Networks Support page for the vSRX3.0 (https://support.juniper.net/support/downloads/?p=vsrx3) and select OS as vSRX3.0 and select the required versions.
  2. Enter your credentials and review/accept the End User License Agreement. You’ll be guided to the software image download page. Follow the instructions on the page and download the Junos OS image file.
  3. Install the downloaded vSRX Virtual Firewall VM on your server. [ When you download a vSRX3.0 image, the image file name includes vsrx3. ]
  4. Check Junos OS and vSRX Virtual Firewall version after a reboot using the show version command.
 
     4. Post-Migration Tasks :        

          Complete the following checks after you install new Junos OS with vSRX3.0 :
  1. Launch the new vSRX Virtual Firewall instance with vSRX3.0 on your server.
  2. Enable network access (for example by configuring an IP address on the fxp0 interface). This step enables you to transfer files to the new vSRX3.0 VM.
  3. Apply the license keys (the existing keys or new keys) on the newly launched vSRX Virtual Firewall instance.
  4. If you are using a chassis cluster setup, enable chassis cluster on the new vSRX3.0 using the set chassis cluster cluster-id X node [0|1] command and reboot VMs.
  5. Transfer any other files that you have taken a backup from vSRX2.0 VM such as IPsec VPN certificates and scripts (If applicable).
  6. Copy the config file you saved earlier back to the /var/tmp folder.
  7. Run the load override /var/tmp/filename.txt in the configuration mode to replace the current configuration with the saved configuration.
  8. Commit the configuration.
  9. Ensure your device settings, network settings, and other configuration are available using the show configuration command.
     

Modification History

Added Documentation link for reference

Related Information

Documentation link : Migrate to vSRX3.0