[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

JUNOS License Overview

As an honor-based licensing structure, JUNOS feature and scaling licenses are universal, and the same feature or scaling key can be installed and configured on multiple routers. However, to conform to JUNOS feature or scale licensing requirements, you must purchase one license per router.

This section contains the following topics:

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 router 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 router (not when it is first committed). In other words, you can commit licensable features or scaling limits to the router configuration, but the grace period does not begin until the router uses the licensable feature or exceeds a licensable scaling level.

Note: 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 router does not issue any license warnings, because it is not yet known whether AAA or L2TP is using the configuration. However, at runtime, the router checks for a license when AAA authenticates clients, but does not check when L2TP authenticates clients.

The router 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 router periodically reports the breach to the CLI command line until a license is installed and properly configured on the router to resolve the breach.

Note: 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.

Software Feature Licenses

Each license is tied to one software feature pack or scaling level, and that license is valid for only one router. Table 6 lists the software features, their current level of support, and the license name.

Table 6: JUNOS Software Feature Licenses

Licensed Software Feature

Supported?

License Name

Per-subscriber RADIUS accounting

Yes

JUNOS Subscriber Access Feature Pack

Per-subscriber RADIUS authentication

Yes

JUNOS Subscriber Access Feature Pack

Address pool assignment

Yes

JUNOS Subscriber Access Feature Pack

Change-of-Authorization (CoA)

Yes

JUNOS Service Management Feature Pack

Dynamic autosensed VLAN

No

JUNOS Subscriber Access Feature Pack

Dynamic and static IP

No

JUNOS Subscriber Access Feature Pack

Subscriber Secure Policy

Yes

Subscriber Secure Policy

Subscriber scaling (1000; base license)

Yes

Dynamic/Static Subscriber Base

Subscriber scaling (4000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (8000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (16000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (32000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (64000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (96000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (128000)

Yes

JUNOS Subscriber Access Feature Pack

Subscriber scaling (256000)

Yes

JUNOS Subscriber Access Feature Pack

L2TP scaling (1000; base license)

No

L2TP Base

Mobile IP scaling (1000; base license)

No

Mobile IP Base

License Key Components

To manage JUNOS licenses, you must understand the components of a license key. A license key consists of two parts:

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

li29183743 4ky27y acasck 82fsj6 jzsn4q ix8i8d adj7kr
                   8uq38t ix8i8d jzsn4q ix8i8d 4ky27y acasck
                   82fsj6 ii8i7e adj7kr 8uq38t ks2923 a9382e

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


[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]