License Management for Junos OS Platforms
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.
See also
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:
XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxx
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 1.
Table 1: Summary of License Management Fields
Field Name | Definition |
|---|---|
| Feature Summary | |
Feature | Name of the licensed feature:
|
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:
mgd: error: No valid upgrade license found for feature 'scale-subscriber'. Aborting Software upgrade. Validation failed
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 2 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 2: 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
| f1—MX5 to MX10 upgrade | Slot 1 and 2
|
MX10 | 40G | 0x555 | Slot 1 and 2
| f2—MX10 to MX40 upgrade | Slot 2 and first 2 ports on Slot 0
|
MX40 | 60G | 0x554 | Slot 1, SLot 2 and first 2 ports on Slot 0
| f3—MX40 to MX80 upgrade | Slot 2 and all ports on Slot 0
|
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 3.
Table 3: 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 3 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.
See also
Managing Licenses
Adding New Licenses (CLI Procedure)
Before adding new licenses, complete the following tasks:
Purchase the required licenses.
Establish basic network connectivity with the router or switch. For instructions on establishing basic connectivity, see the Getting Started Guide or Quick Start Guide for your device.
There are two ways to add licenses using the Junos OS CLI:
The system license keys key configuration statement enables you to configure and delete license keys in a Junos OS CLI configuration file.
The request system license add operational command installs a license through URL or using the license file.
On QFabric systems, install your licenses in the default partition of the QFabric system and not on the individual components (Node devices and Interconnect devices).
To add licenses, complete one of the following procedures:
Installing a License Using a Configuration Statement
Starting with Junos OS Release 15.1, you can configure and delete license keys in a Junos OS CLI configuration file. The system license keys key statement at the [edit] hierarchy level installs a license by using a configuration statement.
The system license keys key configuration statement is not required to install a license. The operational command request system license add installs a license immediately. But because the set system license keys key command is a configuration statement, you can use it to install a license as part of a configuration commit, either directly or by configuration file.
The license keys are validated and installed after a successful commit of the configuration file. If a license key is invalid, the commit fails and issues an error message. You can configure individual license keys or multiple license keys by issuing Junos OS CLI commands or by loading the license key configuration contained in a file. All installed license keys are stored in the /config/license/ directory.
Select a procedure to install a license using configuration:
Installing Licenses Using the CLI Directly
To install an individual license key using the Junos OS CLI:
- Issue the set system license keys key name statement.
The name parameter includes the license ID and the license key. For example:
[edit]user@device# set system license keys key "JUNOS_TEST_LIC_FEAT xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx"To install multiple license keys in the Junos OS CLI, issue the set system license keys key name statement for each license key to install. For example:
[edit]user@device# set system license keys key "key_1"set system license keys key "key_2"set system license keys key "key_2"set system license keys key "key_4" - Issue the commit command.[edit]user@device# commitcommit complete
- Verify that the license key was installed.
For example:
user@device# run show system licenseLicense usage: Licenses Licenses Licenses Expiry Feature name used installed needed sdk-test-feat1 0 1 0 permanent Licenses installed: License identifier: JUNOS_TEST_LIC_FEAT License version: 2 Features: sdk-test-feat1 - JUNOS SDK Test Feature 1 permanentAlternatively, you can issue the show system license command from operational mode.
Installing Licenses Using a Configuration File
Before you begin, prepare the configuration file. In
this example, use the Unix shell cat command
to write the license.conf file:
- Go to the shell.[edit]user@device# exituser@device> exit%
- Open the new
license.conffile.% cat > license.conf - Type the configuration information for the license key
or keys:
For a single license, for example, type the following content:
system { license { keys { key "JUNOS_TEST_LIC_FEAT xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx"; } } }For multiple license keys, for example, type something like this:
system { license { keys { key "key_1" key "key_2" key "key_3" ... key "key_n" } } }
- Press Ctrl+d to save the file.
To install a license key configuration in a file:
- Go to the CLI configuration mode.% cliuser@device> configure[edit]user@device#
- Load and merge the license configuration file.
For example:
user@device# load merge license.confload complete - Issue the show | compare command to see the
configuration.
For example:
[edit]user@device# show | compare[edit system]+ license { + keys { + key "JUNOS_TEST_LIC_FEAT xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx"; + } + } - Issue the commit command.[edit]user@device# commit
- To verify that the license key was installed, issue the show system license command.
For example:
root@switch> show system licenseLicense usage: Licenses Licenses Licenses Expiry Feature name used installed needed sdk-test-feat1 0 1 0 permanent Licenses installed: License identifier: JUNOS_TEST_LIC_FEAT License version: 2 Features: sdk-test-feat1 - JUNOS SDK Test Feature 1 permanent
Installing a License Using an Operational Command
Complete the procedure that relates to your system:
Adding a License to a Device with a Single Routing Engine
To add a new license key to the device using an operational command:
- From the CLI operational mode, enter one of the following
CLI commands:
To add a license key from a file or URL, enter the following command, specifying the filename or the URL where the key is located:
user@host> request system license add filename | urlTo add a license key from the terminal, enter the following command:
user@host> request system license add terminal
- When prompted, enter the license key, separating multiple
license keys with a blank line.
If the license key you enter is invalid, an error appears in the CLI output when you press Ctrl+d to exit license entry mode.
- Go on to Verifying Junos OS License Installation (CLI).
Adding a License to a Device with Dual Routing Engines
On routers that have graceful Routing Engine switchover (GRES) enabled, after successfully adding the new license on the master Routing Engine, the license keys are automatically synchronized on the backup Routing Engine as well. However, in case GRES is not enabled, the new license is added on each Routing Engine separately. This ensures that the license key is enabled on the backup Routing Engine during changeover of mastership between the Routing Engines.
To add a new license key to a router with dual Routing Engines without GRES:
After adding the new license key on the master Routing Engine, use the request chassis routing-engine master switch command to have the backup Routing Engine become the master Routing Engine.
Log in to the active Routing Engine and add the new license key, repeat the same step.
Adding a license key to the router or switch might be delayed
if a kernel resynchronization operation is in progress at that time.
The following message is displayed on the CLI when the license-adding
operation is about to be delayed:
A kernel re-sync
operation is in progress. License update may take several minutes
to complete.
See also
Deleting License Keys (CLI)
Before deleting a license, ensure that the features enabled by the license will not be needed.
You can use the request system license delete operational command, or the delete or deactivate configuration command to delete a license:
Using the Operational Command to Delete Licenses
To delete licenses using the request system license delete command:
- Display the licenses available to be deleted.
user@host> request system license delete license-identifier-list ?Possible completions: E00468XXX4 License key identifier JUNOS10XXX1 License key identifier JUNOS10XXX2 License key identifier JUNOS10XXX3 License key identifier JUNOS10XXX4 License key identifier [ Open a set of values
- To delete a license key or keys from a device using the
CLI operational mode, select one of the following methods:
Delete a single license by specifying the license ID. Using this option, you can delete only one license at a time.
user@host> request system license delete license-identifierDelete all license keys from the device.
user@host> request system license delete allDelete multiple license keys from the device. Specify the license identifier for each key and enclose the list of identifiers in brackets.
user@host> request system license delete license-identifier-list [JUNOS10XXX1 JUNOS10XXX3 JUNOS10XXX4 ...]Delete license(s) ? [yes,no] (no) yes
- Verify the license was deleted by entering the show system license command.
Using a Configuration Command to Delete Licenses
Starting in Junos OS Release
16.1, to remove licenses from the configuration, you can use either
the delete or deactivate configuration command. The delete command deletes a statement or identifier,
and all subordinate statements and identifiers contained within the
specified statement path are deleted with it. The deactivate command adds the inactive: tag to a statement,
effectively commenting out the statement or identifier from the configuration.
Statements or identifiers marked as inactive do not take effect when
you issue the commit command. To remove the inactive: tag from a statement, issue the activate command. Statements or identifiers that have been activated take
effect when you next issue the commit command.
The following procedure uses the delete command, but you could use the deactivate command as well.
To delete one or all licenses using the delete command:
You can use the deactivate command instead of the delete command in this procedure.
- Display the licenses available to be deleted.
Issue the run request system license delete license-identifier-list ? command from the configuration mode of the CLI.
[edit]user@host# run request system license delete license-identifier-list ?A list of licenses on the device is displayed:
Possible completions: E00468XXX4 License key identifier JUNOS10XXX1 License key identifier JUNOS10XXX2 License key identifier JUNOS10XXX3 License key identifier JUNOS10XXX4 License key identifier [ Open a set of values
- Delete the license or licenses you want.
To delete a single license, for example:
[edit]user@host# delete system license keys key “E00468XXX4”To delete all licenses, for example:
[edit]user@host# delete system license keys
- Commit the configuration by entering the commit command.
- Verify the license was deleted by entering the show system license command.
Verifying Junos OS License Installation (CLI)
To verify Junos OS license management, perform the following tasks:
Displaying Installed Licenses
Purpose
Verify that the expected licenses are installed and active on the device.
Action
From the CLI, enter the show system license command.
Sample Output
user@host> show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
subscriber-acct 0 1 0 permanent
subscriber-auth 0 1 0 permanent
subscriber-addr 0 1 0 permanent
subscriber-vlan 0 1 0 permanent
subscriber-ip 0 1 0 permanent
scale-subscriber 0 1000 0 permanent
scale-l2tp 0 1000 0 permanent
scale-mobile-ip 0 1000 0 permanent
Licenses installed:
License identifier: E000185416
License version: 2
Features:
subscriber-acct - Per Subscriber Radius Accounting
permanent
subscriber-auth - Per Subscriber Radius Authentication
permanent
subscriber-addr - Address Pool Assignment
permanent
subscriber-vlan - Dynamic Auto-sensed Vlan
permanent
subscriber-ip - Dynamic and Static IP
permanent
Meaning
The output shows a list of the license usage and a list of the licenses installed on the device. Verify the following information:
Each license is present. Licenses are listed in ascending alphanumeric order by license ID.
The state of each license is permanent.
A state of invalid indicates that the license key is not a valid license key. Either it was entered incorrectly or it is not valid for the specific device.
The feature for each license is the expected feature. The features enabled are listed by license. An all-inclusive license has all features listed.
All configured features have the required licenses installed. The Licenses needed column must show that no licenses are required.
Displaying License Usage
Purpose
Verify that the licenses fully cover the feature configuration on the device.
Action
From the CLI, enter the show system license usage command.
Sample Output
user@host> show system license usageLicenses Licenses Licenses Expiry Feature name used installed needed subscriber-addr 1 0 1 29 days scale-subscriber 0 1000 0 permanent scale-l2tp 0 1000 0 permanent scale-mobile-ip 0 1000 0 permanent
Meaning
The output shows any licenses installed on the device and how they are used. Verify the following information:
Any configured licenses appear in the output. The output lists features in ascending alphabetical order by license name. The number of licenses appears in the third column. Verify that you have installed the appropriate number of licenses.
The number of licenses used matches the number of configured features. If a licensed feature is configured, the feature is considered used. The sample output shows that the subscriber address pooling feature is configured.
A license is installed on the device for each configured feature. For every feature configured that does not have a license, one license is needed.
For example, the sample output shows that the subscriber address feature is configured but that the license for the feature has not yet been installed. The license must be installed within the remaining grace period to be in compliance.
Saving License Keys (CLI)
To save the licenses installed on a device:
- From operational mode, do one of the following tasks
To save the installed license keys to a file or URL, enter the following command:
user@host> request system license save filename | urlFor example, the following command saves the installed license keys to a file named
license.config:user@host>request system license save license.configTo output installed license keys to the terminal, enter the following command:
user@host> request system license save terminal
show system license
List of Syntax
SyntaxSyntax
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 13.3 for the MX Series 5G Universal Routing Platform.
Customer ID added to output of data center users in Junos OS Release 15.1.
Corrected output for duration of license added in Junos OS Release 17.4R1.
Description
Display licenses and information about how they are used.
Options
Required Privilege Level
maintenance
List of Sample Output
show system license (Virtual devices such as vMX and vSRX)show system license
show system license installed
show system license keys
show system license usage
show system license (MX104 Routers)
show system license installed (MX104 Routers)
show system license keys (MX104 Routers)
show system license usage (MX104 Routers)
show system license (MX104 Routers)
show system license installed (MX104 Routers)
show system license keys (MX104 Routers)
show system license usage (MX104 Routers)
show system license (MX104 Routers)
show system license installed (MX104 Routers)
show system license keys (MX104 Routers)
show system license usage (MX104 Routers)
show system license (QFX Series)
show system license (QFX5110 Switch with Disaggregated Feature License)
show system license key-content srx_1year_sub.lic
Output Fields
Table 4 lists the output fields for the show system license command. Output fields are listed in the approximate order in which they appear.
Table 4: show system license Output Fields
Field Name | Field Description |
|---|---|
Feature name | Name assigned to the configured feature. You use this information to verify that all the features for which you installed licenses are present. |
Licenses used | Number of licenses used by a router or switch. You use this information to verify that the number of licenses used matches the number configured. If a licensed feature is configured, the feature is considered used. In Junos OS Release 10.1 and later, the Licenses used column displays the actual usage count based on the number of active sessions or connections as reported by the corresponding feature daemons. This is applicable for scalable license-based features such as Subscriber Access (scale-subscriber), L2TP (scale-l2tp), Mobile IP (scale-mobile-ip), and so on. |
Licenses installed | Information about the installed license key:
|
Licenses needed | Number of licenses required for features being used but not yet properly licensed. |
Expiry | Amount of time left within the grace period before a license is required for a feature being used. |
Sample Output
show system license (Virtual devices such as vMX and vSRX)
user@host> show system license License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
VMX-SCALE 0 1 0 permanent
VMX-BANDWIDTH 0 130000 0 permanent
mobile-next-DPI-base 0 1000 0 permanent
mobile-next-policy-prepaid-scaling 0 1000 0 permanent
mobile-next-http-app-scaling 0 1000 0 permanent
mobile-next-scaling 0 1000 0 permanent
logical-system 0 1 0 permanent
ax411-wlan-ap 0 2 0 permanent
dynamic-vpn 0 2 0 permanent
scale-mobile-ip 0 1000 0 permanent
scale-l2tp 0 1000 0 permanent
scale-subscriber 0 64010 0 permanent
Licenses installed:
License identifier: RMS818090001
License version: 1
Software Serial Number: AID000000001
Customer ID: LABJuniperTest
License count: 1
Features:
VMX-SCALE - Max scale supported by the VMX
date-based, 2017-03-15 05:30:00 IST - 2017-05-14 05:30:00 IST
License identifier: RMS818020001
License version: 1
Software Serial Number: AID000000001
Customer ID: vMX-JuniperNetworks
License count: 1
Features:
VMX-SCALE - Max scale supported by the VMX
permanent
…
show system license
user@host> show system license
License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
subscriber-accounting 2 2 0 permanent
subscriber-authentication 1 2 0 permanent
subscriber-address-assignment 2 2 0 permanent
subscriber-vlan 2 2 0 permanent
subscriber-ip 0 2 0 permanent
scale-subscriber 2 3 0 permanent
scale-l2tp 4 5 0 permanent
scale-mobile-ip 1 2 0 permanent
Licenses installed:
License identifier: XXXXXXXXXX
License version: 2
Customer ID: ACME CORPORATIOM
Features:
subscriber-accounting - Per Subscriber Radius Accounting
permanent
subscriber-authentication - Per Subscriber Radius Authentication
permanent
subscriber-address-assignment - Radius/SRC Address Pool Assignment
permanent
subscriber-vlan - Dynamic Auto-sensed Vlan
permanent
subscriber-ip - Dynamic and Static IP
permanent
show system license installed
user@host> show system license installed License identifier: XXXXXXXXXX
License version: 2
Features:
subscriber-accounting - Per Subscriber Radius Accounting
permanent
subscriber-authentication - Per Subscriber Radius Authentication
permanent
subscriber-address-assignment - Radius/SRC Address Pool Assignment
permanent
subscriber-vlan - Dynamic Auto-sensed Vlan
permanent
subscriber-ip - Dynamic and Static IP
permanent
show system license keys
user@host> show system license keys XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxx
show system license usage
user@host> show system license usageLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
subscriber-accounting 2 2 0 permanent
subscriber-authentication 1 2 0 permanent
subscriber-address-assignment 2 2 0 permanent
subscriber-vlan 2 2 0 permanent
subscriber-ip 0 2 0 permanent
scale-subscriber 2 3 0 permanent
scale-l2tp 4 5 0 permanent
scale-mobile-ip 1 2 0 permanent
show system license (MX104 Routers)
In the following output, ports 0 and 1 are activated by installing the license to activate the first two built-in ports.
user@host> show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
scale-subscriber 0 1000 0 permanent
scale-l2tp 0 1000 0 permanent
scale-mobile-ip 0 1000 0 permanent
MX104-2x10Gig-port-0-1 0 1 0 permanent
Licenses installed:
License identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
show system license installed (MX104 Routers)
In the following output, ports 0 and 1 are activated by installing the license to activate the first two built-in ports.
user@host > show system license installedLicense identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
show system license keys (MX104 Routers)
In the following output, ports 0 and 1 are activated by installing the license to activate the first two built-in ports.
user@host > show system license keys
XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxx
show system license usage (MX104 Routers)
In the following output, ports 0 and 1 are activated by installing the license to activate the first two built-in ports.
user@host > show system license usageLicenses Licenses Licenses Expiry Feature name used installed needed scale-subscriber 0 1000 0 permanent scale-l2tp 0 1000 0 permanent scale-mobile-ip 0 1000 0 permanent MX104-2x10Gig-port-0-1 0 1 0 permanent
show system license (MX104 Routers)
In the following output, ports 2 and 3 are activated by installing the license to activate the next two built-in ports after installing the license to activate the first two built-in ports.
user@host > show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
scale-subscriber 0 1000 0 permanent
scale-l2tp 0 1000 0 permanent
scale-mobile-ip 0 1000 0 permanent
MX104-2x10Gig-port-0-1 0 1 0 permanent
MX104-2x10Gig-port-2-3 0 1 0 permanent
Licenses installed:
License identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
License identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-2-3 - MX104 2X10Gig Builtin Port(xe-2/0/2 & xe-2/0/3) upgrade
permanent
show system license installed (MX104 Routers)
In the following output, ports 2 and 3 are activated by installing the license to activate the next two built-in ports after installing the license to activate the first two built-in ports.
user@host > show system license installedLicense identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
License identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-2-3 - MX104 2X10Gig Builtin Port(xe-2/0/2 & xe-2/0/3) upgrade
permanent
show system license keys (MX104 Routers)
In the following output, ports 2 and 3 are activated by installing the license to activate the next two built-in ports after installing the license to activate the first two built-in ports.
user@host > show system license keys
XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxx
XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxx
show system license usage (MX104 Routers)
In the following output, ports 2 and 3 are activated by installing the license to activate the next two built-in ports after installing the license to activate the first two built-in ports.
user@host > show system license usageLicenses Licenses Licenses Expiry Feature name used installed needed scale-subscriber 0 1000 0 permanent scale-l2tp 0 1000 0 permanent scale-mobile-ip 0 1000 0 permanent MX104-2x10Gig-port-0-1 0 1 0 permanent MX104-2x10Gig-port-2-3 0 1 0 permanent
show system license (MX104 Routers)
In the following output, ports 0,1,2, and 3 are activated by installing a single license key to activate all four built-in ports.
user@host > show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
scale-subscriber 0 1000 0 permanent
scale-l2tp 0 1000 0 permanent
scale-mobile-ip 0 1000 0 permanent
MX104-2x10Gig-port-0-1 0 1 0 permanent
MX104-2x10Gig-port-2-3 0 1 0 permanent
Licenses installed:
License identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
MX104-2x10Gig-port-2-3 - MX104 2X10Gig Builtin Port(xe-2/0/2 & xe-2/0/3) upgrade
permanent
show system license installed (MX104 Routers)
In the following output, ports 0,1,2, and 3 are activated by installing a single license key to activate all four built-in ports.
user@host > show system license installedLicense identifier: XXXXXXXXXX
License version: 2
Features:
MX104-2x10Gig-port-0-1 - MX104 2X10Gig Builtin Port(xe-2/0/0 & xe-2/0/1) upgrade
permanent
MX104-2x10Gig-port-2-3 - MX104 2X10Gig Builtin Port(xe-2/0/2 & xe-2/0/3) upgrade
permanent
show system license keys (MX104 Routers)
In the following output, ports 0,1,2, and 3 are activated by installing a single license key to activate all four built-in ports.
user@host > show system license keys
XXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx
xxxxxx xxxxxx x
show system license usage (MX104 Routers)
In the following output, ports 0,1,2, and 3 are activated by installing a single license key to activate all four built-in ports.
user@host > show system license usageLicenses Licenses Licenses Expiry Feature name used installed needed scale-subscriber 0 1000 0 permanent scale-l2tp 0 1000 0 permanent scale-mobile-ip 0 1000 0 permanent MX104-2x10Gig-port-0-1 0 1 0 permanent MX104-2x10Gig-port-2-3 0 1 0 permanent
show system license (QFX Series)
user@switch> show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
qfx-edge-fab 1 1 1 permanent
Licenses installed:
License identifier: JUNOS417988
License version: 1
Features:
qfx-edge-fab - QFX3000 Series QF/Node feature license
permanent
show system license (QFX5110 Switch with Disaggregated Feature License)
user@switch> show system licenseLicense usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
bgp 0 1 0 2017-07-05 00:00:00 UTC
isis 0 1 0 2017-07-05 00:00:00 UTC
vxlan 0 1 0 2017-07-05 00:00:00 UTC
ovsdb 0 1 0 2017-07-05 00:00:00 UTC
jbs1 0 1 0 2017-07-02 00:00:00 UTC
upgrade1 0 1 0 2017-07-05 00:00:00 UTC
Licenses installed:
License identifier: JUNOS797095
License version: 4
Software Serial Number: 91730A00223925
Customer ID: Juniper
Features:
JUNOS-BASE-SERVICES-CLASS-1 - QFX Junos Base Services license for Class 1 HW
date-based, 2016-07-01 00:00:00 UTC - 2017-07-02 00:00:00 UTC
License identifier: JUNOS797646
License version: 4
Software Serial Number: 91730A00224207
Customer ID: Juniper
Features:
CLASS-1-JUNOS-BASE-ADVANCED-UPGRADE - Class 1 Junos Base to Advanced Services Upgrade
date-based, 2016-07-04 00:00:00 UTC - 2017-07-05 00:00:00 UTC
{master:0}
show system license key-content srx_1year_sub.lic
License Key Content:
License Id: LICENSE-1
License version: 4
Valid for device: CW2716AF0740
Features:
idp-sig - IDP Signature
date-based, 2016-07-03 00:00:00 GMT - 2017-07-03 00:00:00 GMTshow system license (View)
List of Syntax
SyntaxSyntax
Release Information
Command introduced in Junos OS Release 9.5. Logical system status option added in Junos OS Release 11.2.
Description
Display licenses and information about how licenses are used.
Options
Required Privilege Level
view
List of Sample Output
show system licenseshow system license installed
show system license keys
show system license usage
show system license status logical-system all
Output Fields
Table 5 lists the output fields for the show system license command. Output fields are listed in the approximate order in which they appear.
Table 5: show system license Output Fields
Field Name | Field Description |
|---|---|
Feature name | Name assigned to the configured feature. You use this information to verify that all the features for which you installed licenses are present. |
Licenses used | Number of licenses used by the device. You use this information to verify that the number of licenses used matches the number configured. If a licensed feature is configured, the feature is considered used. |
Licenses installed | Information about the installed license key:
|
Licenses needed | Number of licenses required for features being used but not yet properly licensed. |
Expiry | Time remaining in the grace period before a license is required for a feature being used. |
Logical system license status | Displays whether a license is enabled for a logical system. |
Sample Output
show system license
user@host> show system license
License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
av_key_kaspersky_engine 1 1 0 2012-03-30 01:00:00 IST
wf_key_surfcontrol_cpa 0 1 0 2012-03-30 01:00:00 IST
dynamic-vpn 0 1 0 permanent
ax411-wlan-ap 0 2 0 permanent
Licenses installed:
License identifier: JUNOS301998
License version: 2
Valid for device: AG4909AA0080
Features:
av_key_kaspersky_engine - Kaspersky AV
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
License identifier: JUNOS302000
License version: 2
Valid for device: AG4909AA0080
Features:
wf_key_surfcontrol_cpa - Web Filtering
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
show system license installed
user@host> show system license installed
License identifier: JUNOS301998
License version: 2
Valid for device: AG4909AA0080
Features:
av_key_kaspersky_engine - Kaspersky AV
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
License identifier: JUNOS302000
License version: 2
Valid for device: AG4909AA0080
Features:
wf_key_surfcontrol_cpa - Web Filtering
date-based, 2011-03-30 01:00:00 IST - 2012-03-30 01:00:00 IST
show system license keys
user@host> show system license keys XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxx
show system license usage
user@host> show system license usage
Licenses Licenses Licenses Expiry
Feature name used installed needed
av_key_kaspersky_engine 1 1 0 2012-03-30 01:00:00 IST
wf_key_surfcontrol_cpa 0 1 0 2012-03-30 01:00:00 IST
dynamic-vpn 0 1 0 permanent
ax411-wlan-ap 0 2 0 permanent
show system license status logical-system all
user@host> show system license status logical-system
allLogical system license status:
logical system name license status
root-logical-system enabled
LSYS0 enabled
LSYS1 enabled
LSYS2 enabled traceoptions (System License)
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 8.5 for SRX Series and vSRX.
Statement introduced in Junos OS Release 14.1X53-D10 for EX Series and QFX Series.
Statement introduced in Junos OS Release 15.1 for M Series, MX Series, and T Series.
Description
Set trace options for licenses.
Options
/var/log.
By default, the name of the file is the name of the process being
traced.trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached.
Then the oldest trace file is overwritten.If you specify a maximum number of files, you also must specify a maximum file size with the size maximum file-size option.
Range: 2 through 1000 files
Default: 10 files
Range: 10 KB through 1 GB
Default: 128 KB
all—Trace all operations.
config—Trace license configuration processing.
events—Trace licensing events and their processing.
Required Privilege Level
trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration.
request system license add
List of Syntax
SyntaxSyntax
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 9.5 for SRX Series devices.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Added additional information section on XML RPC in Junos OS Release 17.4.
Description
Adding a license key to the Junos OS devices to activate the feature.
Starting in Junos OS Release 18.3R1, the display xml rpc CLI option is supported for request system license add and request system license save commands while installing licenses on Juniper Networks devices.
Options
Additional Information
The | display xml rpc filter returns “xml rpc equivalent of this command is not available,” the following RPC is supported for license installation:
The following RPC is supported for license installation:
<rpc> <request-license-add> <key-data> key </key-data> </request-license-add> </rpc>
Where key-data is the license key data.
<rpc> <request-license-add> <filename> key-file </filename> </request-license-add> </rpc>
Where source is the URL of the source license key file.
Required Privilege Level
maintenance
List of Sample Output
request system license addOutput Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system license add
user@host> request system license add terminalXXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxx XXXXXXXXXX: successfully added add license complete (no errors)
request system license save
List of Syntax
SyntaxSyntax
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 9.5 for SRX Series devices.
Added additional information section on XML RPC in Junos OS Release 17.4.
Description
Save installed license keys to a file or URL.
Starting in Junos OS Release 18.3R1, the display xml rpc CLI option is supported for request system license add and request system license save commands while installing licenses on Juniper Networks devices.
Options
Additional Information
The following RPC is supported for saving installed license keys to a file or URL:
<rpc> <request-license-save> <filename>destination</filename> </request-license-save> </rpc>
Where destination is the URL of the destination license key file.
Required Privilege Level
maintenance
List of Sample Output
request system license saveOutput Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system license save
user@host> request system license save ftp://user@host/license.conf request system license update
Syntax
Release Information
Command introduced in Junos OS Release 9.5.
Description
Starts autoupdating license keys from the license portal.
The request system license update command always uses the default Juniper license server: https://ae1.juniper.net/.
The request system license update command is supported only on SRX, vSRX, and QFX Series devices.
The products supported by the Juniper Agile Licensing (JAL) portal includes: QFX series, SRX Series, EX Series, NFX, vBNG, vMX, vSRX, and ACX. For other Juniper products (SPACE, JSA, SBR Carrier, Screen OS and so on) access the License Management System (LMS).
Options
trial—Immediately updates trial license keys from the license portal.
Required Privilege Level
maintenance
List of Sample Output
request system license updaterequest system license update trial
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system license update
user@host> request
system license update Trying to update license keys from https://ae1.juniper.net has been sent, use show system license to check status.
request system license update trial
user@host> request
system license update trial Request to automatically update trial license keys from https://ae1.juniper.net has been sent, use show system license to check status.
request system license delete
List of Syntax
SyntaxSyntax
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Option license-identifier-list introduced in Junos OS Release 13.1.
Description
Delete a license key. You can choose to delete one license at a time, all licenses at once, or a list of license identifiers enclosed in brackets.
Options
Required Privilege Level
maintenance
license
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 8.5 for SRX Series and vSRX.
Options keys introduced in Junos OS Release 14.1X53-D10.
Statement introduced in Junos OS Release 14.1X53-D10 for EX Series and QFX Series, with option keys included.
Statement introduced in Junos OS Release 15.1 for M Series, MX Series, PTX Series, and T Series, with option keys included.
Description
Specify license information for the device.
Options
Range: 0 through 60 days
Range: 1 through 336 hours
[edit] user@device# set system license keys key "key_1" user@device# set system license keys key "key_2" user@device# set system license keys key "key_3" user@device# set system license keys key "key_4" user@device# commit commit complete
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
license-type
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 11.1 for FX Series switches.
Description
Configure the license type and the scope of SDK application deployment.
Options
license—Type of license. Obtain correct value from the application’s provider.
deployment—Scope of SDK application deployment. You can configure a set of deployments. Obtain correct value from the application’s provider.
Required Privilege Level
admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.