Upgrading the Personality of a Device by Using a PXE Boot Server
The image loaded on the device defines the personality of the device. For instance, if you have purchased a device for use as a core router, you can upgrade the personality of the device for use as an edge router or as a switch. For instance, if you have purchased a PTX10008 device, the installed personality of the device is PTX10008. When you upgrade the personality of the device to an MX10008, the new personality of the device is MX10008. Similarly, if you have purchased a MX10008 device, the installed personality of the device is MX10008 and the new personality of the device, if you upgrade the personality, is PTX10008.
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 the 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
To upgrade the personality of a device from the installed personality to the new personality using the PXE boot server:
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:
- Copy the downloaded installation media to the
/var/tmpdirectory in the PXE boot server.
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
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
user@host> tar xvzf junos-vmhost-install-net-x86-64-xyz.tgz –C /var/tmp
attributes 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
user@host> rm -f /tftpboot
- Extract the network installation package.
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/scripts
/var/installdirectory. Create a new
user@host>mv /var/install /var/install_old
- Extract the installation package.
For example, this sample output is specific to the ptx 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 the
attributesfile. If the file does not exist in the specified location, copy the attribute file.
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
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.
After you copy the image to the PXE Boot Server, to install the image on the router, reboot the router to install the image. You can use the request vmhost reboot network command to install the image. The router 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. For more information, see Upgrading the Personality of a Device by Using a USB Flash Drive. If the router fails to reboot or is not accessible, follow these steps:
- 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 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
WARNING: The installation will erase the contents of your disks.
Install vmhost and Junos Software on Primary and Secondary disk [y/n]
- In operational mode, 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 mx10008. If you have
upgraded the personality of the device to a PTX10008 device, the new
personality of the device is ptx10008.
user@host> show version
Hostname: host Model: ptx10008
user@host> show version
Hostname: host Model: mx10008
Juniper Networks does not support using the request vmhost software rollback command to revert to the previously installed personality.