Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Software Installation and Upgrade

  • Increased memory allocation for Junos VM (MX204)—Starting in Junos OS Release 21.2R1, we support increased memory allocation for Junos VM. The available VM size options are default (16GB) and high (24GB). After you update the VM size, you must perform a system reboot using the request vmhost reboot statement.

    Before you increase the memory, please contact Juniper Networks technical support to know the use cases that we support. After the memory upgrade, if you want to downgrade the Junos OS image, revert the VM memory to default and perform a system reboot using the request vmhost reboot command.

    [See VM Host Overview.]

  • Support for DHCP option 43 suboption 8 to provide proxy server information in PHC (EX2300-C, EX2300-MP, EX4300, EX4300-MP, EX4300-VC, EX4600-VC, EX4650, and EX4650-48Y-VC)—Starting in Junos OS Release 21.2R1, 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. The daemon then populates either the phc_vendor_specific_info.xml files or thephc_v6_vendor-specific_info.xml files located at /var/etc/ with vendor-specific information.

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

  • ZTP with IPv6 support (EX2300-C, EX2300-MP, EX4300, EX4300-MP, EX4300-VC, EX4600-VC, EX4650, and EX4650-48Y-VC)—Starting in Junos OS Release 21.2R1, you can use a DHCPv6 client and zero-touch provisioning (ZTP) to provision a device. 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 one of the DHCPv4 bindings fails, 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.]

  • Dynamic port speed detection for ZTP (QFX10002)—Starting in Junos OS Release 21.2R1, you can use either WAN interfaces or management interfaces to automatically download and install the appropriate software and the configuration file on your device during the bootstrap process. Zero-touch provisioning (ZTP) automatically configures WAN interfaces based on the optics type, and then connects your device to the DHCP server to perform the bootstrap process.

    [See Zero Touch Provisioning.]

  • Support of the PXE boot method (SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800)—Starting in Junos OS Release 21.2R1, we support the Preboot Execution Environment (PXE) boot method. With a PXE boot server, you can prepare an environment to boot devices by using a network interface that is independent of available data storage devices or installed operating systems. A client-enabled system uses a PXE boot to load an OS from a remote server and boot from it. PXE boot uses the standard protocols UDP/IP, Trivial File Transfer Protocol (TFTP), and BOOTP to transfer the image.

    [See Upgrading the Personality of a Device by Using a PXE Boot Server.]