Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Licenses for PTX, MX, M and T Series

 

Software Features That Require Licenses on M Series, MX Series, and T Series Routers

Table 1 lists the licenses you can purchase for each M Series, MX Series, and T Series software feature. Each license allows you to run the specified software feature on a single device.

Note

The DHCP server functionality for Junos OS is part of the subscriber management feature. You must have the S-SA-FP, S-MX80-SA-FP or S-MX104-SA-FP license in order to enable the DHCP server. For service accounting, you must also have S-SSM-FP.

For information about how to purchase a software license, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Table 1: Junos OS Feature License Model Number for M Series, MX Series, and T Series Routers

Licensed Software Feature

Supported Devices

Model Number

Generalized Multiprotocol Label Switching (GMPLS) Support on Junos OS

M10i, M7i, M120, M160, M20, M320, M40e, T320, T640, and MX Series Routers

JS-GMPLS

IPv6 Support on Junos OS

M120, M160, M20, M320, M40e, T320, T640, and MX Series Routers

JS-IPv6

Logical Router Support for Junos OS

M10i, M120, M160, M20, M320, M40e, M7i, T320, T640, and MX Series Routers

JS-LR

J-Flow accounting license for Adaptive Services (AS) PIC and Multiservices PIC

M10i, M120, M160, M20, M320, M40e, M7i, T320, M10, M5, T640, and T1600

S-ACCT

Chassis license for Application Traffic Optimization service, policy enforcement and application statistics. This license includes S-AI and S-LDPF fucntionality and 1-year Signature Subscription License

MX104, MX240, MX480, MX960, M Series, and T Series Routers

S-ATO

Software License for Passive Monitoring Flow Collector Application, supporting 100 Kpps throughput; Chassis based license for Multiservices PIC

M320, T640, T320, T1600

S-COLLECTOR-100K

License to use Compressed Real-Time Transport Protocol (CRTP) feature in AS PIC and Multiservices PIC

M10i, M120, M160, M20, M320, M40e, M7i, T320, M10, M5, T640, and T1600

S-CRTP

Software License for Passive Monitoring DFC Application, supporting 100Kpps throughput; Chassis based license for Multiservices PIC

M320, T640, T320, and T1600

S-DFC-100K

Security Services license for AS PIC and Multiservices PIC

M10i, M7i, M5, M120, M160, M20, M320, M40e, T320, T640, M10, and T1600

S-ES

Chassis license for IDP service, policy enforcement. This license includes S-AI and S-LDPF fucntionality and 1-year Signature Subscription License

MX104, MX240, MX480, MX960, M Series, and T Series Routers

S-IDP

Junos-FIPS Software License

M10i, M7i, M320, M40e, T320, and T640

S-JUNOS-FIPS

Link Services Software License—up to 1023 ML bundles per Chassis for Multiservices PIC and Multiservices Dense Port Concentrator (DPC)

M5, M7i, M10, M10i, M20, M40e, M120, M320, T320, T640, T1600, MX240, MX480, and MX960

S-LSSL-1023

Link Services Software Ugrade License—from 255 to 1023 ML bundles per Chassis for Multiservices PIC and Multiservices DPC

M5, M7i, M10, M10i, M20, M40e, M120, M320, T320, T640, T1600, MX240, MX480, and MX960

S-LSSL-1023-UPG

Link Services Software Ugrade License—from 64 to 255 ML bundles per Chassis for AS PIC, Multiservices PIC, and Multiservices DPC

M5, M7i, M10, M10i, M20, M40e, M120, M320, T320, T640, T1600, MX240, MX480, and MX960

S-LSSL-255-UPG

Link Services Software License—up to 255 ML bundles per Chassis for AS PIC, Multiservices PIC, and Multiservices DPC

M10, M7i, M5, M120, M20, M320, M40e, T320, T640, M10i, T1600, MX240, MX480, and MX960

S-LSSL-256

Link Services Software License—up to 4 ML bundles per Chassis for AS PIC, Multiservices PIC, and Multiservices DPC

M10i, M120, M20, M320, M40e, M7i, T320, M10, M5, T640, T1600, MX240, MX480, and MX960

S-LSSL-4

Link Services Software License—up to 64 ML bundles per Chassis for AS PIC, MS PIC and MS DPC

M10, M7i, M5, M120, M20, M320, M40e, T320, T640, M10i, T1600, MX240, MX480, and MX960

S-LSSL-64

Link Services Software Upgrade License—from 4 to 64 ML bundles per Chassis for AS PIC, Multiservices PIC, and Multiservices DPC

M5, M7i, M10, M10i, M20, M40e, M120, M320, T320, T640, T1600, MX240, MX480, and MX960

S-LSSL-64-UPG

Software License for Passive Monitoring Flow Monitor Application, supporting 1M flows. Chassis based license for Multiservices PIC

M320, T640, T320, and T1600

S-MONITOR-1M

Network Address Translation (NAT), FW license on AS PIC and Multiservices PIC: Multi-instance

M10, M7i, M5, M120, M160, M20, M320, M40e, T320, T640, M10i, and T1600

S-NAT-FW-MULTI

NAT, FW license on AS PIC and Multiservices PIC: Single-instance

M10, M7i, M5, M120, M160, M20, M320, M40e, T320, T640, M10i, and T1600

S-NAT-FW-SINGLE

Software license for Packet trigger subscriber policy

MX240, MX480, MX960, M120, and M320

S-PTSP

Subscriber Access Feature Pack License Scaling (128000)

MX104, MX240, MX480, MX960, M120, and M320

S-SA-128K

Subscriber Access Feature Pack License Scaling (32000)

MX104, MX240, MX480, MX960, M120, and M320

S-SA-32K

Subscriber Access Feature Pack License Scaling (4000)

MX104, MX240, MX480, MX960, M120, M320, and MX80

S-SA-4K

Subscriber Access Feature Pack License Scaling (64000)

MX104, MX240, MX480, MX960, M120, and M320

S-SA-64K

Subscriber Access Feature Pack License Scaling (8000)

MX104, MX240, MX480, MX960, M120, M320, and MX80

S-SA-8K

Subscriber Access Feature Pack License Scaling (96000)

MX104, MX240, MX480, MX960, M120, and M320

S-SA-96K

Subscriber Access Feature Pack license

MX104, MX240, MX480, MX960, M120, and M320

S-SA-FP

Stateful Failover for Services on AS PIC and Multiservices PIC: Multilink PPP (MLPPP) only

M10, M7i, M5, M120, M160, M20, M320, M40e, T320, T640, M10i, and T1600

S-SERVICES-SFO

Subscriber Service Management Feature Packet License (RADIUS/SRC based Service Activation and Deactivation) Per-Service Accounting Features for Subscribers

MX104, MX240, MX480, MX960, M120, and M320

S-SSM-FP

Subscriber Traffic Lawful Intercept Feature Pack License

MX240, MX480, MX960, M120, M320, and MX80

S-SSP-FP

Software license for application aware traffic direct feature

MX240, MX480, MX960, M120, and M320

S-TFDIRECT-APP

Software license for subscriber aware traffic direct feature

MX240, MX480, MX960, M120, and M320

S-TFDIRECT-SUB

Video Services Feature Pack license

M120, M320, MX80, MX104, MX240, MX480, and MX960

S-VIDEO-FP

Port capacity enhancement Feature Pack License for MX5 routers

MX5

mx5-to-mx10-upgrade

Port capacity enhancement Feature Pack License for MX10 routers

MX10

mx10-to-mx40-upgrade

Port capacity enhancement Feature Pack License for MX40 routers

MX40

mx40-to-mx80-upgrade

Software Features That Require Licenses on MX Series Routers Only

Table 2 lists the licenses you can purchase for each MX Series software feature. Each license allows you to run the specified software feature on a single device.

Note
  • This is not a complete list of licenses. Contact your Juniper Networks representative for license information.

  • License is not required to use NAT feature on MX150, MX204, and MX10003 routers.

For information about how to purchase a software license, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Note

The DHCP server functionality for Junos OS is part of the subscriber management feature. You must have the S-SA-FP, S-MX80-SA-FP or S-MX104-SA-FP license in order to enable the DHCP server. For service accounting, you must also have S-SSM-FP.

Starting in Junos OS Release 16.1R1, after the completion of the 30 day grace period, DHCP bindings on MX series devices are limited to 10. This counts against broadband scale licenses S-MX104-SA-FP and S-SA-4K.

Licensing details for DHCP Relay Configurations—If processing dhcp-relay relay-option-82 is not required, then configure the forward-only statement under the [edit forwarding-options dhcp-relay relay-option (default-action | equals | starts-with)] hierarchy-level instead of configuring dhcp-relay directly. The forward-only DHCP Relay configurations do not require the S-SA-FP / S-MX80-SA-FP / S-MX104-SA-FP license to be installed. Also, configuring forward-only DHCP Relay assumes that the peer DHCP server is capable of returning relay-option-82 attributes originally sent via the DHCP Relay.

Subscriber Access Feature Pack (SKUs - S-SA-FP, S-MX80-SA-FP, and S-MX104-SA)

  • Per subscriber RADIUS accounting (time and volume based) – require SSM for per service accounting

  • RADIUS-based authentication and authorization

  • Subscriber configuration through client profiles at subscriber login

  • You require the S-SSM-FP SKU to change variable values within client profiles through radius grant or access accept, COA or RID, and SRC

  • RADIUS and SDX based address pool management

  • Static and dynamic IP management

  • Dynamic auto-sensed VLANs

  • Video edge services (S-SA-FP SKU is the superset and the S-VIDEO-FP SKU is not required)

Subscriber Services Management Feature Pack (SKUs - S-SSM-FP, S-MX80-SSM-FP, and S-MX104-SSM-FP)

  • Per service RADIUS accounting (time and volume based)

  • Activate or deactivate service profiles at subscriber login through the RADIUS grants or access accepts (services activation and deactivation VSAs) or changes to existing sessions through the RADIUS COA or RID, or SRC

  • Parameterization of service profiles

  • ANCP QoS adjustment based on synchronization rate through ANCP

Table 2: Junos OS Feature License Model Number for MX Series Routers

Licensed Software Feature

Supported Devices

Model Number

Upgrade license—from MX80-10G-ADV to MX80-40G-ADV

MX80

MX80-10G40G-UPG-ADV-B

Upgrade license—from MX80-10G to MX80-40G

MX80

MX80-10G40G-UPG-B

Upgrade license—from MX80-40G-ADV to full MX80

MX80

MX80-40G-UPG-ADV-B

Upgrade license—from MX80-40G to full MX80

MX80

MX80-40G-UPG-B

Upgrade license-–from MX80-5G-ADV to MX80-10G-ADV

MX80

MX80-5G10G-UPG-ADV-B

Upgrade license—from MX80-5G to MX80-10G

MX80

MX80-5G10G-UPG-B

Upgrade license to activate 2x10GE P2&3

MX104

S-MX104-ADD-2X10GE

Upgrade license to activate 2X10GE P0&1

MX104

S-MX104-UPG-2X10GE

Upgrade license to activate 4X10GE fixed ports on MX104

MX104

S-MX104-UPG-4X10GE

License to support per VLAN queuing on MX80

MX5, MX10, MX40, and MX80

S-MX80-Q

License to support per VLAN queuing on MX104

MX104

S-MX104-Q

Chassis-based software license for inline J-Flow monitoring on MX5, MX10, M40, MX80, and MX104 Series routers

MX5, MX10, MX40, MX80, and MX104

S-JFLOW-CH-MX5-104

Chassis-based software license for inline J-Flow monitoring on MX240 routers

MX240

S-JFLOW-CH-MX240

Chassis-based software license for inline J-Flow monitoring on MX480 routers

MX480

S-JFLOW-CH-MX480

Chassis-based software license for inline J-Flow monitoring on MX960 routers

MX960

S-JFLOW-CH-MX960

Chassis-based software license for inline J-Flow monitoring on MX2008 routers

MX2008

S-JFLOW-CH-MX2008

Chassis-based software license for inline J-Flow monitoring on MX2010 routers

MX2010

S-JFLOW-CH-MX2010

Chassis-based software license for inline J-Flow monitoring on MX2020 routers

MX2020

S-JFLOW-CH-MX2020

Flow monitoring and accounting features using J-Flow service on any Modular Port Concentrator (MPC) or MS-DPC

MX240, MX480, and MX960

S-ACCT-JFLOW-CHASSIS

Software License for in-line J-Flow service on Trio MPCs

MX240, MX480, MX960, MX2008, MX2010, and MX2020

S-ACCT-JFLOW-IN

Flow monitoring and accounting features using J-Flow service on any MPC limited to 10G of total JFLOW traffic

MX80

S-ACCT-JFLOW-IN-10G

Flow monitoring and accounting features using J-Flow service on any MPC limited to 10G of total JFLOW traffic

MX80

S-ACCT-JFLOW-IN-10G-UPG

Flow monitoring and accounting features using J-Flow service on any MPC limited to 5G of total JFLOW traffic

MX80

S-ACCT-JFLOW-IN-5G

Security services (IPsec, VPN and group VPN) license based on a single NPU for MS-MIC, MS-DPC or MS-MPC

MX Series Routers

S-ES-NPU

2000 IKE sessions on MS-DPC; Chassis based, limited to 6000 per Chassis

MX240, MX480, and MX960

S-ES-2K

4000 IKE sessions on MS-DPC; Chassis based, limited to 6000 per Chassis

MX240, MX480, and MX960

S-ES-4K

Upgrade from 2000 IKE sessions to 4000 IKE sessions on MS-DPC; Chassis based, limited to 6000 per Chassis

MX240, MX480, and MX960

S-ES-4K-UPG

6000 IKE sessions on MS-DPC; Chassis based, limited to 6000 per Chassis

MX240, MX480, and MX960

S-ES-6K

Upgrade from 4000 IKE sessions to 6000 IKE Sessions on MS-DPC; Chassis based, limited to 6000 per Chassis

MX240, MX480, and MX960

S-ES-6K-UPG

License to run stateful firewall on one NPU per MS-MIC, MS-DPC or MS-MPC

MX Series Routers

S-FW-NPU

License to support DS3 Channelization (down to DS0) on each Modular Interface Card (MIC) for MIC-3D-8DS3-E3; also requires license S-MX80-Q when used on the MX80 platform

MX5, MX10, MX40, MX80, MX104, MX240, MX480, MX960, MX2010, and MX2020

S-MIC-3D-8CHDS3

License to support full-scale Layer 3 routes and Layer 3 VPN

MX5, MX10, MX40, and MX80

S-MX80-ADV-R

License to support 256K routes

MX104

S-MX104-ADV-R1

License to support scaling Layer 3 and VPN routes to 1 million or more entries on MX104 platforms

MX104

S-MX104-ADV-R2

License to support full-scale Layer 3 routes and Layer 3 VPN on each slot for MPC-3D-16XGE-SFPP

MX240, MX480, MX960, MX2010, and MX2020

S-MPC-3D-16XGE-ADV-R

License to support full-scale Layer 3 routes and Layer 3 VPN on each slot for port queuing MPCs

MX240, MX480, MX960, MX2010, and MX2020

S-MPC-3D-PQ-ADV-R

License to support Precision Timing Protocol (PTP)

MX960

S-MPC-3D-PTP

License to support full-scale Layer 3 routes and Layer 3 VPN on each slot for hierarchical quality of service (HQoS) MPCs

MX240, MX480, MX960, MX2010, and MX2020

S-MPC-3D-VQ-ADV-R

Subscriber Management Feature Pack License

MX5, MX10, MX40, and MX80

S-MX80-SA-FP

(Includes S-LNS-IN)

MX104

S-MX104-SA-FP

(Includes S-LNS-IN)

Subscriber Access Feature Pack License

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-FP

Subscriber Service Management Feature Packet License—RADIUS and SRC-based service activation and deactivation per-service accounting features

MX5, MX10, MX40, and MX80

S-MX80-SSM-FP

MX104

S-MX104-SSM-FP

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SSM-FP

Upgrade to Traffic Direct Advanced (per MS-DPC)

MX960

S-MX-TD-UPG

License to run one instance of the NAT software on one NPU per MS-DPC

MX240, MX480, and MX960

S-NAT

License to support inline NAT software on MX5, MX10, MX40, MX80, MX104

MX5, MX10, MX40, MX80, and MX104

S-NAT-IN-MX5-104 (Replaces S-NAT-IN-MX40-MX80 and S-NAT-IN-MX5-MX10)

License to run one instance of the NAT software on one NPU per MS-MIC, MS-DPC, or MS-MPC

MX Series Routers

S-NAT-NPU (Replaces S-NAT-IN-MX40-MX80-UPG)

License to run NAT using any MPC in an MX Chassis

MX240, MX480, and MX960

S-NAT-IN-MX-CHASSIS

Subscriber Access Feature Pack License Scaling (4000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-4K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 4000 through 8000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-8K

Subscriber Access Feature Pack License Scaling (8000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-8K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 8000 through 16,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-16K

Subscriber Access Feature Pack License Scaling (16,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-16K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 16,000 through 32,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-32K

Subscriber Access Feature Pack License Scaling (32,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-32K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 32,000 through 64,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-64K

Subscriber Access Feature Pack License Scaling (64,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-64K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 64,000 through 96,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-96K

Subscriber Access Feature Pack License Scaling (96,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-96K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 96,000 through 128,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-128K

Subscriber Access Feature Pack License Scaling (128,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-128K

Upgrade license—Subscriber Access Feature Pack scaling license upgrade from 128,000 through 256,000 subscribers

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-UP-256K

Subscriber Access Feature Pack License Scaling (256,000)

MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SA-256K

Software License for Secure Flow Mirroring Service (FlowTap) (does not require MS-DPC)

MX80, MX104, MX240, MX480, and MX960

S-SFM-FLOWTAP-IN

License to run one instance of the SFW and software on a MS-DPC

MX960, MX480, and MX240

S-SFW

Software license for one member of an MX Virtual Chassis

MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-VCR

Upgrade license—from MX10 to equivalent of MX40; allows additional 2x10G fixed ports to be used on the MX10 router

MX10-T

MX10-40-UPG

Upgrade license—from MX10 to equivalent of MX80; allows additional 4x10G fixed ports to be used on the MX10 router

MX10-T

MX10-80-UPG

Upgrade license—from MX40 to equivalent of MX80; allows additional 2x10G fixed ports to be used on the MX40 router

MX40-T

MX40-80-UPG

Upgrade license—from MX5 to equivalent of MX10; allows second MIC slot to be used on the MX5 router

MX5-T

MX5-10-UPG

Upgrade license—from MX5 to equivalent of MX40; allows second MIC slot and 2x10G fixed ports to be used on the MX5 router

MX5-T

MX5-40-UPG

Upgrade license—from MX5 to equivalent of MX80. Allows second MIC slot and 4x10G fixed ports to be used on the MX5 router

MX5-T

MX5-80-UPG

License to use MX as Controller or Aggregation device for Junos Fusion. One license per MX is needed.

MX5, MX10, MX40, MX80, MX104, MX240, MX480, MX960, MX2010, and MX2020

S-MX-AD-FUSION-LIC

License to run any supported EX4300 model as a satellite device in Junos Fusion mode. One license per EX4300 is needed

MX240, MX480, MX960, MX2010, and MX2020

S-MX-SAT-EX4300

License to run any supported QFX5100 model as a satellite device in Junos Fusion mode. One license per QFX5100 is needed

MX240, MX480, MX960, MX2010, and MX2020

S-MX-SAT-QFX5100

Subscriber Traffic Lawful Intercept Feature Pack License

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-SSP-FP

Junos BB Policy Enforcement Feature License for dynamic subscriber authentication and authorization using NASREQ (1 per chassis)

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-BB-NASREQ

Junos BB Policy Enforcement feature license for PCRF communications using 3GPP Gx and Gx+ (1 per chassis)

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-BB-GX

Junos BB Policy Enforcement feature license for online charging using 3GPP Gy interface (1 per chassis)

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-BB-GY

Software License for Inline L2TP LNS (MX204, MX240/480/960, MX2008, MX2010/2020) (1 per chassis)

MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003

S-LNS-IN

Software Features That Require Licenses on M Series Routers Only

Table 3 lists the licenses you can purchase for each M Series software feature. Each license allows you to run the specified software feature on a single device.

For information about how to purchase a software license, contact your Juniper Networks sales representative at https://www.juniper.net/in/en/contact-us/.

Table 3: Junos OS Feature License Model Number for M Series Routers

Licensed Software Feature

Supported Devices

Model Number

J-Flow accounting license on Integrated Adaptive Services Module (ASM) and Integrated Multiservices Module

M7i

S-ACCT-BB

Security Services license on ASM and Integrated Multiservices Module

M7i

S-ES-BB

Layer 2 Tunneling Protocol (L2TP) L2TP Network Server (LNS) license for 16000 sessions on Multiservices PIC

M120

S-LNS-16K

L2TP LNS license Upgrade—from 8000 to 16000 sessions on Multiservices PIC

M120

S-LNS-16K-UPG

L2TP LNS license for 2000 sessions on AS PIC or Integrated Adaptive Services Module and Multiservices PIC

M7i, M10i, and M120

S-LNS-2K

L2TP LNS license for 4000 sessions on AS PIC or Integrated Adaptive Services Module and Multiservices PIC

M7i, M10i, and M120

S-LNS-4K

L2TP LNS license Upgrade—from 2000 to 4000 sessions on AS PIC or Integrated Adaptive Services Module and Multiservices PIC

M7i, M10i, and M120

S-LNS-4K-UPG

L2TP LNS license for 8000 sessions on Multiservices PIC

M7i, M10i, and M120

S-LNS-8K

L2TP LNS license Upgrade—from 4000 to 8000 sessions  on AS PIC and Multiservices PIC

M7i, M10i, and M120

S-LNS-8K-UPG

Link services software license on integrated ASM and Integrated Multi Services Module—up to 4 ML bundles

M7i

S-LSSL-BB

NAT, FW license on Integrated ASM and Integrated Multi Services Module: Multi instance

M7i

S-NAT-FW-MULTI-BB

NAT, FW license on Integrated ASM and Integrated Multi Services Module: Single instance

M7i

S-NAT-FW-SINGLE-BB

Tunnel services software license for AS PIC and Multiservices PIC (chassis license)

M7i and M10i

S-TUNNEL

License Modes for PTX Series Routers

PTX Series routers are available in two license variants: IR and R. Depending on the license purchased, the router offers full IP or LSR.

Table 4 describes the two license variants for the PTX1000.

Table 4: License Variants for the PTX1000

License

Description

Scale Restictions

IR

Scaled up LSR and peering

  • Up to 1 million routes in the forwarding information base (FIB)

  • Up to 6 million routes in the routing information base (RIB)

  • Up to 256 routing instances of the virtual routing and forwarding (VRF) instance type

  • Up to 128 thousand LSPs

R

Full IP core

None

Note

The license-mode statement is only supported on the PTX3000 and PTX5000 Series routers with third-generation FPCs.

Table 5 describes the two license variants for the PTX3000 and PTX5000.

Table 5: License Variants for the PTX3000 and PTX5000 FPCs

License

Description

Scale Restrictions

IR

Scaled up LSR and peering

  • Up to 2 million routes in the forwarding information base (FIB)

  • Up to 6 million routes in the routing information base (RIB)

  • Up to 256 routing instances of the virtual routing and forwarding (VRF) instance type

  • Up to 128 thousand LSPs

R

Full IP core

None

For the PTX3000 and PTX5000, If you purchase two FPCs: one with an IR license and one with an R license. After the FPCs are installed on a router, both FPCs appear identical. To distinguish between an FPC with an IR license and an FPC with an R license after the FPC is installed on the router, you must configure the license mode based on the license purchased. For instance, if you purchased an FPC with the IR license, you must configure the license mode for that FPC as IR. The license mode settings are set specific to each FPC slot. If the FPC is installed in a different slot, or moved to another device, the license mode settings must be reconfigured on the new slot or device. Also, the license mode settings previously configured must be deleted.

Note

The license mode settings are used only to provide information. You cannot set or alter the license of the FPC by configuring the license mode.

To view the current license mode settings, from the configuration mode, use the show chassis fpc command. To view the current license mode settings, from the operational mode, use the show chassis hardware extensive command. To delete the existing license mode settings, use the delete chassis fpc command.

License Modes for Enhanced MPCs Overview

Enhanced MPCs are available in three license variants. Before Junos OS Release 16.1, there were two variants: infrastructure routing (IR) and routing (R). Starting in Junos OS Release 16.1, there is also a base variant, making a total of three licence variants. All variants support an identical feature set, but with a few scale differences.Table 6 describes the three license variants.

Table 6: License Variants for MPCs

License

How to Identify

Description

base

No special suffix in the license name.

  • All Layer 2, Layer 2.5, and Layer 3 features.

  • Up to 32 Layer 3 routing instances of the virtual routing and forwarding (VRF) instance. The VRF support includes Layer 3 VPN (L3VPN).

  • Up to 2 million routes in the forwarding information base (FIB), provided there is hardware support. (FIB is also known as forwarding table.)

  • Up to 6 million routes in the routing information base (RIB), also known as routing table.

IR

-IR suffix in the license name.

  • All Layer 2, Layer 2.5, and Layer 3 features.

  • Up to 32 Layer 3 routing instances of the virtual routing and forwarding (VRF) instance. The VRF support includes Layer 3 VPN (L3VPN).

R

-R suffix in the license name.

Full-scale Layer 2, Layer 2.5, and Layer 3 features. Scale is determined by the hardware capabilities.

Suppose you have purchased two MPC4Es: one with IR license and one with R license. After the MPCs are installed on a router, both MPCs appear identical. To distinguish between an MPC with an IR license and an MPC with an R license after the MPC is installed on the router, you must configure the license mode based on the license purchased. For instance, if you have purchased an MPC with the IR license, you must configure the license mode for that MPC as IR. The license mode settings are set specific to each MPC slot. If the MPC is installed in a different slot, or moved to another device, the license mode settings must be reconfigured on the new slot or device. Also, the license mode settings previously configured must be deleted.

Note

The license mode settings are used only to provide information. You cannot set or alter the license of the MPC by configuring the license mode.

To view the current license mode settings on an MPC, from the configuration mode, use the show chassis fpc command. To view the current license mode settings on an MPC, from the operational mode, use the show chassis hardware extensive command. To delete the existing license mode settings on an MPC, use the delete chassis fpc command.

Configuring the License Mode for Specific Enhanced MPCs on MX Series Routers

Starting with Junos OS Release 14.2, you can set the license mode for enhanced MPCs such as MPC4E, MPC5E, and MPC6. Configuring the license mode enables you to distinguish between an MPC with an IR license and an MPC with an R license after the MPC is installed on the router. An MPC with an R license supports all the Layer 2, Layer 2.5, and Layer 3 features. An MPC with an IR license offers partial support for these features. For more information about the license variants, see License Modes for Enhanced MPCs Overview

Note

The license mode settings are used only to provide information. You cannot set or alter the license of the MPC when you configure the license mode.

Before you configure the license mode of the MPC, verify the license of the MPC. You will need this information do configure the license mode.

Do not try to set the license mode while the card is rebooting or the following error message will appear: Card not online or TRIO/DPC based.

To configure the license mode for MPCs on MX Series routers:

  1. Configure the license mode for the MPC in a specified MPC slot.

    If the MPC has an IR license, configure the license mode as IR. If the MPC has an R license, configure the license mode of the MPC as R.

  2. In configuration mode, verify the configuration, for example:
  3. After verifying the license mode, commit the changes by using the commit statement.

Example: Configuring the License Mode for MPC5E

This example describes how to configure the license mode for MPC5E on the MX480 router. It also describes how to remove the license mode settings and reconfigure the license mode settings on a new slot.

Requirements

This example uses the following hardware and software components:

  • Junos OS Release 14.2 or later for MX Series routers

  • A single MX480 router with MPC5E with R license

Overview

Configuring the license mode for an MPC enables you to distinguish between an MPC with an IR license and an MPC with an R license after the MPC is installed on the router.

Note

The license mode settings are used only to provide information. You cannot set or alter the license of the MPC when you configure the license mode.

The license mode settings are set specific to each MPC slot. If the MPC is installed in a different slot, or moved to another device, the license mode settings must be reconfigured on the new slot or device. Also, the license mode settings configured previously must be removed. You can view the license mode settings from both configuration mode and operational mode.

Topology

In this example, an MPC5E is installed in slot 4 of an MX480 router and has an R license. The R license indicates that all Layer 2, Layer 2.5, and Layer 3 features are supported on the MPC. You first configure the license mode of the MPC5E in slot 4 to R. After configuring the license mode, you can verify the license mode settings. You then install the MPC5E in slot 2 of the same router. License mode settings are set specific to each MPC slot. Therefore, the license mode setting must be reconfigured. After you move the MPC5E, delete the license mode setting on slot 4 and then reconfigure the license mode setting on slot 2.

Configuration

To configure the license mode for the MPC5E according to the topology specified in the overview section, perform these tasks:

Configuring the License Mode for MPC5E in Slot 4

Step-by-Step Procedure

To configure the license mode for the MPC5E in slot 4:

  1. Configure the license mode R for the MPC5E in slot 4:
  2. In configuration mode, verify the configuration.
  3. After verifying the license mode, commit the changes by using the commit statement.

Deleting the License Mode for MPC5E in Slot 4

Step-by-Step Procedure

To delete the license mode R for the MPC5E in slot 4:

  1. Delete the license mode for the MPC5E.
  2. In configuration mode, verify the configuration.
  3. After verifying the license mode, commit the changes by using the commit statement.

Configuring the License Mode for MPC5E in Slot 2

Step-by-Step Procedure

To configure the license mode for the MPC5E in slot 2:

  1. Configure the license mode R for the MPC5E.
  2. In configuration mode, verify the configuration.
  3. After verifying the license mode, commit the changes by using the commit statement.

Verification

To confirm that you have accurately configured the license mode settings on MPC5E, perform these tasks:

Verifying That License Mode Is Configured for MPC5E in Slot 4

Purpose

To verify that license mode R is configured for the MPC5E in slot 4.

Action

From operational mode, enter the show chassis hardware extensive command.

user@host> show chassis hardware extensive

Meaning

License mode R is configured for the MPC5E in slot 4.

Verifying That the Configured License Mode Is Deleted

Purpose

To verify that the configured license mode is deleted.

Action

From operational mode, enter the show chassis hardware extensive command.

user@host> show chassis hardware extensive

Meaning

The license mode setting has been removed for the MPC5E in slot 4.

Verifying That the License Mode Is Configured for MPC5E in Slot 2

Purpose

To verify that license mode R is configured for the MPC5E in slot 2.

Action

From operational mode, enter the show chassis hardware extensive command.

user@host> show chassis hardware extensive

Meaning

License mode R is configured for the MPC5E in slot 2.

Junos OS Feature License Keys

Some Junos OS software features require a license to be activated. To enable each licensed feature, you must purchase, install, manage, and verify a license key that corresponds to the licensed feature.

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.

Note

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

Table 8: 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 8 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.

Subscriber Access Licensing Overview

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.

Note

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.

Address-Assignment Pools Licensing Requirements

The address-assignment pool feature is part of the Junos OS Subscriber Management Feature Pack license. You must install and properly configure the license to meet the requirements for using the address-assignment pool feature.

Release History Table
Release
Description
Starting in Junos OS Release 16.1R1, after the completion of the 30 day grace period, DHCP bindings on MX series devices are limited to 10. This counts against broadband scale licenses S-MX104-SA-FP and S-SA-4K.
Starting in Junos OS Release 16.1, there is also a base variant, making a total of three licence variants.
Starting with Junos OS Release 14.2, you can set the license mode for enhanced MPCs such as MPC4E, MPC5E, and MPC6.