Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Installing Application Packages

To install an application you install the application package or packages, and then you install the application on the router. An application package consists of binaries and their supplements. Application packages are distributed in a single .tgz file, which contains all the necessary resources to run the application.

As of Junos OS Release 12.3, Junos applications will install on Junos only if the application is built with the same release as the Junos OS Release on which the application is being installed. For example, an application built with Release 12.3R2 will only install on Junos OS Release 12.3R2 and will not install on Junos OS Release 12.3R1 or Junos OS Release 12.3R3 or Junos OS Release 13.1R1.

To install an application on a router, you configure the statements that describe the certificate. These statements include the provider name, the type of certificate, and the scope of application deployment. The provider name identifies the provider of the application to the system and allows application packages from that provider to be installed on the router. Furthermore, each package’s embedded certificate contains parameters about the provider’s partnership with Juniper Networks: the license type and deployment scope parameters. As with the provider name, these parameters for the package must be allowed by the configuration in order for the package’s installation to be allowed.

Note: If graceful routing engine switchover (GRES), or nonstop active routing (NSR) is enabled when you initiate a software installation, the software does not install properly. Make sure you issue the CLI delete chassis redundancy command when prompted. If GRES is enabled, it will be removed with this command. By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit routing-options] hierarchy level to disable it. For more information about GRES and NSR, see the Junos OS High Availability Library for Routing Devices.

1. Go to configuration mode of the CLI.
   user@router> configureEntering configuration mode [edit] user@router#
2. Go to the [edit system extensions] hierarchy level.
   [edit]user@router# edit system extensions[edit system extensions]
3. Configure the provider name, the license type, and the deployment scope associated with the application package. This information is supplied by the application’s provider.

   Note: Older certificates have all the certificate information concatenated in the providers name statement. These older certificates are still supported, and you can install packages signed with them.

   [edit system extensions]user@router# set providers name license-type license deployment-scope deployment

   For example, if abc is a provider name issued to a provider with a customer type of license and two deployment scopes, you might issue the following command.

   [edit system extensions]user@router# set providers abc license-type customer deployment-scope [ private commercial ]
4. Make other application-specific configuration changes as required by the application’s provider.
5. Commit the changes to the configuration.
   [edit system extensions]user@router# top[edit] user@router# commitcommit complete
6. Exit the configuration mode.
   [edit] user@router# exitExiting configuration mode
7. If you have a rescue configuration, update the rescue configuration by issuing the request system configuration rescue save command.
   user@host> request system configuration rescue save

   Note: Making sure the active configuration and the rescue configuration are consistent will prevent errors when installing applications. The system will find the same provider information in both.

8. In the operational mode of the CLI, install the application package. You can add one or multiple packages at one time.

   • To add one package at a time, use the request system software add command.
     user@router> request system software add package-name
   • To add multiple packages at once, use the request system software add set command.
     user@router> request system software add set [package-name1 package-name2 package-name3]

     For example, this set command allows you to install the core Junos OS package and Junos application packages simultaneously.

   You will see the application package being installed. For example, if your package’s filename is abcapps-11.1_2011.tgz.
   user@router> request system software add abcapps-11.1_2011.tgz

   Installing package '/var/home/user/abcapps-11.1_2011.tgz'
   ...
   Verified abcapps-11.1_2011.tgz signed by abc-enggroup
   Adding abcapps...
   Available space: 150060 require: 2598
   Saving package file in /var/sw/pkg/abcapps-11.1_2011.tgz Saving state
   for rollback ...