- play_arrow Overview
- play_arrow Configuring High Availability
- play_arrow Monitoring and Troubleshooting JDM
- play_arrow Configuration Statements and Operational Commands
Installing Software on NFX250 Devices
Downloading and Installing Software
Downloading Software
You can download the software package you need in one of two ways:
Downloading Software by Using a Browser
You download the software package you need from the Juniper Networks Support website at https://www.juniper.net/support/.
To access the download section, you must have a service contract and an access account. If you need help obtaining an account, complete the registration form at the Juniper Networks website: https://userregistration.juniper.net/entitlement/setupAccountInfo.do.
To download the software image:
From your browser, go to https://www.juniper.net/support/.
The Online Support (CSC) page opens.
Click the Download Software link.
The Download Software page appears.
Select the software package that you want to download. You can select software that supports a specific platform or technology.
On the page that appears, click the Software tab and select the Junos OS installation package to download.
Log in with your username and password.
On the Download Software page that appears, the following options are available:
If you want to download the software on your local host, click the CLICK HERE link and save the file to your system. If you want to place the file on a remote system, you must make sure that the file can be accessible by the router, switch, or services gateway by using HTTP, FTP, or SCP. Proceed with the installation. See Installing Software by Using the Command-Line Interface for more details.
If you want to download the software on your device, use the following procedure to download and install the software on the device.
-
Click Copy to copy the generated URL generated to the clipboard.
Note:The URL string generated remains active only for 15 minutes.
Log in to your device.
In operational mode, enter the
file copy “URL” destinationcommand.In the command, paste the copied URL string (for URL) and then enter /var/tmp (as the destination on your hard disk).
Example:
content_copy zoom_out_mapuser@host> file copy "https://cdn.juniper.net/software/ittest/software_target/agileEcotTest/Dev_Binary_Build.tar? SM_USER=user1=1507622971_dce164fa854b4a27550c254eef950dd8” /var/tmpNote:Ensure that the URL string is enclosed within quotation marks. Also ensure that there is sufficient free space available on the device.
The software image is downloaded on your device.
Install the software by using the
request system software add package-namecommand.Example:
content_copy zoom_out_mapuser@host> request system software add /var/tmp/ junos-install-mx-x86-32-17.3R1.10.tgzYour software is installed on the device.
-
See Also
Installing Software by Using the Command-Line Interface
Download the software package you need from the Juniper Networks Support website at https://www.juniper.net/support/, and place the package on a local system. You can then transfer the downloaded package to the device using either the router or switch command-line interface, or the local system command-line interface.
To access the download section, you must have a service contract and an access account. If you need help obtaining an account, complete the registration form at the Juniper Networks website: https://userregistration.juniper.net/entitlement/setupAccountInfo.do.
Before you transfer the software package, ensure that the FTP
service is enabled on the device.Enable the FTP service
using the set system services ftp command:
user@host# set system services ftp
To transfer the software package using the device command-line interface:
To transfer the package by using the local system command-line interface:
From the local system command line, initiate an FTP session with the device using the
ftpcommand:content_copy zoom_out_mapuser@host> ftp host
host is the hostname or address of the router or switch.
Log in with your customer support–supplied username and password:
content_copy zoom_out_mapUser Name: username 331 Password required for username. Password: password
After your credentials are validated, the FTP session opens.
Navigate to the software package location on the local system, and transfer the package by using the
putcommand:content_copy zoom_out_mapuser@host> put installation-package
Following is an example of an installation-package name: junos-install-mx-x86-32-17.3R1.10.tgz
Close the FTP session by using the
byecommand:content_copy zoom_out_mapuser@host> bye Goodbye
See Also
Software Installation on NFX250 Network Services Platform
This topic lists the commands to be used for installing a software package and upgrading an image on NFX250 Network Services Platform and rebooting the NFX250 platform. It also lists the commands to be used for formatting and reverting the system to factory state.
To install a new package on the NFX250 Network Services Platform:
[edit] user@jdm> request system software add package [reboot]
Reboot is an option to reboot the device after installing the new software package.
Replace package with the following
path:
For a software package in a local directory on the platform—/var/tmp/package.tgz
To reboot the platform:
[edit] user@jdm> request system reboot
To format the system by deleting all user data, configuration details, and reinstall current software on the NFX250 Network Services platform:
user@jdm> request system zeroize
To format the system by deleting all user data, configuration details, and to upgrade the software on the NFX250 Network Services platform:
user@jdm> request system software add package clean-install
The zeroize and clean-install commands
work only for primary installation and do not work for backup installation.
The zeroize and clean-install commands might remove all user installed software packages, VNF
files of the user, and so on. After completing these operations, you
must fetch these information and reinstall the software. You might
require a console access to configure the basic remote network access
if the system is in factory state.
Upgrading an Image on the Disaggregated Junos OS Platform
To upgrade the images of JCP, JDM, and the host OS on the disaggregated Junos OS platform:
content_copy zoom_out_mapuser@jdm>request system software add jinstall reboot
For example:
content_copy zoom_out_mapuser@jdm>request system software add /var/tmp/jinstall-nfx-2-flex-15.1X53-D40.3.secure-domestic-signed.tgz reboot | no-more System software upgrade in progress, please wait... Pushing Junos image package to the host... Installing /var/tmp/install-media-nfx-2-junos-15.1X53-D45.3.secure.tgz Extracting the package ... total 1191772 -rw-r--r-- 1 20607 758 313873261 Nov 22 09:18 jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz -rw-r--r-- 1 20607 758 906487459 Nov 22 09:18 jinstall-nfx-2-junos-15.1X53-D45.3.secure-app.tgz ============================================ Host OS upgrade is FORCED Current Host kernel version : 3.14.61-rt58-WR7.0.0.13_ovp Package Host kernel version : 3.14.61-rt58-WR7.0.0.13_ovp Current Host version : 3.0.2 Package Host version : 3.0.2 Min host version required for applications: 2.2.0 ============================================ Validate linux image... upgrade_platform: ------------------- upgrade_platform: Parameters passed: upgrade_platform: silent=0 upgrade_platform: package=/var/tmp/tmp.LKb5WwiFu8junos_cli_upg/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz upgrade_platform: clean install=0 upgrade_platform: on primary =0 upgrade_platform: clean upgrade=0 upgrade_platform: Need reboot after staging=1 upgrade_platform: ------------------- upgrade_platform: upgrade_platform: Checking input /var/tmp/tmp.LKb5WwiFu8junos_cli_upg/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz ... upgrade_platform: Input package /var/tmp/tmp.LKb5WwiFu8junos_cli_upg/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz is valid. Secure Boot is enforced. ALLOW:usr/secureboot/grub/BOOTX64.EFI ALLOW:boot/bzImage-intel-x86-64.bin ALLOW:boot/initramfs.cpio.gz Setting up Junos host applications for installation ... Installing Host OS ... upgrade_platform: ------------------- upgrade_platform: Parameters passed: upgrade_platform: silent=0 upgrade_platform: package=/var/tmp/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz upgrade_platform: clean install=0 upgrade_platform: on primary =0 upgrade_platform: clean upgrade=0 upgrade_platform: Need reboot after staging=0 upgrade_platform: ------------------- upgrade_platform: upgrade_platform: Checking input /var/tmp/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz ... upgrade_platform: Input package /var/tmp/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz is valid. Secure Boot is enforced. ALLOW:usr/secureboot/grub/BOOTX64.EFI ALLOW:boot/bzImage-intel-x86-64.bin ALLOW:boot/initramfs.cpio.gz upgrade_platform: Staging the upgrade package - /var/tmp/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz.. ./ ./bzImage-intel-x86-64.bin ./bzImage-intel-x86-64.bin.psig ./grub/ ./grub/grub.conf ./grub/grub.efi ./initramfs.cpio.gz ./initramfs.cpio.gz.psig ./linux.checksum ./version.txt ./upgrade_platform ./host-version ./platform_info ./initrd.cpio.gz bzImage-intel-x86-64.bin: OK initramfs.cpio.gz: OK version.txt: OK upgrade_platform: Checksum verified and OK... 1528703 blocks upgrade_platform: Staging of /var/tmp/jinstall-nfx-2-junos-15.1X53-D45.3.secure-linux.tgz completed upgrade_platform: System need *REBOOT* to complete the upgrade upgrade_platform: Run upgrade_platform with option -r | --rollback to rollback the upgrade Host OS upgrade staged. Reboot the system to complete installation! Rebooting ... System going down for reboot in 30 seconds... System reboot in progress... Shutting down virtual-machines... Waiting for virtual-machines to shutdown, retry = 0 Waiting for virtual-machines to shutdown, retry = 1 Waiting for virtual-machines to shutdown, retry = 2 No virtual-machines active now. Rebooting the system... INIT: Sending processes the TERM signal {master:0} root@nfx250-m-p2a-sys11-jdm> Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 4169) . Unmount Junos cgroup... Done Stopping atd: OK Stopping domain name service: named. Unmounting cgroups...Done Stopping system message bus: dbus. stopping DNS forwarder and DHCP server: dnsmasq... stopped /usr/bin/dnsmasq (pid 9449 9448) done. Stopping docker: Stopping HOSTAP Daemon: no /usr/sbin/hostapd found; none killed hostapd. Shutting down irqbalance: no irqbalance found; none killed done Stopping ntpd: done stopping rsyslogd ... done Stopping internet superserver: xinetd. Waiting for sanlock to stop: Success Clearing ebtables rulesets: filter nat broute done. ok Stopping crond: OK Stopping S.M.A.R.T. daemon: smartd. Stopping network management services: snmpd snmptrapd libvirtMib_subagent. * Stopping virtualization library daemon: libvirtd Deconfiguring network interfaces... done. Stopping tcsd: OK Stopinit: Failed to release D-Bus name: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ping redis-server... Sending all processes the TERM signal... Sending all processes the KILL signal... Unmounting remote filesystems... Deactivating swap... Unmounting local filesystems... Rebooting... RE-FPGA-DRV: reboot notifier called with 0x0001 RE-FPGA-DRV: Please standby while rebooting. . .. .. .. . Booting from Flash A FPGA Reset Reason = 0x80 Primary BIOS version CBDE_SFP_00.21_01.01 Total Memory Size = 16GB Checking Primary BIOS code integrity...Passed! Press Esc for boot options ME is in normal operational state Booting HDD00.1 (StorFly VSFBM6CC100G-JUN)... Secure boot is enforced Welcome to GRUB! Secure Grub2 Diskboo
Reverting the System to the Factory-Default Configuration
To revert the system to factory-default configuration:
user@jdm# load factory-default warning: activating factory configuration
Rebooting the System
To reboot the system:
user@jdm>request system reboot
For example:
user@jdm>request system reboot Reboot the system ? [yes,no] (no) yes System reboot operation started, please wait... System going down for reboot in 30 seconds... System reboot in progress... Shutting down virtual-machines... . . . .
The time taken to reboot the system depends on the number of active VNFs. The system is rebooted only after all the active VNFs are shut down.
