Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

License Configuration

 

Installing Junos OS Licenses on Virtual Chassis Member Routers

To enable some Junos OS features or router scaling levels, you might have to purchase, install, and manage separate software license packs. The presence on the router of the appropriate software license keys (passwords) determines whether you can configure and use certain features or configure a feature to a predetermined scale.

Before you configure an MX Series Virtual Chassis, install the following Junos OS software licenses on each MX Series router to be configured as a member of the Virtual Chassis:

  • MX Virtual Chassis Redundancy Feature Pack—You must install a unique MX Virtual Chassis Redundancy Feature Pack for each member router in the Virtual Chassis. If you issue the request virtual-chassis member-id set, request virtual-chassis member-id delete, request virtual-chassis vc-port set, or request virtual-chassis vc-port delete command to set or delete member IDs or Virtual Chassis ports without first installing an MX Virtual Chassis Redundancy Feature Pack on both member routers, the software displays a warning message that you are operating without a valid Virtual Chassis software license.

    There is no separate license for Virtual Chassis like there is for Virtual Chassis Fabric.

  • Junos OS feature licenses—Purchase and install the appropriate Junos OS feature licenses to enable use of a particular software feature or scaling level in your network. You must install the required feature licenses on each member router in the Virtual Chassis.

Sometimes, if a Virtual Chassis member is newly installed, the licenses are lost, creating a situation in which any new license installed in master Routing Engine will get synced across all members, but any previously installed license (any license installed before the newly installed member) does not get synced. In this case, you must reinstall (delete and add) licenses in the master Routing Engine if a Virtual Chassis member is replaced. This procedure will sync all installed licenses to all members.

This topic covers the following procedures:

Installing Junos OS Licenses on Members

Before you begin:

To install Junos OS licenses on each member router in the Virtual Chassis:

  1. Install the required licenses on the MX Series router to be designated as the protocol master for the Virtual Chassis.
    1. Install the MX Virtual Chassis Redundancy Feature Pack.

    2. Install the Junos OS feature licenses required for your software feature or scaling level.

  2. Install the required licenses on the MX Series router to be designated as the protocol backup for the Virtual Chassis.
    1. Install the MX Virtual Chassis Redundancy Feature Pack.

    2. Install the Junos OS feature licenses required for your software feature or scaling level.

  3. (Optional) Verify the license installation on each member router.

    For example:

Reinstalling Junos OS Licenses on New Members

When you need to install a new Virtual Chassis member router, use this procedure to ensure all installed licenses are synced to all members.

Before adding the new Routing Engine to the Virtual Chassis, install required operational packages. This is like the first procedure, Installing Junos OS Licenses on Members.

To sync Junos OS licenses from master to newly replaced virtual chassis members:

  1. On the master router, exit the CLI to switch to user root.
    user@host> start shell user root
  2. Enter the root password and go back into the CLI.
  3. Copy the licenses from the master member to the Routing Engine that does not have licenses installed (that is, the newly installed Routing Engine).
    user@host> file copy /config/license/*.lic member0-re0:/config/license/

Configuring the JET Application and its License on a Device Running Junos OS

Before you can start a JET application on a device running Junos OS, first determine if you must configure the license. License configuration for JET applications is required only if you are deploying on-box applications written in C or C++ and built using the Juniper Extension Toolkit (JET) development environment. For simple Python JET applications, which do not require licensing, this task is not required.

This topic contains two examples of configuring JET applications to run on Junos OS:

Configuring a Python Application to Run on a Device

To configure a JET Python application and its license on a device:

  1. (Optional if Python application is signed) Issue the set system scripts language python command.

    If you do not include the language python statement, you cannot execute unsigned Python scripts on the device.

    Junos OS supports using symbolic links for files in the /var/db/scripts/jet directory, but the device will only execute the script at the target location if it is signed.

  2. At the [edit system extensions] hierarchy level, configure the application’s provider’s ID, for example:

    The same provider license must be used to configure a JET application to run on Junos OS as was used to package it.

  3. Configure the license type and deployment scope.
  4. Commit the configuration.

Configuring a C or C++ Application to Run on a Device

To configure a JET C or C++ application:

  1. Configure the application’s provider’s ID, license type, and deployment scope.

    The following application example was packaged using chef as the provider license:

    The same provider license must be used to configure a JET application to run on Junos OS as was used to package it.

  2. Commit the configuration and exit to operational mode.

Configuring the Router to Strictly Enforce the Subscriber Scaling License

To enable some Juniper Networks Junos OS features or router scaling levels, you might have to purchase, install, and manage separate software license packs. The presence on the router of the appropriate software license keys (passwords) determines whether you can configure and use certain features or configure a feature to a predetermined scale.

For the latest information about subscriber access licensing, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Subscriber Secure Policy Licensing Requirements

To enable and use subscriber secure policy, you must install and properly configure the Subscriber Secure Policy license.

You can configure the router to strictly enforce the subscriber scaling feature, which is part of the Junos Subscriber Access Feature Pack license. The subscriber scaling feature specifies the maximum number of subscribers that can be logged in at any one time.

When you configure strict scaling license support, the router performs the following actions:

  • Strictly enforces the subscriber scaling license and does not allow any grace period. When the number of logged-in subscriber reaches the number allowed by the scaling license, no additional subscribers are allowed to log in.

  • Creates the informational log message, “90 percent of installed subscriber scale licenses in use" in /var/log/messages, to inform you when you have 10 percent of the total allowed licenses remaining. The router clears this condition when license usage falls below 90 percent. The log message is created again if the 90 percent usage is later reached.

To configure the router to strictly enforce the subscriber scaling license:

  1. Specify that you want to configure subscriber management.
  2. Configure the router to enforce the scaling license.