Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Software Installation and Upgrade

  • Support for bootstrapping using HTTP proxy server in phone-home client (EX2300, EX2300-VC, EX3400, EX3400-VC, EX4400-24T, EX4400-48F, EX4400-48T, and EX4600)—Starting in Junos OS Release 21.1R1, when the phone-home client (PHC) receives information regarding the HTTP proxy server through either DHCP option 43 suboption 8 or DHCP option 17 suboption 8, it creates an HTTPS transparent tunnel with the proxy server. After the tunnel is established, the PHC uses the tunnel as a proxy for the phone-home server or redirect server. The phone-home client downloads the software image and configuration file through the tunnel onto the device. When bootstrapping is complete, the device reboots and the tunnel quits.

    [See Obtaining Configurations and Software Image Without User Intervention Using Phone-Home Client.]

  • Support for DHCP option 43 suboption 8 to provide proxy server information in phone-home client (EX2300, EX2300-VC, EX3400, EX3400-VC, EX4400-24T, EX4400-48F, EX4400-48T, and EX4600)—Starting in Junos OS Release 21.1R1, during the bootstrapping process, the phone-home client (PHC) can access the redirect server or the phone-home server through a proxy server. The DHCP server uses DHCP option 43 suboption 8 or DHCP option 17 suboption 8 to deliver the details of both IPv4 and IPv6 proxy servers to the PHC. The DHCP daemon running on the target switch learns about the proxy servers in the initial DHCP cycle and then populates either the phc_vendor_specific_info.xml files or the phc_v6_vendor-specific_info.xml files located in the /var/etc/ directory with the vendor-specific information.

    [See Obtaining Configurations and Software Image Without User Intervention Using Phone-Home Client.]

  • Phone-home client (vSRX)—Starting in Junos OS Release 21.1R1, the phone-home client (PHC) is responsible for the initial bootup and configuration of the vSRX VM instance when the virtual machine (VM) instance is turned on. When the vSRX VM instance boots up with the factory-default configuration, the phone-home client connects to a redirect server, which then redirects to the phone-home serverr. The phone-home client downloads the initial configuration and the latest Junos OS image from the phone-home server. .The new image is installed first, and then the initial configuration is applied and committed on the vSRX VM instance.

    If the redirect server does not provide any phone-home server information, the phone-home client restarts the provisioning process and keeps connecting to the redirect server until provisioning is successful.

    [See Obtaining Configurations and Software Image Without User Intervention Using Phone-Home Client.]

  • Zero-touch provisioning (ZTP) with IPv6 support (QFX5120-32C)—Starting in Junos OS Release 21.1R1, you can use a DHCPv6 client and ZTP to provision a QFX5120-32C switch.. During the bootstrap process, the device first uses the DHCPv4 client to request for information regarding the image and configuration file from the DHCP server. The device checks the DHCPv4 bindings sequentially. If there is a failure with one of the DHCPv4 bindings, the device continues to check for bindings until provisioning is successful. However, if there are no DHCPv4 bindings, the device checks for DHCPv6 bindings and follows the same process as for DHCPv4 until the device is provisioned successfully. Both DHCPv4 and DHCPv6 clients are included as part of the default configuration on the device.

    The DHCP server uses DHCPv6 options 59 and 17 and applicable suboptions to exchange ZTP-related information between itself and the DHCP client.

    [See Zero Touch Provisioning.]

  • Support for signed third-party application installation (MX10003, MX10008, QFX5210, QFX10002, and QFX10008 routers with VM host architecture)—Starting in Junos OS Release 21.1R1, you can install signed third-party application installation and carry over the application between upgrades.

    The backup of third-party package occurs during upgrade. Hence, the package is restored even if the installed package is deleted or uninstalled before a reboot. However, as the third party package restoration depends on the contents saved on the disk during upgrade and the configuration to allow the package to be installed, restoration is not possible when

    • Configuration is removed after upgrade
    • Content is removed due to deletion by configuring request vmost zeroize command

    On platforms where jinstall-host.tgz images are installed, the minimum space required for the backup is 250MB. After backup, if the free space available is less than 200MB, the backup would be deleted to make space for upgrade. On platforms where junos-vmhost images are installed, the minimum space required for backup of third party unbundled packages is 1200MB. After the backup, if the free space is less than 512MB, the backup would be deleted to free up space for upgrade.

    [See Installing, Upgrading, Backing Up, and Recovery of VM Host.]

  • Support for phone-home client (EX4400 Virtual Chassis)—Starting in Junos OS Release 21.1R1, the phone-home client (PHC) can securely provision an EX4400 Virtual Chassis without requiring user interaction. You only need to:

    • Ensure that the Virtual Chassis members have the factory-default configuration.

    • Interconnect the member switches using dedicated or default-configured Virtual Chassis ports.

    • Connect the Virtual Chassis management port or any network port to the network.

    • Power on the Virtual Chassis members.

    The PHC automatically starts up on the Virtual Chassis and connects to the phone-home server (PHS). The PHS responds with bootstrapping information, including the Virtual Chassis topology, software image, and configuration. The PHC upgrades each Virtual Chassis member with the new image and applies the configuration, and the Virtual Chassis is ready to go.

    [See Provision a Virtual Chassis Using the Phone-Home Client.]

  • request system software status command (MX480, MX960, MX2010, MX2020, SRX1500, SRX4100, SRX4400, SRX4600, SRX5400, SRX5600, SRX5800, vMX, and vSRX)—Starting in Junos OS Release 21.1R1, you can use the CLI command request system software status to view the status of the software package installation or uninstallation on the local Routing Engine.