Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Upgrading the Personality of QFX10002-60C and PTX10002-60C Devices

The installed image on your devices determines the personality of the device. Juniper Networks offers benefits of changing the personality of your device. You can install the image of QFX10002-60C in PTX10002-60C device and vice versa. You can install the new personality via Preboot Execution Environment (PXE) boot method boot, USB, CLI, and ZTP.

Upgrading the Personality of QFX10002-60C and PTX10002-60C Devices Using the PXE Boot Server

You can configure your QFX10002-60C device as a PTX10002-60C device or your PTX10002-60C device as a QFX10002-60C device. The image loaded on the device determines the personality of the device. For example, if you have purchased a QFX10002-60C device, the installed personality is a QFX10002-60C device. When you upgrade the QFX10002-60C device to a PTX10002-60C device, the new personality of the device is a PTX10002-60C device. Similarly, if you have purchased a PTX10002-60C device, the installed personality is a PTX10002-60C device and the new personality, if you upgrade, is a QFX10002-60C device.

You can install the new personality on the devices using Preboot Execution Environment (PXE) boot method. A PXE boot prepares a client/server environment to boot devices by using a network interface that is independent of available data storage devices or installed operating systems. The image of the operating system is stored on a TFTP server. You can have separate PXE boot servers for each image.

Note:

When you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C default configuration is deleted, and the PTX10002-60C configuration becomes the default configuration. When you upgrade the PTX10002-60C personality to a QFX10002-60C personality, the PTX10002-60C default configuration is deleted, and the QFX10002-60C configuration becomes the default configuration. Additionally, the software snapshot in the secondary disk is deleted, and the new software snapshot is installed in the secondary disk. For example, if you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C snapshot is deleted, and the PTX10002-60C snapshot is installed in the secondary disk.

Note:

When you order the spare JNP10002-60C-CHAS, it is preloaded with the QFX10002-60C and PTX10002-60C software images in the /var/tmp location. If you want to convert a QFX10002-60C device to a PTX10002-60C device, use the PTX10002-60C image. If you want to convert a PTX10002-60C device to QFX10002-60C device, use the QFX10002-60C image.

For example, to upgrade the QFX10002-60C device from the installed personality of QFX10002-60C to the new personality of PTX10002-60C device using the PXE Boot Server Option:

  • Copy the image you want installed on the QFX10002-60C device to the PXE Boot Server.

  • Reboot the device to install the image.

Note:

If you have already copied the image to the PXE Boot server, reboot the device to install the image.

To copy the image you want installed to the PXE Boot Server:

  1. Copy the downloaded installation media to the /var/tmp directory in the PXE boot server.

    For example:

  2. Log in to the PXE boot server and verify the installation file.
  3. Extract the junos-vmhost-install-net TAR file.
  4. Remove the previously installed files, if any, from the /tftpboot directory.
  5. Extract the network installation package.
  6. Rename or delete the previously installed root file system/scripts from the /var/install directory. Create a new /var/install directory.
  7. Extract the installation package.
  8. Verify that the /var/install folder contains the attributes file. If the file does not exist in the specified location, copy the attribute file.
    Note:

    The attribute file consists of the personality information of the image. If the attributes file is not present, the device is unable to upgrade to the new personality even when the PXE boot server has the relevant image.

  9. Set permissions for the files in the /var/install and /tftpboot directories.
  10. Exit the PXE boot server.

After you copy the image to the PXE Boot Server, to install the image on the device, reboot the device to install the image. You can use the request vmhost reboot network command to install the image. The device boots from the PXE server and installs the image on both the SSDs. However, if the device fails to reboot, you can use the USB disk installation option. If the device fails to reboot or is not accessible, follow these steps:

  1. Power cycle the device.

  2. Press the ESC button to go to the Boot Manager Menu.

  3. Select Boot Manager, and then press Enter.

  4. Select ETH00 (xx:xx:xx:xx:xx:xx) option. A warning message is displayed. At the prompt, select y to install the image on both the primary and secondary disks.

  5. In operational mode, verify that the upgrade is successful.

Note:

Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.

Upgrading the Personality of QFX10002-60C and PTX10002-60C Devices Using the USB Option

You can configure your QFX10002-60C device as a PTX10002-60C device or your PTX10002-60C device as a QFX10002-60C device. The image loaded on the device determines the personality of the device. For example, if you have purchased a QFX10002-60C device, the installed personality is a QFX10002-60C device. When you upgrade the QFX10002-60C device to a PTX10002-60C device, the new personality of the device is a PTX10002-60 C device. Similarly, if you have purchased a PTX10002-60C device, the installed personality is a PTX10002-60C device and the new personality, if you upgrade, is a QFX10002-60C device.

In an USB upgrade, the content of the SSDs are erased and the image is installed from the USB to both the primary and secondary disks. Based on the image used, the device comes up as either a QFX10002-60C or a PTX10002-60C device. This is irrespective of the previously installed personality of the JNP10002-60C-CHAS chassis.

Note:

When you order the spare JNP10002-60C-CHAS, it is preloaded with the QFX10002-60C and PTX10002-60C software images in the /var/tmp location. If you want to convert a QFX10002-60C device to a PTX10002-60C device, use the PTX10002-60C image. If you want to convert a PTX10002-60C device to QFX10002-60C device, use the QFX10002-60C image.

For example, to upgrade the QFX10002-60C device from the installed personality of QFX10002-60C to the new personality of PTX10002-60C device using the USB Option:

  1. Insert the external USB flash drive. The external flash drive is detected.
  2. Reboot the device.
  3. Unplug the USB flash drive after the system reboots, when prompted.
Note:

Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.

Upgrading the Personality of QFX10002-60C and PTX10002-60C Devices Using the CLI Option

You can configure your QFX10002-60C device as a PTX10002-60C device or your PTX10002-60C device as a QFX10002-60C device. The image loaded on the device determines the personality of the device. For example, if you have purchased a QFX10002-60C device, the installed personality is a QFX10002-60C device. When you upgrade the QFX10002-60C device to a PTX10002-60C device, the new personality of the device is a PTX10002-60C device. Similarly, if you have purchased a PTX10002-60C device, the installed personality is PTX10002-60C and the new personality, if you upgrade, is a QFX10002-60C device.

Note:

When you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C default configuration is deleted, and the PTX10002-60C configuration becomes the default configuration. When you upgrade the PTX10002-60C personality to a QFX10002-60C personality, the PTX10002-60C default configuration is deleted, and the QFX10002-60C configuration becomes the default configuration. Additionally, the software snapshot in the secondary disk is deleted, and the new software snapshot is installed in the secondary disk. For example, if you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C snapshot is deleted, and the PTX10002-60C snapshot is installed in the secondary disk.

Note:

When you order the spare JNP10002-60C-CHAS, it is preloaded with the QFX10002-60C and PTX10002-60C software images in the /var/tmp location. If you want to convert a QFX10002-60C device to a PTX10002-60C device, use the PTX10002-60C image. If you want to convert a PTX10002-60C device to QFX10002-60C device, use the QFX10002-60C image.

  • Verify if the installed image supports the required command to upgrade to the new personality. If it does not, upgrade to a later version of the image before you upgrade to the new personality.

  • Delete any configuration that is not supported or not compatible with the new personality before you upgrade the personality. If any unsupported configuration is retained in the device after it reboots with the new image, the device returns to the factory-default configuration.

For example, to upgrade the QFX10002-60C device from the installed personality of QFX10002-60C to the new personality of PTX10002-60C device using the CLI Option:

  1. In operational mode, verify the installed personality of the device
  2. Download the software package from https://www.juniper.net/support/. For information about downloading software packages, see Downloading Software (Junos OS). Save the software package to the /var/path/package-name directory on the device. For example, you can save the software package to the /var/tmp directory.
    Note:

    Download the software package specific to the personality you want to upgrade to. The software package for QFX Series devices is different from the software package for the PTX Series devices.

  3. In operational mode, install the software package by using the request vmhost software add path/package-name command. For example, to install the junos-vmhost-install-ptx-x86-64-zyx.tgz package:
    Note:

    If you do not specify the no-validate option, the device displays the following error message error: Upgrading to a different model is supported only with no-validate option .

  4. Run the show version command to verify that the upgrade is successful.
Note:

Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.

To ensure that all 4 partitions are upgraded to the same personality, follow these steps:

  1. Boot from solid-state drive (SSD) Disk 2 using the request vmhost reboot command.

  2. Upgrade to the new personality using no-validate option. This command upgrades both partitions on SSD Disk 1.

    For example:

    If you are upgrading to the PTX10002-60C device, include the package for the PTX10002-60C device. If you are upgrading to the QFX10002-60C device, include the package for the QFX10002-60C device.

  3. After booting up from SSD1, take a snapshot from SSD1 to SSD2.

    This ensures that both partitions on SSD2 are upgraded to new personality.

Upgrading the Personality of QFX10002-60C and PTX10002-60C Devices Using Zero Touch Provisioning (ZTP)

You can configure your QFX10002-60C device as a PTX10002-60C device or your PTX10002-60C device as a QFX10002-60C device. The image loaded on the device determines the personality of the device. For example, if you have purchased a QFX10002-60C device, the installed personality is a QFX10002-60C device. When you upgrade the QFX10002-60C device to a PTX10002-60C device, the new personality of the device is a PTX10002-60C device. Similarly, if you have purchased a PTX10002-60C device, the installed personality is PTX10002-60C and the new personality, if you upgrade, is a QFX10002-60C device.

Note:

When you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C default configuration is deleted, and the PTX10002-60C configuration becomes the default configuration. When you upgrade the PTX10002-60C personality to a QFX10002-60C personality, the PTX10002-60C default configuration is deleted, and the QFX10002-60C configuration becomes the default configuration. If you have provided your own Junos OS configuration, that configuration becomes the default configuration. Additionally, the software snapshot in the secondary disk is deleted, and the new software snapshot is installed in the secondary disk. For example, if you upgrade the QFX10002-60C personality to a PTX10002-60C personality, the QFX10002-60C snapshot is deleted, and the PTX10002-60C snapshot is installed in the secondary disk.

Note:

When you order the spare JNP10002-60C-CHAS, it is preloaded with the QFX10002-60C and PTX10002-60C software images in the /var/tmp location. If you want to convert a QFX10002-60C device to a PTX10002-60C device, use the PTX10002-60C image. If you want to convert a PTX10002-60C device to QFX10002-60C device, use the QFX10002-60C image.

  • Verify if the installed image supports the required command to upgrade to the new personality. If it does not, upgrade to a later version of the image before you upgrade to the new personality.

  • Delete any configuration that is not supported or not compatible with the new personality before you upgrade the personality. If any unsupported configuration is retained in the device after it reboots with the new image, the device returns to the factory-default configuration.

Before you begin:

  • Ensure that the switch or router has access to the following network resources:

    • The DHCP server that provides the location of the software image and configuration files on the network

      Refer to your DHCP server documentation for configuration instructions.

    • The File Transfer Protocol (anonymous FTP), Hypertext Transfer Protocol (HTTP), or Trivial File Transfer Protocol (TFTP) server on which the software image and configuration files are stored

      Note:

      Although TFTP is supported, we recommend that you use FTP or HTTP instead, because these transport protocols are more reliable.

      CAUTION:

      HTTP URLs are limited to 256 characters in length.

    • A Domain Name System (DNS) server to perform reverse DNS lookup

    • (Optional) An NTP server to perform time synchronization on the network

    • (Optional) A system log (syslog) server to manage system log messages and alerts

  • Locate and record the MAC address printed on the switch or router chassis.

CAUTION:

You cannot commit a configuration while the switch or router is performing the software update process. If you commit a configuration while the switch or router is performing the configuration file autoinstallation process, the process stops, and the configuration file is not downloaded from the network.

For example, to upgrade the QFX10002-60C device from the installed personality of QFX10002-60C to the new personality of PTX10002-60C device using ZTP:

  1. In operational mode, verify the installed personality of the device
  2. Boot the device.
  3. Make sure the device has the default factory configuration installed.

    Issue the request vmhost zeroize command on the device that you want to provision.

  4. Download the software package specific to the personality you want to upgrade from https://www.juniper.net/support/.

    The software package for QFX Series devices is different from the software package for the PTX Series devices.

  5. Save the software package and the configuration file to the FTP, HTTP, or TFTP server from which the device will download these files.
  6. Configure the DHCP server to provide the necessary information to the switch or router.

    Configure IP address assignment.

    You can configure dynamic or static IP address assignment for the management address of the switch or router. To determine the management MAC address for static IP address mapping, add 1 to the last byte of the MAC address of the switch or router, which you noted before you began this procedure.

  7. Define the format of the vendor-specific information for DHCP option 43 in the dhcpd.conf file.

    Here is an example of an ISC DHCP 4.2 server dhcpd.conf file:

    Note:

    Starting in Junos OS Release 18.2R1, a new DHCP option is introduced to set the timeout value for the file downloads over FTP. If the transfer-mode is set as FTP, the default value for the timeout is automatically set as 120 minutes, that is, in case the FTP session gets interrupted due to loss of connectivity in the middle of a file transfer, it will timeout after 120 minutes and ZTP will attempt to retry the file fetching process. This value can be overridden using the DHCP option as follows:

    where “val” is the user configurable timeout value in seconds and must be provided within quotes (like, "val”).

  8. Configure the following DHCP option 43 suboptions:
    Note:

    DHCP option 43 suboptions 05 through 255 are reserved.

    • Suboption 00: The name of the software image file to install.

      Note:

      When the DHCP server cannot use suboption 00, configure the software image filename using suboption 04. If both suboption 00 and suboption 4 are defined, suboption 04 is ignored.

    • Suboption 01: The name of the script or configuration file to install.

      The following list provides the types of scripts and their associated interpreter paths:

      • Shell script interpreter path: #!/bin/sh

      • SLAX script interpreter path: #!/usr/libexec/ui/cscript

      • Python script interpreter path: #!/usr/bin/python

        Unsigned Python scripts are only supported on limited platforms, such as the QFX5100 device. If you try to execute unsigned Python scripts on devices that do not provide support, error messages will be issued.

      Note:

      If the file does not contain special characters (#!) , ZTP determines that the file is a configuration file and loads the configuration file.

    • Suboption 02: The symbolic link to the software image file to install.

      Note:

      If you do not specify suboption 2, the ZTP process handles the software image as a filename, not a symbolic link.

    • Suboption 03: The transfer mode that the switch or router uses to access the TFTP, FTP, or HTTP server. If you select FTP as the transfer mode, Junos OS uses the anonymous FTP login to download files from the FTP server.

      Note:

      If suboption 03 is not configured, TFTP becomes the transfer mode by default.

    • Suboption 04: The name of the software image file to install.

      Note:

      When the DHCP server cannot use suboption 00, configure the image file using suboption 04. If both suboption 00 and suboption 4 are defined, suboption 04 is ignored.

    • Suboption 05: The name of the JLoader image file to install.

  9. (Mandatory) Configure either option 150 or option 66.
    Note:

    You must configure either option 150 or option 66. If you configure both option 150 and option 66, option 150 takes precedence, and option 66 is ignored. Also, make sure you specify an IP address, not a hostname, because name resolution is not supported.

    • Configure DHCP option 150 to specify the IP address of the FTP, HTTP, or TFTP server.

    • Configure DHCP option 66 to specify the IP address of the FTP, HTTP, or TFTP server.

  10. (Optional) Configure DHCP option 7 to specify one or more system log (syslog) servers.
  11. (Optional) Configure DHCP option 42 to specify one or more NTP servers.
  12. (Optional) Configure DHCP option 12 to specify the hostname of the switch or router.

    The following sample configuration shows the DHCP options you just configured:

    Based on the DHCP options you just configured, the following statements are appended to the Junos OS configuration file (for example, jn-switch35.config):

  13. Monitor the ZTP process by looking at the following log files.
    Note:

    When SLAX (live operating system based on Linux) scripts are issued, the op-script.log and event-script.log files are produced.

    • /var/log/dhcp_logfile

    • /var/log/event-script.log

    • /var/log/image_load_log

    • /var/log/messages

    • /var/log/op-script.log

    • /var/log/script_output

    You can also monitor the ZTP process by looking at error messages and issuing operational commands. See Monitoring Zero Touch Provisioning for more information.

  14. Run the show version command to verify that the upgrade is successful.