ON THIS PAGE
Upgrading the Personality of a Device by Using a USB Flash Drive
Upgrading the Personality of a Device by Using a PXE Boot Server
Upgrading the Personality of SRX1500 Device by Using a PXE Boot Server
Upgrading the Personality of SRX4100 Device by Using a PXE Boot Server
Upgrading the Personality of SRX4600 Device by Using a PXE Boot Server
Personality Upgrade Process
Understanding the Personality Upgrade Process for a Device
Personality of a device can be defined as a combination of the purpose of the device and the solution that the device provides. For instance, a switch is a Layer 2 (Data Link Layer) device that is designed to connect two or more networking devices on a network. Most switches (except a few Layer 3 switches) act as bridge devices that receive data packets from a source device, process the data, and forward it to a destination device within the same network. A router, in contrast, connects multiple networks. It is typically a Layer 3 (Network Layer) device because its primary function is to forward packets destined either for its own network or for other networks.
Starting in Junos OS Release 18.2R1, you can upgrade the personality of a device from the installed personality to a new personality without having to upgrade the entire device.
The build image loaded on a device defines the personality of the device. For instance, suppose you purchase a core router such as a PTX10008. The build image loaded on the router indicates its installed personality—that is, PTX10008. You can upgrade its personality and use it as an edge router such as an MX10008, in which case the device personality changes to MX10008. Similarly, you can change the device personality from an MX10008 to a PTX10008. You can also alternate between a switch (for example, QFX10002-60C) and a router (say, PTX10002-60C) by simply upgrading the device personality.
To upgrade the device personality from one device to another, you need certain common hardware components supported by both the devices. In the case of an MX10008 and a PTX10008, the presence of the common Routing and Control Board (RCB)—JNP10K-RE1—and the eight-slot universal chassis—JNP10008—enables you to upgrade from one device to the other seamlessly.
When you order a spare JNP10K-RE1 RCB, the image of the
MX10008 build is installed on that RCB. The spare JNP10K-RE1 also
contains an image of the PTX10008 build at the /var/tmp location. You can upgrade an MX10008 router to an PTX10008 by using
that image.
You can upgrade the personality of the device to a new personality by:
Using the USB flash drive
Using the Junos OS CLI
Using the PXE boot server
Benefits of Personality Upgrade
Reuse—The same device (universal chassis) can be used as an edge router or a core router or a switch.
Time-saving—You can quickly deploy the new device personality in the network.
Lower capital expenditure and operating costs—You can upgrade the device personality instead of purchasing a new device.
Network Growth management—Upgrading the personality of your device helps you manage the network growth when growth forecasts are discouraging.
Lower inventory and storage costs for distributors.
Guidelines and Restrictions
This section describes the guidelines to consider when you upgrade the personality of a device:
If you attempt to upgrade the personality of the device without using the recommended CLI command, the device can become inaccessible and unstable. For more information, see Upgrading the Personality of a Device by Using CLI.
There are no in-built restrictions or checks to validate the image that you plan to install on the device.
Verify that 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.
When you upgrade the personality of the device, the configuration present in the device is migrated to the new personality. This is similar to a Junos OS upgrade. Therefore, any configuration that is not supported on the new personality must be deleted 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.
Retain the minimum configuration required on the device, so the management interface is accessible.
Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.
Supported Personality Upgrades
Table 1 displays the various combinations of device personality upgrades that are supported by Junos OS.
Table 1: Supported Personality Upgrades on Junos OS
Installed Personality | New Personality | Initial Junos OS Release | Common HW Component |
|---|---|---|---|
MX10008 | PTX10008 | 18.2 | Routing and Control Board (JNP10K-RE1) |
PTX10008 | MX10008 | 18.2 | Routing and Control Board (JNP10K-RE1) |
QFX10002-60C | PTX10002-60C | 18.2 | |
PTX10002-60C | QFX10002-60C | 18.2 | |
MX10016 | PTX10016 | 18.4 | Routing and Control Board (JNP10K-RE1) |
PTX10016 | MX10016 | 18.4 | Routing and Control Board (JNP10K-RE1) |
There are multiple ways to change the personality of a device:
Upgrading the Personality of a Device by Using a USB Flash Drive
Upgrading the Personality of a Device by Using a PXE Boot Server
Upgrading the Personality of a Device by Using a USB Flash Drive
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
In a USB upgrade, the content of the SSDs are erased and the image is installed from the USB flash drive to both the primary and secondary disks. Based on the image used, the device comes up as a PTX10008 or an MX10008. This is irrespective of the previously installed personality of the device.
When you order a spare JNP10K-RE1 RCB, the image of the
MX10008 build is installed on that RCB. The spare RCB also contains
an image of the PTX10008 build at the /var/tmp location. You can upgrade an MX10008 router to an PTX10008 by using
that image.
To upgrade the personality of the device by using a USB flash drive:
- Insert the external USB flash drive. The external flash drive is detected.
- Reboot the device.user@host# run request vmhost reboot usbORuser@host# run request vmhost reboot
- When prompted, unplug the USB flash drive after the system reboots.
Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.
Upgrading the Personality of a Device by Using CLI
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
You can upgrade the personality of the device by using CLI configuration on devices running Junos OS.
When you order a spare JNP10K-RE1 RCB, the image of the
MX10008 build is installed on that RCB. The spare RCB also contains
an image of the PTX10008 build at the /var/tmp location. You can upgrade an MX10008 router to an PTX10008 by using
that image.
How to Upgrade the Personality of a Device on Junos OS
Use the following CLI procedure to upgrade the personality of a device running Junos OS.
Verify that the installed image supports the required CLI 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 is 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.
To upgrade the device to a new personality by using the Junos OS CLI:
- In operational mode, verify the installed personality
of the device. If you have purchased an MX10008 device, the installed
personality of the device is displayed as mx10008. If you
have purchased a PTX10008 device, the installed personality of the
device is displayed as ptx10008.user@host> show version
Hostname: host Model: mx10008
Hostname: host Model: ptx10008
- Download the software package or build image from https://www.juniper.net/support/. For information about downloading
software packages, see Downloading Software. Save the software
package to the /var/path/package-name directory on the router. 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 PTX Series routers is different from the software package for MX Series routers.
- In configuration mode, install the software package by
using the request vmhost software add path/package-name command. Install the software
package based on the new personality you want to upgrade to, as follows:user@host# run request vmhost software add /var/tmp/junos-vmhost-install-ptx-x86-64-xyz.tgz upgrade-to-model ptx10008 no-validateuser@host# run request vmhost software add /var/tmp/junos-vmhost-install-mx-x86-64-zyx.tgz upgrade-to-model mx10008 no-validate
Note If you do not specify the no-validate option, the router displays the following error message: error: Upgrading to a different model is supported only with no-validate option.
- Reboot the router so the new package is loaded.user@host# run request vmhost reboot
- Run the show version command to verify that
the upgrade is successful. If you have upgraded the personality of
the device to an MX10008 device, the new personality of the device
is displayed as mx10008. If you have upgraded the personality
of the device to a PTX10008 device, the new personality of the device
is displayed as ptx10008.user@host> show version
Hostname: host Model: ptx10008
Hostname: host Model: mx10008
Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.
To ensure that all four partitions are upgraded to the same personality, follow these steps:
- Boot from the solid-state drive (SSD) Disk 2 by using
the request vmhost reboot command.user@host>request vmhost reboot disk2
- Upgrade to the new personality by using the upgrade-to-model and no-validate options. This command upgrades both partitions
on the SSD Disk 1.user@host# run request vmhost software add junos-vmhost-install-x.tgz upgrade-to-model X no-validate reboot
If you are upgrading to PTX10008, include the package for the PTX Series routers and replace X with ptx10008 before the no-validate option. If you are upgrading to MX10008, include the package for the MX Series routers and replace X with mx10008 before the no-validate option.
- After the device boots up from SSD Disk 1, take a snapshot
from SSD Disk 1 to Disk 2.user@host> request vmhost snapshot partition
This step ensures that both partitions on Disk 2 are upgraded to the new personality.
After you complete Step 1 through Step 3, all four partitions are upgraded to new personality.
Upgrading the Personality of a Device by Using a PXE Boot Server
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
You can upgrade the personality of a device by using the Preboot Execution Environment (PXE) boot server. 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 a separate PXE boot server for each image.
When you order a spare JNP10K-RE1 RCB, the image of the
MX10008 build is installed on that RCB. The spare RCB also contains
an image of the PTX10008 build at the /var/tmp location. You can upgrade an MX10008 router to an PTX10008 by using
that image.
To upgrade the personality of a device from the installed personality to the new personality by using the PXE boot server method:
Copy the image you want installed on the device to the PXE boot server.
Reboot the device to install the image.
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 and install the image:
- Copy the downloaded installation media to the
/var/tmpdirectory in the PXE boot server.For example:
scp /volume/build/junos/18.2/release/zyx/ship/junos-vmhost-install-net-x86-64-xyz.tgz user@host:/var/tmp/ - Log in to the PXE boot server and verify the installation
file.
For example:
user@host> ls -lh junos-vmhost-install-net-x86-64-xyz.tgz-rw-r--r-- 1 root root 1.8G May 24 00:42 junos-vmhost-install-net-x86-64-xyz.tgz
- Extract the
junos-vmhost-install-netTAR file.For example:
user@host> tar xvzf junos-vmhost-install-net-x86-64-xyz.tgz –C /var/tmpattributes junos-vmhost-install-ptx.tgz manifest manifest.certs manifest.ecerts manifest.esig manifest.sig package.xml pkg_add_vmhost.sh vmhost-install-net-x86_64-xyz.tgz
- Remove the previously installed files, if any, from the
/tftpbootdirectory.user@host> rm -f /tftpbootuser@host> mkdir /tftpboot - Extract the network installation package.
For example:
user@host> tar xvzf /var/tmp/vmhost-install-net-x86_64-xyz.tgz -C /tftpboot/./ ./vmhost-version.sh ./bootpxe64.efi ./vmhost-version ./grub.cfg .. ... -rw-rw-r-- 1 930 930 45M Oct 20 01:51 vmhost-install-net-x86_64-xyz.tgz -rw-rw-r-- 1 930 930 6 Oct 20 01:51 vmhost-version -rwxrwxr-x 1 930 930 416 Oct 20 01:51 vmhost-version.sh -rw-r--r-- 1 930 930 6.9M Oct 20 01:51 vmlinuz
- Rename or delete the previously installed root file
system/scriptsfrom the/var/installdirectory. Create a new/var/installdirectory.user@host>mv /var/install /var/install_olduser@host>mkdir /var/install - Extract the installation package.
For example, this sample output is specific to the PTX Series device installation package.
user@host>tar xvzf /var/tmp/junos-vmhost-install-ptx.tgz -C /var/install./ ./vmhost-pkgs-version ./vm/ ./vm/note ./vm/grub.cfg.ngre ./vm/vsmartd-1.0-0.x86_64.rpm ./vm/re_fpga-1.0-0.x86_64.rpm ./vm/veccd-1.0-0.x86_64.rpm ./vmhost-version.sh ./vmhost/ ./vmhost/vmhost-x86_64-xyz.img.gz ... ... ./junos/junos-mtre-upgrade.sh ./vmhost-core-x86_64-15.1I20151019_1021_builder.tgz ./junos/ ./junos/junos-install-x86-64-xyz.img.gz
- Verify that the
/var/installfolder contains theattributesfile. 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.
user@host> mv /var/tmp/attributes /var/install
- Set permissions for the files in the
/var/installand/tftpbootdirectories.user@host> chown root:root /tftpboot/* user@host>chmod a+rwx /tftpboot/* user@host>chown -R root:root /var/install user@host>chmod -R a+rwx /var/install
- Exit the PXE boot server.
user@host> exit
- After you copy the image to the PXE boot server, to install
the image on the device, reboot the device to install the image.
user@host> request vmhost reboot network
The router boots from the PXE server and installs the image on both the SSDs.
If the device fails to reboot, you can use the USB disk installation option. For more information, see Upgrading the Personality of a Device by Using a USB Flash Drive. However, after using USB disk installation, if the router fails to reboot or is not accessible, follow these steps on the console:
- Power cycle the chassis or remove the RCB (JNP10K-RE1) and plug it back in.
- Press the ESC button to go to the Boot Manager Menu.
- Select Boot Manager, and then press Enter.
- Select the 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.
WARNING: The installation will erase the contents of your disks.
Install vmhost and Junos Software on Primary and Secondary disk [y/n]
y
- In operational mode, verify that the upgrade is successful.
If you have upgraded the personality of the device to an MX10008,
the new personality of the device is mx10008. If you have
upgraded the personality of the device to a PTX10008, the new personality
of the device is ptx10008.
user@host> show versionHostname: host Model: ptx10008
user@host> show versionHostname: host Model: mx10008
Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.
Upgrading the Personality of SRX1500 Device by Using a PXE Boot Server
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
You can upgrade the personality of a device by using the Preboot Execution Environment (PXE) boot server. 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 a separate PXE boot server for each image.
To upgrade the personality of a device from the installed personality to the new personality by using the PXE boot server method:
Copy the image you want installed on the device to the PXE boot server.
Reboot the device to install the image. 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 and install the image:
- Remove the previously installed files, if any, from the
/var/lib/tftpboot/directory.user@host> rm -f /tftpbootuser@host> mkdir /tftpboot - Copy the downloaded installation media to the
/var/lib/tftpboot/directory in the PXE boot server.For example:
scp /volume/build/junos/20.1/release/zyx/ship/
junos-install-media-pxe-srxentedge-x86-64-20.3I-20200517_dev_common.0.1613.tgz user@host:/var/lib/tftpboot/ - Log in to the PXE boot server and verify the installation
file.
For example:
user@host> ls -lh junos-install-media-pxe-srxentedge-x86-64-20.3I-20200517_dev_common.0.1613.tgz-rw-r--r-- 1 root root 1.8G June 08 00:42 junos-install-media-pxe-srxentedge-x86-64-20.3I-20200517_dev_common.0.1613.tgz
- Extract the
junos-install-media-pxe-srxentedgeTAR file.For example:
user@host> tar xvzf junos-install-media-pxe-srxentedge-x86-64-20.3I-20200517_dev_common.0.1613.tgz –C /var/lib./initramfs.cpio.gz ./initrd.cpio.gz ./upgrade_platform ./initramfs.cpio.gz.psig ./vmlinuz.psig ./HOST_COMPAT_VERSION ./application-pkg.tgz ./EFI/ ./EFI/BOOT/ ./EFI/BOOT/BOOTX64.EFI ./EFI/BOOT/grub-root.pub ./EFI/BOOT/grub-trusted.gpg.psig ./EFI/BOOT/grub-trusted.gpg ./linux.checksum ./version.txt ./host-version ./vmlinuz
- Copy the BOOTX64.EFI file to the tftp home folder /var/lib/tftpboot/
user@host> cp EFI/BOOT/BOOTX64.EFI /var/lib/tftpboot/ - Create a secure boot folder at /var/lib/tftpboot/
user@host> rm -rf /var/lib/tftpboot/secure-bootuser@host> mkdir /var/lib/tftpboot/secure-boot - Copy the grub files in the secure boot folder.
user@host> cp EFI/BOOT/grub-root.pub secure-boot/user@host> cp EFI/BOOT/grub-trusted.gpg secure-boot/user@host> cp EFI/BOOT/grub-trusted.gpg.psig secure-boot/ - Move initrd.cpio.gz and application-pkg.tgz in ftp server
folder (/var/ftp/)
user@host> mv application-pkg.tgz /var/ftp/user@host> mv initrd.cpio.gz /var/ftp/ - Create grub-startup.cfg in /var/lib/tftpboot/secure-boot
folder.
user@host> cat grub-startup.cfginsmod search insmod linux insmod tftp insmod reboot insmod efi_gop insmod efi_uga insmod read insmod chain insmod boot insmod font insmod serial set timeout=5 menuentry 'PXE image' { set net_default_server=192.168.120.1 echo 'Loading ...' linux (tftp)/vmlinuz root=/dev/ram quiet console=ttyS0,9600n8 acpi=ht libata.force=noncq acpi_enforce_resources=lax install rootfs=ftp://192.168.120.1/initrd.cpio.gz app_pkg=ftp://192.168.120.1/application-pkg.tgz efi=debug intel_iommu=on isolcpus=2,3 echo 'Loading initial ramdisk ...' initrd (tftp)/initramfs.cpio.gz } - After you copy the image to the PXE boot server, to install
the image on the device, reboot the device to install the image.
user@host> request system reboot
The router boots from the PXE server and installs the image on both the SSDs.
If the device fails to reboot, you can use the USB disk installation option. For more information, see Upgrading the Personality of a Device by Using a USB Flash Drive. However, after using USB disk installation, if the router fails to reboot or is not accessible, follow these steps on the console:
- Reboot or power on the device
- Press the ESC button to go to the Boot Manager Menu.
- Select Setup Utility, and then press Enter.
- Select the boot type as UEFI Boot Type, PXE boot capability as UEFI:IPv4, first boot device asPXE on ME and set network stack as Enabled.
- Click F10
- In operational mode, verify that the upgrade is successful.
If you have upgraded the personality of the device to an SRX1500,
the new personality of the device is srx1500.
user@host> show versionHostname: host Model: srx1500
Juniper Networks does not support using the request system software rollback command to revert to the previously installed personality.
Upgrading the Personality of SRX4100 Device by Using a PXE Boot Server
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
You can upgrade the personality of a device by using the Preboot Execution Environment (PXE) boot server. 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 a separate PXE boot server for each image.
To upgrade the personality of a device from the installed personality to the new personality by using the PXE boot server method:
Copy the image you want installed on the device to the PXE boot server.
Reboot the device to install the image. 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 and install the image:
- Remove the previously installed files, if any, from the
var/lib/tftpboot/directory.user@host> rm -f /tftpbootuser@host> mkdir /tftpboot - Copy the downloaded installation media to the
/var/lib/tftpboot/directory in the PXE boot server.For example:
scp /volume/build/junos/20.1/release/zyx/ship/
junos-install-media-pxe-srxmr-x86-64-20.3I-20200520_dev_common.0.1928.tgz user@host:/var/lib/tftpboot/ - Log in to the PXE boot server and verify the installation
file.
For example:
user@host> ls -lh junos-install-media-pxe-srxmr-x86-64-20.3I-20200520_dev_common.0.1928.tgz-rw-r--r-- 1 root root 1.8G June 08 00:42 junos-install-media-pxe-srxmr-x86-64-20.3I-20200520_dev_common.0.1928.tgz
- Extract the
junos-install-media-pxe-srxmrTAR file.For example:
user@host> tar xvzf junos-install-media-pxe-srxmr-x86-64-20.3I-20200520_dev_common.0.1928.tgz –C /var/lib./initramfs.cpio.gz ./initrd.cpio.gz ./upgrade_platform ./initramfs.cpio.gz.psig ./vmlinuz.psig ./HOST_COMPAT_VERSION ./application-pkg.tgz ./EFI/ ./EFI/BOOT/ ./EFI/BOOT/BOOTX64.EFI ./EFI/BOOT/grub-root.pub ./EFI/BOOT/grub-trusted.gpg.psig ./EFI/BOOT/grub-trusted.gpg ./linux.checksum ./version.txt ./host-version ./vmlinuz
- Move initrd.cpio.gz and application-pkg.tgz in ftp server
folder (/var/ftp/)
user@host> mv application-pkg.tgz /var/ftp/user@host> mv initrd.cpio.gz /var/ftp/ - Install syslinux on ftp server.
user@host> yum install syslinux - Copy syslinux files to ftp server.
user@host> cp /usr/share/syslinux/menu.c32 /usr/share/syslinux/vesamenu.c32 /usr/share/syslinux/pxelinux.0 /var/lib/tftpboot/ - Create PXE menu.
user@host> mkdir /var/lib/tftpboot/pxelinux.cfg - Create a new default file at PXE menu.
user@host> cat pxelinux.cfg/defaultdefault vesamenu.c32 prompt 0 timeout 800 #display boot.msg #menu background splash.jpg menu title Welcome! menu color border 0 #ffffffff #00000000 menu color sel 7 #ffffffff #ff000000 menu color title 0 #ffffffff #00000000 menu color tabmsg 0 #ffffffff #00000000 menu color unsel 0 #ffffffff #00000000 menu color hotsel 0 #ff000000 #ffffffff menu color hotkey 7 #ffffffff #ff000000 menu color scrollbar 0 #ffffffff #00000000 LABEL SRXMR---20.3 MENU LABEL ^B SRXMR---20.3 KERNEL vmlinuz INITRD initramfs.cpio.gz APPEND vm console=ttyS0,9600n8 root=/dev/ram intel_iommu=on acpi=off isolcpus=2,3 libata.force=noncq acpi_enforce_resources=lax install rootfs=ftp://192.168.120.1/initrd.cpio.gz install app_pkg=ftp://192.168.120.1/application-pkg.tgz - After you copy the image to the PXE boot server, to install
the image on the device, reboot the device to install the image.
user@host> request system reboot
The router boots from the PXE server and installs the image on both the SSDs.
If the device fails to reboot, you can use the USB disk installation option. For more information, see Upgrading the Personality of a Device by Using a USB Flash Drive. However, after using USB disk installation, if the router fails to reboot or is not accessible, follow these steps on the console:
- Reboot or power on the device
- Press the ESC button to go to the Boot Manager Menu.
- Select the boot mode as LEGACY, boot option 1 as Network, and set network stack as Disabled.
- Select save and exit or click F4 to start PXE boot.
- Select the menu from the screen and click Enter to reboot the device.
- Choose boot option 1 as Hard Disk.
- Select save and exit or click F4.
- In operational mode, verify that the upgrade is successful.
If you have upgraded the personality of the device to an SRX4100,
the new personality of the device is srx4100.
user@host> show versionHostname: host Model: srx4100
Juniper Networks does not support using the request system software rollback command to revert to the previously installed personality.
Upgrading the Personality of SRX4600 Device by Using a PXE Boot Server
The build image loaded on the device defines the personality of the device. You can change the personality of the device by upgrading it.
You can upgrade the personality of a device by using the Preboot Execution Environment (PXE) boot server. 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 a separate PXE boot server for each image.
To upgrade the personality of a device from the installed personality to the new personality by using the PXE boot server method:
Copy the image you want installed on the device to the PXE boot server.
Reboot the device to install the image. 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 and install the image:
- Remove the previously installed files, if any, from the
/var/lib/tftpboot/directory.user@host> rm -f /tftpbootuser@host> mkdir /tftpboot - Copy the downloaded installation media to the
/var/lib/tftpboot/directory in the PXE boot server.For example:
scp /volume/build/junos/20.1/release/zyx/ship/
junos-install-media-pxe-srxhe-x86-64-20.3I-20200521_dev_common.0.1013.tgz user@host:/var/lib/tftpboot/ - Log in to the PXE boot server and verify the installation
file.
For example:
user@host> ls -lh junos-install-media-pxe-srxhe-x86-64-20.3I-20200521_dev_common.0.1013.tgz-rw-r--r-- 1 root root 1.8G June 08 00:42 junos-install-media-pxe-srxhe-x86-64-20.3I-20200521_dev_common.0.1013.tgz
- Extract the
junos-install-media-pxe-srxheTAR file.For example:
user@host> tar xvzf junos-install-media-pxe-srxhe-x86-64-20.3I-20200521_dev_common.0.1013.tgz –C /var/lib./initramfs.cpio.gz ./initrd.cpio.gz ./upgrade_platform ./initramfs.cpio.gz.psig ./vmlinuz.psig ./HOST_COMPAT_VERSION ./application-pkg.tgz ./EFI/ ./EFI/BOOT/ ./EFI/BOOT/BOOTX64.EFI ./EFI/BOOT/grub-root.pub ./EFI/BOOT/grub-trusted.gpg.psig ./EFI/BOOT/grub-trusted.gpg ./linux.checksum ./version.txt ./host-version ./vmlinuz
- Copy the BOOTX64.EFI file to the tftp home folder /var/lib/tftpboot/
user@host> cp EFI/BOOT/BOOTX64.EFI /var/lib/tftpboot/ - Create a secure boot folder at /var/lib/tftpboot/
user@host> rm -rf /var/lib/tftpboot/secure-bootuser@host> mkdir /var/lib/tftpboot/secure-boot - Copy the grub files in the secure boot folder.
user@host> cp EFI/BOOT/grub-root.pub secure-boot/user@host> cp EFI/BOOT/grub-trusted.gpg secure-boot/user@host> cp EFI/BOOT/grub-trusted.gpg.psig secure-boot/ - Move initrd.cpio.gz and application-pkg.tgz in ftp server
folder (/var/ftp/)
user@host> mv application-pkg.tgz /var/ftp/user@host> mv initrd.cpio.gz /var/ftp/ - Create grub-startup.cfg in /var/lib/tftpboot/secure-boot
folder.
user@host> cat grub-startup.cfginsmod search insmod linux insmod tftp insmod reboot insmod efi_gop insmod efi_uga insmod read insmod chain insmod boot insmod font insmod serial set timeout=5 menuentry 'PXE image' { set net_default_server=192.168.120.1 echo 'Loading ...' linux (tftp)/vmlinuz root=/dev/ram quiet console=ttyS0,9600n8 acpi=ht libata.force=noncq acpi_enforce_resources=lax install rootfs=ftp://192.168.120.1/initrd.cpio.gz app_pkg=ftp://192.168.120.1/application-pkg.tgz efi=debug intel_iommu=on isolcpus=2,3 echo 'Loading initial ramdisk ...' initrd (tftp)/initramfs.cpio.gz } - After you copy the image to the PXE boot server, to install
the image on the device, reboot the device to install the image.
user@host> request system reboot
The router boots from the PXE server and installs the image on both the SSDs.
If the device fails to reboot, you can use the USB disk installation option. For more information, see Upgrading the Personality of a Device by Using a USB Flash Drive. However, after using USB disk installation, if the router fails to reboot or is not accessible, follow these steps on the console:
- Reboot or power on the device
- Press the ESC button to go to the Boot Manager Menu.
- Select Setup Utility, and then press Enter.
- Select the PXE boot capability as UEFI:IPv4, disable HDD and enable ETH00 under EPI.
- Click F10
- In operational mode, verify that the upgrade is successful.
If you have upgraded the personality of the device to an SRX4600,
the new personality of the device is srx4600.
user@host> show versionHostname: host Model: srx4600
Juniper Networks does not support using the request system software rollback command to revert to the previously installed personality.