JUNOS OS Subscriber Management Scaling Values, Release 10.

About This Spreadsheet

This spreadsheet presents current subscriber access scaling values for various configurations
of MX Series 3D Universal Edge Routers and M Series Multiservice Edge Routers. The scaling values achieved for a
particular router depend on the hardware and software configuration. A router does not simultaneously support all
maximum configurations.

Notes about scaling values

Scaling Values for Junos OS Release 10.4
Scaling Values for Junos OS Release 10.3
Scaling Values for Junos OS Release 10.2
Scaling Values for Junos OS Release 10.1

To obtain the most current version of all Juniper Networks® technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/index.html.

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
■ Document or topic name
■ URL or page number
■ Software release version (if applicable)
The following notes are referred to from within individual Release tabs. Not all notes apply to all releases. The releases associated with each note are indicated in
parentheses at the end of the note.

1) This document generally refers to hardware modules by model number. In some cases, when the scaling value applies to all modules of a kind, the term family is use
rather than listing each module separately. See the MX Series 3D Universal Edge Router Line Card Guide for tables that correlate model numbers with descriptive nam
for the hardware.

Scaling values for MX80 routers were not available at the time of publication. (Applies to all releases.)

2) PPP connections are supported in a range of configurations. For example, an MX Series router supports 63,999 dynamic PPPoE interfaces per chassis when all
subscribers are configured on the same VLAN. In this example, 63,999 pp0 interfaces are configured under the same VLAN logical interface and the 1 remaining logica
interface is consumed for the single VLAN.

At the other extreme, when you configure each subscriber on a separate VLAN (using stacked VLANs) up to 32,000 dynamic PPPoE interfaces per chassis are
supported. In this case, each subscriber connection consumes 2 logical interfaces: one for the VLAN logical interface and one for the pp0 logical interface. (Applies to
Junos OS Releases 10.1, 10.2, 10.3, 10.4.)

3) On the MX-MPC1-3D-Q and MX-MPC2-3D-Q modules, the ingress and egress queues are hard partitioned. Of the total maximum queues, fifty percent are available
for ingress and fifty percent are available for egress. You cannot allocate the queues in any other proportions.

On the MX-MPC2-3D-EQ module, you can allocate all 512,000 of the total maximum queues for egress queuing, leaving 0 ingress queues. Alternatively, you can alloca
256,000 queues for egress and 256,000 queues for ingress. You cannot allocate more than 256,000 ingress queues, and you cannot allocate the queues in any other
proportions. (Applies to Junos OS Release 10.4.)

4) This value is the maximum number of subscriber interfaces per module that can be supported by queues dedicated to each interface. The actual number of subscribe
(up to the maximum) that can be serviced by dedicated queues depends upon how many queues you dedicate to each interface. (Applies to Junos OS Release 10.4.)

For example, if you dedicate 4 queues per subscriber interface on an MX-MPC1-3D-Q module, you can support 16,000 subscribers with dedicated queues:
(64,000 dedicated queues) / (4 queues per subscriber interface) = 16,000

If you dedicate 8 queues per subscriber interface on an MX-MPC1-3D-Q module, you can support only 8,000 subscribers with dedicated queues:
(64,000 dedicated queues) / (8 queues per subscriber interface) = 8,000
 Feature Notes MX240, MX480, and MX960 M120 and M320
Note 1
CoS queues per port on port-queuing modules
MX-MPC1-3D 8 –
MX-MPC2-3D 8 –

CoS total queues per VLAN-queuing module Note 3

MX-MPC1-3D-Q 128,000 –
MX-MPC2-3D-Q 256,000 –
MX-MPC2-3D-EQ 512,000 –

CoS ingress queues per VLAN-queuing module Note 3

MX-MPC1-3D-Q 64,000 –
MX-MPC2-3D-Q 128,000 –
MX-MPC2-3D-EQ 256,000 –
–
CoS egress queues per VLAN-queuing module Note 3
MX-MPC1-3D-Q 64,000 –
MX-MPC2-3D-Q 128,000 –
MX-MPC2-3D-EQ 512,000 –

CoS egress queues per MIC on VLAN-queuing modules Note 5

MX-MPC1-3D-Q 32,000 –
MX-MPC2-3D-Q 64,000 –
MX-MPC2-3D-EQ 128,000 –

CoS egress queues per port on VLAN-queuing modules Note 5

MX-MPC1-3D-Q 16,000 –
MX-MPC2-3D-Q 32,000 –
MX-MPC2-3D-EQ 64,000 –

CoS subscriber interfaces supported by

dedicated queues per VLAN-queuing module
4 queues per interface (8 queues per interface) Note 4
MX-MPC1-3D-Q 16,000 (8,000) –
MX-MPC2-3D-Q 32,000 (16,000) –
MX-MPC2-3D-EQ Note 6 64,000 (64,000) –
DHCP client bindings per chassis 120,000 –

DHCP subscriber VLANs (CVLANs) per chassis 64,000 –

DHCP subscriber VLANs (CVLANs) per module

MX Series Enhanced Queuing IP Services DPCs
(DPCE-R-Q-40GE-SFP and DPCE-R-Q-4XGE-XFP) 16,000 –
Trio MPC1 32,000 –
Trio MPC2 64,000 –

Dynamic profiles per chassis 2,000 2,000

L2TP LAC sessions per chassis Note 7 32,000 –

L2TP LAC sessions per line module Note 7

Trio MPC1 32,000 –
Trio MPC2 32,000 –

L2TP LAC tunnels per chassis Note 7 16,000 –

L2TP LAC tunnels per line module Note 7

Trio MPC1 16,000 –
Trio MPC2 16,000 –

L2TP LAC sessions per tunnel Note 7 32,000 –

PPPoE interfaces per chassis Note 2 64,000 16,000

PPPoE interfaces per module

IQ2/IQ2E PIC families – 4,000
Trio MPC1 16,000 –
Trio MPC2 32,000 –

PPPoE service name tables

PPPoE service name tables per chassis 32 32
Named service entries across all PPPoE service name
tables, per chassis (includes empty and any entries) 512 512
ACI/ARI pairs per service name table 8,000 8,000
PPPoE subscriber VLANs (CVLANs) per chassis 32,000 8,000

PPPoE subscriber VLANs (CVLANs) per module

IQ2/IQ2E PIC families – 2,000
Trio MPC1 16,000 –
Trio MPC2 32,000 –
 Feature Notes MX240, MX480, and MX960 M120 and M320
Note 1
DHCP client bindings per chassis 120,000 –

DHCP subscriber VLANs (CVLANs) per chassis 64,000 –

DHCP subscriber VLANs (CVLANs) per module

MX Series Enhanced Queuing IP Services DPCs
(DPCE-R-Q-40GE-SFP and DPCE-R-Q-4XGE-XFP) 16,000 –
Trio MPC1 32,000 –
Trio MPC2 64,000 –

Dynamic profiles per chassis 2,000 2,000

PPPoE interfaces per chassis Note 2 63,999 15,999

PPPoE interfaces per module

IQ2/IQ2E PIC families – 4,000
Trio MPC1 16,000 –
Trio MPC2 32,000 –

PPPoE service name tables

PPPoE service name tables per chassis 32 32
Named service entries across all PPPoE service name tables,
per chassis (includes empty and any entries) 512 512
ACI/ARI pairs per service name table 8,000 8,000

PPPoE subscriber VLANs (CVLANs) per chassis 32,000 8,000

PPPoE subscriber VLANs (CVLANs) per module

IQ2/IQ2E PIC families – 2,000
Trio MPC1 16,000 –
Trio MPC2 32,000 –
 Feature Notes MX240, MX480, and MX960
Note 1
DHCP client bindings per chassis 120,000

DHCP subscriber VLANs (CVLANs) per chassis 64,000

DHCP subscriber VLANs (CVLANs) per module

MX Series Enhanced Queuing IP Services DPCs
(DPCE-R-Q-40GE-SFP and DPCE-R-Q-4XGE-XFP) 16,000
Trio MPC1 32,000
Trio MPC2 64,000

Dynamic profiles per chassis 2,000

PPPoE interfaces per chassis Note 2 63,999

PPPoE interfaces per module

IQ2/IQ2E PIC families –
Trio MPC1 16,000
Trio MPC2 32,000

PPPoE service name tables

PPPoE service name tables per chassis 32
Named service entries across all PPPoE service name tables,
per chassis (includes empty and any entries) 512
ACI/ARI pairs per service name table 8,000

PPPoE subscriber VLANs (CVLANs) per chassis 32,000

PPPoE subscriber VLANs (CVLANs) per module

IQ2/IQ2E PIC families –
Trio MPC1 16,000
Trio MPC2 32,000
 Feature Notes MX240, MX480, and MX960 M120 and M320
Note 1
DHCP client bindings per chassis 120,000 –

DHCP subscriber VLANs (CVLANs) per chassis 64,000 –

DHCP subscriber VLANs (CVLANs) per module

MX Series Enhanced Queuing IP Services DPCs
(DPCE-R-Q-40GE-SFP and DPCE-R-Q-4XGE-XFP) 16,000 –
Trio MPC/MIC 64,000 –

Dynamic profiles per chassis 2,000 2,000

PPPoE dynamic interfaces per chassis 63,999 15,999

PPPoE dynamic interfaces per module

IQ2/IQ2E PIC families – 4,000
Trio MPC/MIC 32,000 –

PPP static interfaces per chassis 15,999 15,999

PPPoE subscriber VLANs (CVLANs) per chassis 32,000 8,000

PPPoE subscriber VLANs (CVLANs) per module

IQ2/IQ2E PIC families – 2,000
Trio MPC/MIC 32,000 –
 JUNOS Subscriber Management Scaling Values, Release 10.4

This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright © 1986-1997, Epilogue
Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public
domain.

This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto.

This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software
included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright © 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.

GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by
Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing protocol.
Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright © 1988, Regents of the
University of California. All rights reserved. Portions of the GateD software copyright © 1991, D. L. S. Associates.

This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc.

Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or
registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or
otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed
to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347,
6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

JUNOS® Software Subscriber Management Scaling Values

Release 10.4
Copyright © 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.

Revision History
October 2010—R1 JUNOS 10.4

The information in this document is current as of the date listed in the revision history.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS Software has no known time-related limitations through the year
2038. However, the NTP application is known to have some difficulty in the year 2036.