Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Software License Overview

 

Platforms Supported in the Licensing Guide

This guide describes how to install, manage, and monitor licenses on Juniper Networks devices. Table 1 shows the platforms supported in the licensing guide.

Table 1: Platforms Supported in the Licensing Guide

Category

Platforms

Juniper Flex Program

cRPD, MPC10E Line Cards, MX204 Router, QFX5120-32C, QFX5200-32C-L, QFX5220-32CD, and QFX5220-128C

Routing

cRPD, M Series, MX Series, PTX Series, T Series, and vMX

Security

SRX Series and vSRX

Switching

EX Series, QFX Series, and QFabric System

Network Management

Junos Space, Network and Security Manager (NSM), and J-Web Device Manager

Junos OS Feature Licenses

Some Junos OS software features require a license to activate the feature. To enable a licensed feature, you need to purchase, install, manage, and verify a license key that corresponds to each licensed feature. To conform to Junos OS feature licensing requirements, you must purchase one license per feature per device. The presence of the appropriate software license key on your device determines whether you are eligible to configure and use the licensed feature.

To speed deployment of licensed features, Junos OS software implements an honor-based licensing structure and provides you with a 30-day grace period to use a licensed feature without a license key installed. The grace period begins when you configure the feature and your device uses the licensed feature for the first time, but not necessarily when you install the license. After the grace period expires, the system generates system log messages saying that the feature requires a license. To clear the error message and use the licensed feature properly, you must install and verify the required license.

Data center customers, for example those using the QFX platform, use universal licenses. Starting in Junos OS Release 15.1, to ensure that license keys are used properly, Juniper Networks license key generation is enhanced to specify a customer ID in the license key. You can see the customer ID displayed in the output of the show system license command.

For information about how to purchase software licenses, contact your Juniper Networks sales representative.

License Enforcement

For features or scaling levels that require a license, you must install and properly configure the license to meet the requirements for using the licensable feature or scale level. The device enables you to commit a configuration that specifies a licensable feature or scale without a license for a 30-day grace period. The grace period is a short-term grant that enables you to start using features in the pack or scale up to the system limits (regardless of the license key limit) without a license key installed. The grace period begins when the licensable feature or scaling level is actually used by the device (not when it is first committed). In other words, you can commit licensable features or scaling limits to the device configuration, but the grace period does not begin until the device uses the licensable feature or exceeds a licensable scaling level.

Configurations might include both licensed and nonlicensed features. For these situations, the license is enforced up to the point where the license can be clearly distinguished. For example, an authentication-order configuration is shared by both Authentication, Authorization, and Accounting (AAA), which is licensed, and by Layer 2 Tunneling Protocol (L2TP), which is not licensed. When the configuration is committed, the device does not issue any license warnings, because it is not yet known whether AAA or L2TP is using the configuration. However, at runtime, the device checks for a license when AAA authenticates clients, but does not check when L2TP authenticates clients.

The device reports any license breach as a warning log message whenever a configuration is committed that contains a feature or scale limit usage that requires a license. Following the 30-day grace period, the device periodically reports the breach to syslog messages until a license is installed and properly configured on the device to resolve the breach.

Successful commitment of a licensable feature or scaling configuration does not imply that the required licenses are installed or not required. If a required license is not present, the system issues a warning message after it commits the configuration.

Junos OS Feature License Keys

This section contains the following topics:

License Key Components

A license key consists of two parts:

  • License ID—Alphanumeric string that uniquely identifies the license key. When a license is generated, it is given a license ID.

  • License data—Block of binary data that defines and stores all license key objects.

For example, in the following typical license key, the string XXXXXXXXXX is the license ID, and the trailing block of data is the license data:

The license data defines the device ID for which the license is valid and the version of the license.

License Management Fields Summary

The Licenses page displays a summary of licensed features that are configured on the device and a list of licenses that are installed on the device. The information on the license management page is summarized in Table 2.

Table 2: Summary of License Management Fields

Field Name

Definition

Feature Summary 

Feature

Name of the licensed feature:

  • Features—Software feature licenses.

  • All features—All-inclusive licenses

Licenses Used

Number of licenses currently being used on the device. Usage is determined by the configuration on the device. If a feature license exists and that feature is configured, the license is considered used.

Licenses Installed

Number of licenses installed on the device for the particular feature.

Licenses Needed

Number of licenses required for legal use of the feature. Usage is determined by the configuration on the device: If a feature is configured and the license for that feature is not installed, a single license is needed.

Installed Licenses 

ID

Unique alphanumeric ID of the license.

State

Valid—The installed license key is valid.

Invalid—The installed license key is not valid.

Version

Numeric version number of the license key.

Group

If the license defines a group license, this field displays the group definition.

If the license requires a group license, this field displays the required group definition.

Because group licenses are currently unsupported, this field is always blank.

Enabled Features

Name of the feature that is enabled with the particular license.

Expiry

Verify that the expiration information for the license is correct.

For Junos OS, only permanent licenses are supported. If a license has expired, it is shown as invalid.

To speed deployment of licensed features, Juniper Networks implements an honor-based licensing structure and provides you with a 30-day grace period to use a licensed feature without a license key installed. The grace period begins when you configure the feature and your device uses the licensed feature for the first time, but not necessarily when you install the license. After the grace period expires, the system generates system log messages saying that the feature requires a license. To clear the error message and use the licensed feature properly, you must install and verify the required license.

Data center customers, for example those using the QFX platform, use universal licenses. Starting in Junos OS Release 15.1, to ensure that license keys are used properly, Juniper Networks license key generation is enhanced to specify a customer ID in the license key. You can see the customer ID displayed in the output of the show system license command.

Release-Tied License Keys and Upgrade Licenses on MX Series Routers

The Junos OS licensing infrastructure currently associates a license feature with attributes such as date, platform, and validity. In addition to these attributes, for MX Series routers running Junos OS Release 12.2 and later, a licensed feature can be associated with a release number at the time of generating the license key. This type of release-tied license key is used to validate a particular licensed feature while attempting a software upgrade. The upgrade process aborts if the release number in the license key is earlier than the Junos OS release number to which the system is being upgraded.

Additionally, an upgrade license key can be generated for a release-tied licensed feature. An upgrade license key is used for carrying forward a capacity license to the upgrade release. Although an upgrade license might be an acceptable license on the current release, it does not add to the existing capacity limit. The capacity added in the upgrade license key is valid for the upgrade software release only.

The release number embedded in the license key indicates the maximum release number up to which Junos OS can be upgraded.

As an example, assume that your system is running Junos OS Release 12.2 and is using the scale-subscriber licensed feature with a later release-tied upgrade license key installed. If you request a software upgrade to the later release of Junos OS, the software upgrade operation fails and the following error message is displayed:

In this example, to successfully upgrade to the later release of Junos OS, the release number included in the upgrade license key should be greater than or equal to the later release number. Also, you can perform software upgrades up to the previous release without any additional license keys to retain the existing scale limit.

When you install a release-tied license, the following apply:

  • You can purchase an upgrade capacity license only if a base capacity license for the same scale-tier has already been generated or purchased.

  • You cannot install an upgrade license if the capacity does not match any of the existing base capacity licenses on the system.

  • The license installation fails when you install a lower release number license key on a higher software release number.

  • A release-tied license can be installed on a Junos OS release number that is lower than or equal to the release number included in the license key. For example, a 12.2 license key is valid on Junos OS Release 12.1.

  • An upgrade license is valid only on the target release number specified in the license key, but can be installed on an earlier Junos OS release. For example, a 4 K scale-tier upgrade license for Junos OS Release 12.2 can be installed on an earlier release, and the installed count of licenses remains unaltered.

  • Release-tied licenses of the previous release are not deleted on upgrading Junos OS to a newer release version.

Licensable Ports on MX5, MX10, and MX40 Routers

Starting with Junos OS Release 12.2, license keys are available to enhance the port capacity on MX5, MX10, and MX40 routers up to the port capacity of an MX80 router. The MX5, MX10, and MX40 routers are derived from the modular MX80 chassis with similar slot and port assignments, and provide all functionality available on an MX80 router, but at a lower capacity. Restricting port capacity is achieved by making a set of MIC slots and ports licensable. MICs without a license are locked, and are unlocked or made usable by installing appropriate upgrade licenses.

The base capacity of a router is identified by the Ideeprom assembly ID (I2C ID), which defines the board type. However, the Junos OS licensing infrastructure allows the use of restricted ports without a license for a grace period of 30 days. After the grace period expires, the router reverts back to the base capacity if no upgrade license is purchased and installed for the locked ports. The I2C ID along with an upgrade license determine the final capacity of an MX5, MX10, or MX40 router.

The MX5, MX10, MX40, and MX80 routers support the following types of MICs:

  • A built-in 10-Gigabit Ethernet MIC with four 10-Gigabit Ethernet ports

  • Two front-pluggable MICs

A feature ID is assigned to every license upgrade for enhancing port capacity. Table 3 displays the chassis types and their associated port capacity, I2C ID, base capacity, feature ID, feature name, and the final capacity after a license upgrade.

Table 3: Upgrade Licenses for Enhancing Port Capacity

Chassis Type

Port Capacity

I2C ID

Base Capacity

Feature ID and Feature Name

Upgrade Capacity

MX5

20G

0x556

Slot 1

  • 1/MIC0

f1—MX5 to MX10 upgrade

Slot 1 and 2

  • 1/MIC0

  • 1/MIC1

MX10

40G

0x555

Slot 1 and 2

  • 1/MIC0

  • 1/MIC1

f2—MX10 to MX40 upgrade

Slot 2 and first 2 ports on Slot 0

  • 1/MIC1

  • First 2 ports on 0/MIC0

MX40

60G

0x554

Slot 1, SLot 2 and first 2 ports on Slot 0

  • 1/MIC0

  • 1/MIC1

  • First 2 ports on 0/MIC0

f3—MX40 to MX80 upgrade

Slot 2 and all ports on Slot 0

  • 1/MIC1

  • All 4 ports on 0/MIC0

When installing an upgrade license for enhancing port capacity on MX5, MX10 and MX40 routers, consider the following:

  • To upgrade an MX5 router to MX80 router capacity, licenses for all three features (f1, f2, f3) must be installed. All three features can be provided in a single license key.

  • To upgrade an MX10 router to MX40 router capacity, installing a license key with f2 feature is sufficient.

  • Non-applicable feature IDs in a license key reject the upgrade license. For example:

    • An f1 feature ID on an MX10 upgrade license key rejects the license.

    • Feature IDs f1 and f2 on an MX40 upgrade license key reject the entire license.

Port Activation on MX104 Routers

Starting with Junos OS Release 13.3, license keys are available to activate the ports on the MX104 router. MX104 routers have four built-in ports. By default, in the absence of valid licenses, all four built-in ports are deactivated. By installing licenses, you can activate any two of the four or all of the four built-in ports. For instance, you can install a license to activate the first two built-in ports (xe-2/0/0 and xe-2/0/1) or you can install a license to activate the next two built-in ports (xe-2/0/2 and xe-2/0/3). You can also install a license to activate all four built-in ports (xe-2/0/0, xe-2/0/1, xe-2/0/2, and xe-2/0/3). If you have already activated two of the built-in ports, you can install an additional license to activate the other two built-in ports on the MX104 router.

A feature ID is assigned to every license for activating the built-in ports on the MX104 router. The port license model with the feature ID is described in Table 4.

Table 4: Port Activation License Model for MX104 Routers

Feature ID

Feature Name

Functionality

F1

MX104 2X10G Port Activate (0 and 1)

Ability to activate first two built-in ports (xe-2/0/0 and xe-2/0/1)

F2

MX104 2X10G Port Activate (2 and 3)

Ability to activate next two built-in ports (xe-2/0/2 and xe-2/0/3)

Both the features are also provided in a single license key for ease of use. To activate all four ports, you must either install the licenses for both the features listed in Table 4 or the single license key for both features. If you install the single license key when feature IDs F1 and F2 are already installed, the license does not get rejected. Also, MX104 routers do not support the graceful license expiry policy. A graceful license expiry policy allows the use of a feature for a certain period of time (usually a grace period of 30 days), and reverts if the license for that feature is not installed after the grace period.

Related Documentation

Release History Table
Release
Description
Starting in Junos OS Release 15.1, to ensure that license keys are used properly, Juniper Networks license key generation is enhanced to specify a customer ID in the license key.