### JunosE 12.3.0 Release Notes

> ### ERX310, ERX7xx, and ERX14xx System Maximums

> The following tables provide system maximums for the ERX310, ERX7xx, and ERX14xx routers.

> #### General System Maximums

> Table 1 lists some general system maximums for the ERX routers.

> Table 1: General System Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> Fabric size | 10 Gbps | 5 or 10 Gbps | 10 Gbps | 40 Gbps
> Chassis per 7-foot rack | 14 | 6 | 3 | 3
> NTP clients | 1000 | 1000 | 1000 | 1000
> NTP servers | 300 | 300 | 300 | 300
> Sessions per chassis (simultaneous Telnet + FTP + SSH, in any combination) | 30 | 30 | 30 | 30
> Virtual routers per chassis | 1000 | 1000 | 1000 | 1000
> Virtual routers per line module | 1000 | 1000 | 1000 | 1000
> ICR Partitions per chassis | 640 | 640 | 640 | 640
> ICR Partitions per line module | 64 | 64 | 64 | 64

> #### Physical and Logical Density Maximums

> Table 2 lists physical and logical density maximums for the ERX routers. The following notes are referred to in Table 2:

> 1. Wire rate indicates the port density that supports maximum (wire-rate) performance. Oversubscribed indicates the port density possible when you are willing to accept less than wire-rate performance by oversubscribing the available fabric bandwidth. The ERX310 and ERX1440 routers do not support oversubscription; port densities for these models indicate wire-rate performance.
> 2. When you pair the GE-2 or GE-HDE line module with the GE-2 SFP I/O module on the ERX1440 router, you can terminate up to 24 Gigabit Ethernet interfaces. Slots 2 and 4 on the ERX1440 router support two Gigabit Ethernet interfaces at wire rate; the remaining 10 slots support one Gigabit Ethernet interface at wire rate. On the ERX310 router, all four ports (active and redundant) are at wire rate.

> For more information about bandwidth and line-rate considerations for the GE-2 line module or the GE-HDE line module and their corresponding I/O modules on E Series routers, see JunosE Physical Layer Configuration Guide, Chapter 5, Configuring Ethernet Interfaces.

> 3. When you pair the GE-HDE line module with the GE-8 I/O module on the ERX1440 router, you can terminate up to 96 Gigabit Ethernet interfaces. Slots 2 and 4 on the ERX1440 router support two Gigabit Ethernet interfaces at wire rate; the remaining 10 slots support one Gigabit Ethernet interface at wire rate. On the ERX310 router, only two Gigabit Ethernet interfaces per slot are at wire rate; therefore, only four Gigabit Ethernet interfaces are at wire rate for the entire router.

> For more information about bandwidth and line-rate considerations for the GE-HDE line module and the GE-8 I/O module on E Series routers, see JunosE Physical Layer Configuration Guide, Chapter 5, Configuring Ethernet Interfaces.

> 4. The OC3/STM-1 GE/FE line module and OC3-2 GE APS I/O module combination does not support line rate for Gigabit Ethernet interfaces.

> Table 2: Physical and Logical Density Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> Physical density wire rate/oversubscribed (See Note 1 on page 53.) |
> Channelized OC3 ports per chassis (cOC3 STM1 FO I/O modules) | 8 | 16/20 | 32/48 | 48
> Channelized OC12 ports per chassis (cOC12 STM4 FO I/O modules) | 2 | 4/5 | 4/12 | 12
> Channelized T3 ports per chassis (CT3/T3 12 I/O modules) | 24 | 48/60 | 96/144 | 144
> E3 (unchannelized) ports per chassis (CT3/T3 12 I/O modules) | 24 | 48/60 | 96/144 | 144
> Fast Ethernet (10/100) ports per chassis (FE-8 I/O and FE-8 SFP I/O modules) | 16 | 32/40 | 32/96 | 96
> Gigabit Ethernet ports per chassis (GE I/O modules) | 2 | 4/5 | 4/12 | 12
> Gigabit Ethernet ports per chassis (GE-2 SFP I/O modules) (See Note 2 on page 53.) | 4 | – | – | 14/24
> Gigabit Ethernet ports per chassis (GE-8 I/O modules) (See Note 3 on page 53.) | 4/16 | – | – | 14/96
> Gigabit Ethernet ports per chassis (OC3-2 GE APS I/O module) (See Note 4 on page 53.) | 2 | 4/5 | 4/12 | 12
> OC3/STM-1 ATM ports per chassis (OC3-4 I/O modules) | 8 | 16/20 | 32/48 | 48
> OC3/STM-1 ATM ports per chassis (OC3-2 GE APS I/O module) | 4 | 10 | 24 | 24
> OC3/STM-1 POS ports per chassis (OC3-4 I/O modules) | 8 | 16/20 | 16/48 | 48
> OC12/STM-4 ATM ports per chassis (OC12 STM4 I/O modules) | 2 | 4/5 | 8/12 | 12
> OC12/STM-4 POS ports per chassis (OC12 STM4 I/O modules) | 2 | 4/5 | 4/12 | 12
> OC48/STM16 POS ports per chassis (OC48 FRAME I/O modules); ERX1440 router only | – | – | – | 2
> T3 (unchannelized) ports per chassis (4xDS3 ATM I/O modules) | 8 | 16/20 | 32/48 | 48
> T3 (unchannelized) ports per chassis (CT3/T3 12 I/O modules) | 24 | 48/60 | 96/144 | 144
> Logical density per chassis |  |  |  |
> Logical E1s per chassis | 504 | 1260 | 3024 | 3024
> Logical E3s per chassis | 24 | 60 | 144 | 144
> Logical fractional E1s (DS0) per chassis | 4000 | 10,000 | 24,000 | 24,000
> Logical fractional T1s (DS0) per chassis | 4000 | 10,000 | 24,000 | 24,000
> Logical OC3/STM1 per chassis | 8 | 20 | 48 | 48
> Logical OC12/STM4 per chassis | 2 | 5 | 12 | 12
> Logical OC48/STM16 per chassis (ERX1440 router only) | – | – | – | 2
> Logical T1s per chassis | 672 | 1680 | 4032 | 4032
> Logical T3s per chassis | 24 | 60 | 144 | 144
> Logical density per module combination (specified line module and all supported I/O modules) |  |  |  |
> Logical E1s per cOCx/STMx F0 line module | 252 63 per OC3/STM1 | 252 63 per OC3/STM1 | 252 63 per OC3/STM1 | 252 63 per OC3/STM1
> Logical E3s per COCX-F3 line module | 12 | 12 | 12 | 12
> Logical fractional E1s (DS0) per cOCx/STMx F0 line module | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1
> Logical fractional T1s (DS0) per cOCx/STMx F0 line module | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1 | 2000 500 per OC3/STM1
> Logical fractional T1s (DS0) per CT3/T3-F0 line module | 1992 166 per T3 | 1992 166 per T3 | 1992 166 per T3 | 1992 166 per T3
> Logical fractional T3s (DS3) per COCX-F3 line module | 12 | 12 | 12 | 12
> Logical T1s per cOCx/STMx F0 line module | 336 84 per OC3/STM1 | 336 84 per OC3/STM1 | 336 84 per OC3/STM1 | 336 84 per OC3/STM1
> Logical T1s per CT3/T3-F0 line module | 336 28 per T3 | 336 28 per T3 | 336 28 per T3 | 336 28 per T3
> Logical T3s per COCX-F3 line module | 12 | 12 | 12 | 12
> Logical T3s per cOCx/STMx F0 line module | 12 3 per OC3/STM1 | 12 3 per OC3/STM1 | 12 3 per OC3/STM1 | 12 3 per OC3/STM1
> Logical T3s per CT3/T3-F0 | 12 | 12 | 12 | 12
> Logical T3s per OCx/STMx/DS3-ATM line module with 4xDS3 ATM I/O module | 4 | 4 | 4 | 4

> #### Link Layer Maximums

> Table 3 lists link layer maximums for the ERX routers. The following notes are referred to in Table 3:

> 1. The ERX1440 router supports a maximum of 48,000 interface columns of all types combined. You can use either all dynamic interfaces or a combination of dynamic and static interfaces to achieve this maximum. For bridged Ethernet, IP network, and PPP interfaces, the ERX1440 router supports a maximum of 32,000 static major interfaces. Although the ERX1440 router supports a maximum of 48,000 static major interfaces for PPPoE, the PPPoE static limit is enforced at the subinterface level, which has a limit of 32,000.

> The ERX705, ERX710, and ERX1410 routers support a maximum of 32,000 interfaces of all types combined; the ERX310 router supports a maximum of 16,000 interfaces of all types combined. For these routers, the interfaces can be any combination of dynamic or static.

> The JunosE Software supports up to 10,000 PPP interfaces with EAP authentication negotiation configured. Performance and scalability is unchanged when EAP is not configured.

> 2. The total maximum number of Ethernet subinterfaces that can be active at any one time on an ERX310 router, an ERX7xx router, or an ERX14xx router is limited by the number of slots per chassis. Of this total, you can configure all single-tagged VLAN subinterfaces, all double-tagged S-VLAN subinterfaces, or a combination of both VLAN subinterfaces and S-VLAN subinterfaces to achieve this maximum.

> Table 3: Link Layer Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> ARP entries per line module |  |  |  |
> Dynamic ARP entries | 32,768 | 32,768 | 32,768 | 32,768
> Static ARP entries | 32,768 | 32,768 | 32,768 | 32,768
> Total ARP entries | 32,768 | 32,768 | 32,768 | 32,768
> ATM bulk configuration VC ranges per chassis | 300 | 300 | 300 | 300
> ATM bulk configuration VC ranges per line module | 300 | 300 | 300 | 300
> ATM bulk configuration total VCs per chassis | 64,000 | 160,000 | 384,000 | 384,000
> ATM bulk configuration total VCs per line module |  |  |  |
> OCx/STMx/DS3-ATM | 32,000 | 32,000 | 32,000 | 32,000
> OC3/STM1 GE/FE | 32,000 | 32,000 | 32,000 | 32,000
> ATM bulk configuration overriding profile assignments per chassis | 100 | 100 | 100 | 100
> ATM VCs per chassis (active/configured) | 16,000/32,000 | 32,000/64,000 | 32,000/64,000 | 48,000/96,000
> ATM VCs per line module |  |  |  |
> OCx/STMx/DS3-ATM (active/configured) | 8000/16,000 | 8000/16,000 | 8000/16,000 | 8000/16,000
> OC3/STM1 GE/FE (active/configured) | 8000/16,000 | 8000/16,000 | 8000/16,000 | 8000/16,000
> ATM VCs per port |  |  |  |
> OCx/STMx/DS3-ATM (active/configured) | 8000/16,000 | 8000/16,000 | 8000/16,000 | 8000/16,000
> OC3/STM1 GE/FE (active/configured) | 8000/16,000 | 8000/16,000 | 8000/16,000 | 8000/16,000
> ATM VC classes per chassis | 100 | 100 | 100 | 100
> ATM VP/VC addresses per line module |  |  |  |
> OCx/STMx/DS3-ATM | 20-bit | 20-bit | 20-bit | 20-bit
> OC3/STM1 GE/FE | 20-bit | 20-bit | 20-bit | 20-bit
> ATM VP tunnels per port, all supported modules | 256 | 256 | 256 | 256
> Bridged Ethernet interfaces per chassis (See Note 1 on page 56.) | 16,000 | 32,000 | 32,000 | 48,000
> Bridged Ethernet interfaces per line module |  |  |  |
> OCx/STMx/DS3-ATM | 8192 | 8192 | 8192 | 8192
> OC3/STM-1 GE/FE | 8192 | 8192 | 8192 | 8192
> Dynamic interfaces |  |  |  |
> Active autosensed dynamic interface columns per chassis over static or dynamic (bulk) ATM1483 subinterfaces | 16,000 | 32,000 | 32,000 | 48,000
> Ethernet 802.3ad Link Aggregation |  |  |  |
> Links per LAG (bundle) | 8 | 8 | 8 | 8
> LAGs (bundles) per chassis | 64 | 64 | 64 | 64
> Ethernet S-VLANs per chassis (See Note 2 on page 56.) | 32,768 | 81,920 | 96,000 | 96,000
> Ethernet S-VLANs per I/O module |  |  |  |
> FE-8 I/O and FE-8 SFP I/O | 16,384 | 16,384 | 16,384 | 16,384
> GE I/O | 16,384 | 16,384 | 16,384 | 16,384
> GE-2 SFP I/O | 16,384 | – | – | 16,384
> GE-8 I/O | 16,384 | – | – | 16,384
> OC3-2 GE APS I/O | 16,384 | 16,384 | 16,384 | 16,384
> Ethernet VLANs per chassis (See Note 2 on page 56.) | 32,768 | 81,920 | 96,000 | 96,000
> Ethernet VLANs per I/O module (no more than 4096 VLANs per port)
> FE-8 I/O and FE-8 SFP I/O | 8192 | 8192 | 8192 | 8192
> GE I/O | 4096 | 4096 | 4096 | 4096
> GE-2 SFP I/O | 8192 | – | – | 8192
> GE-8 I/O | 16,384 | – | – | 16,384
> OC3-2 GE APS I/O | 4096 | 4096 | 4096 | 4096
> Ethernet VLAN bulk configuration VLAN ranges per chassis | 300 | 300 | 300 | 300
> Ethernet VLAN bulk configuration VLAN ranges per line module | 300 | 300 | 300 | 300
> Ethernet VLAN overriding profile assignments per chassis | 200 | 200 | 200 | 200
> Ethernet VRRP VRIDs per line module | 800 | 800 | 800 | 800
> Frame Relay virtual circuits per chassis | 2000 | 5000 | 12,000 | 12,000
> Frame Relay virtual circuits per line module |  |  |  |
> COCX-F3 | 1000 | 1000 | 1000 | 1000
> cOCx/STMx F0 | 1000 | 1000 | 1000 | 1000
> OC48 (ERX1440 router only) | – | – | – | 1000
> Frame Relay virtual circuits per port |  |  |  |
> COCX-F3 | 1000 | 1000 | 1000 | 1000
> cOCx/STMx F0 | 1000 | 1000 | 1000 | 1000
> OC48 (ERX1440 router only) | – | – | – | 1000
> HDLC interfaces per chassis | 4000 | 10,000 | 24,000 | 24,000
> HDLC interfaces per line module |  |  |  |
> COCX-F3 | 12 | 12 | 12 | 12
> cOCx/STMx F0 | 2000 | 2000 | 2000 | 2000
> CT3/T3 F0 | 1992 | 1992 | 1992 | 1992
> OCx/STMx/DS-3 ATM | 8000 | 8000 | 8000 | 8000
> OCx/STMx POS | 4 | 4 | 4 | 4
> OC48 (ERX1440 router only) | – | – | – | 1
> MLFR bundles per chassis | 5000 | 5000 | 5000 | 5000
> MLFR bundles per line module | Bundles per line module are limited only by the availability of interface columns on the module. Because a bundle requires at least one interface column, the number of bundles cannot exceed the number of interface columns.
> MLPPP bundles per chassis | 12,000 | 12,000 | 12,000 | 12,000
> MLPPP bundles per line module | The maximum number of MLPPP bundles supported per line module is the lesser of the maximum number of MLPPP bundles supported per chassis or of the maximum number of interfaces supported on the line module. For more information, see the JunosE Link Layer Configuration Guide.
> PPP interfaces per chassis (See Note 1 on page 56.) | 16,000 | 32,000 | 32,000 | 48,000
> PPP interfaces per line module |  |  |  |
> COCX-F3 | 12 | 12 | 12 | 12
> cOCx/STMx FO | 2000 | 2000 | 2000 | 2000
> GE/FE | 8000 | 8000 | 8000 | 8000
> GE-2 | 8000 | – | – | 8000
> GE-HDE | 8000 | – | – | 8000
> OCx/STMx/DS-3 ATM | 8000 | 8000 | 8000 | 8000
> OC3/STM-1 GE/FE | 8000 | 8000 | 8000 | 8000
> OCx/STMx POS | 4 | 4 | 4 | 4
> OC48 (ERX1440 router only) | – | – | – | 1
> PPP packet logging |  |  |  |
> Aggregate dynamic and static PPP interfaces for which you can log PPP packets per chassis | 32 | 32 | 32 | 32
> PPPoE service name tables |  |  |  |
> PPPoE service name tables per chassis | 16 | 16 | 16 | 16
> Service name tags per PPPoE service name table (including one empty service name tag) | 17 | 17 | 17 | 17
> PPPoE subinterfaces |  |  |  |
> Subinterfaces per chassis (See Note 1 on page 56.) | 16,000 | 32,000 | 32,000 | 48,000
> Subinterfaces per GE/FE line module | 8000 | 8000 | 8000 | 8000
> Subinterfaces per GE-2 line module | 8000 | – | – | 8000
> Subinterfaces per GE-HDE line module | 8000 | – | – | 8000
> Subinterfaces per OCx/STMx/DS-3 ATM line module | 8000 | 8000 | 8000 | 8000
> Subinterfaces per OC3/STM-1 GE/FE line module | 8000 | 8000 | 8000 | 8000
> Transparent bridging and VPLS |  |  |  |
> Bridge groups or VPLS instances per chassis | 1024 | 1024 | 1024 | 1024
> Bridge interfaces per line module in bridge groups or VPLS instances | 8000 | 8000 | 8000 | 8000
> Bridge interfaces per chassis in bridge groups or VPLS instances | 16,000 | 32,000 | 32,000 | 32,000
> Learned MAC address entries combined for all bridge groups and VPLS instances on a chassis | 64,000 | 64,000 | 64,000 | 64,000

> #### Routing Protocol Maximums

> Table 4 lists routing protocol maximums for the ERX routers. The following notes are referred to in Table 4:

> 1. The total set of FTEs can be shared by interfaces, next hops, ECMP sets, VRs, and VRFs. Next-hop FTEs identify the next hop on multiaccess media, such as ATM multipoint, Ethernet, or bridged Ethernet. Each VR or VRF consumes three entries. Each interface, next hop, and ECMP set consumes a single entry. One FTE is reserved for internal use, and the system software limits the number of FTEs used by interfaces to a maximum of 32,000. The remaining FTEs can be shared across the other types.
> 2. The ERX1440 router supports a maximum of 48,000 interfaces of all types combined. You can use either all dynamic interfaces or a combination of dynamic and static interfaces to achieve this maximum. The ERX1440 router supports a maximum of 32,000 static PPP/PPPoE interfaces and a maximum of 36,500 static IP network interfaces. Bridged Ethernet does not enforce a limit so IP interfaces created on Bridged Ethernet can scale to the IP maximum of 36,500.

> The ERX705, ERX710, and ERX1410 routers support a maximum of 32,000 IP network interfaces; the ERX310 router supports a maximum of 16,000 IP network interfaces. For all these models, the interfaces can be any combination of dynamic or static.

> 3. These values are subject to limitations on available SRP module memory, which varies according to your router configuration.
> 4. Depending on your configuration, the router may support more routing table entries or fewer routing table entries than this value. In any case, you can choose to limit the number of routes that can be added to the routing table on a per-VR or per-VRF basis by means of the maximum routes command.
> 5. The maximum number of ANCP adjacencies can be scaled over a maximum of 100 virtual routers. Fewer ANCP adjacencies can be scaled in configurations with more than 100 virtual routers.
> 6. This maximum is not valid for Frame Relay. The Frame Relay maximum is 1000 circuits over MPLS per line module, because only 1000 Frame Relay DLCIs are permitted per line module.
> 7. On the ERX1440 router, you can achieve 32,767 total Martini circuits over ATM or Ethernet interfaces. For all routers, the total Martini can be any combination of external inter-router circuits and internal circuits (local cross-connects).
> 8. There is no per-VR limit; all multicast routes can be on a single VR or present across multiple VRs.
> 9. The maximum number of interfaces can be achieved by any combination; for example, two streams each being replicated to 32,768 interfaces; 16,384 streams each being replicated four times; or any other combination.
> 10. Dynamic values represent typical limits that vary depending on configuration details and actual dynamic behavior. For dynamic values only, multiple server modules (SMs) in a chassis can improve the values as long as the multiple server modules are online and the number of virtual routers configured with NAT is greater than or equal to the number of server modules. If a server module fails, the load is redistributed to the remaining server modules, with a consequent reduction in aggregate capacity.
> 11. Static and dynamic translations occupy the same table; therefore, the number of static translation entries present in the table reduces the room for dynamic entries.

> Table 4: Routing Protocol Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> BFD |  |  |  |
> Sessions per line module | 50 | 50 | 50 | 50
> ECMP maximum paths to a destination |  |  |  |
> BGP, IS-IS, MPLS, OSPF, RIP | 16 | 16 | 16 | 16
> IPv4 forwarding table entries per chassis (See Note 1 on page 61.) | 1,048,576 | 1,048,576 | 1,048,576 | 1,048,576
> IP network interfaces (IPv4 and IPv6) |  |  |  |
> Per chassis (See Note 2 on page 61.) | 32,000 | 32,000 | 32,000 | 48,000
> Per line module | 16,383 | 16,383 | 16,383 | 16,383
> IPv4 routing protocol scaling and peering densities (See Note 3 on page 61.) |  |  |  |
> Routing table entries (See Note 4 on page 61.) | 500,000 | 500,000 | 500,000 | 500,000
> ANCP Adjacency Scaling (See Note 5 on page 61.) | 5000 | 5000 | 5000 | 5000
> BGP-4 peering sessions | 1000 | 1000 | 1000 | 1000
> BGP-4 routes (NLRI) | 1,500,000 | 1,500,000 | 1,500,000 | 1,500,000
> IP next hops (egress FECs) | 1,000,000 | 1,000,000 | 1,000,000 | 1,000,000
> MPLS next hops (egress FECs) | 500,000 | 500,000 | 500,000 | 500,000
> MPLS forwarding entries | 64,000 | 64,000 | 64,000 | 64,000
> IS-IS adjacencies | 150 | 150 | 150 | 150
> IS-IS routes | 20,000 | 20,000 | 20,000 | 20,000
> MPLS LDP LSPs | 10,000 | 10,000 | 10,000 | 10,000
> MPLS RSVP-TE LSPs | 10,000 | 10,000 | 10,000 | 10,000
> OSPF adjacencies | 1000 | 1000 | 1000 | 1000
> OSPF routes | 25,000 | 25,000 | 25,000 | 25,000
> IPv6 routing table entries (See Note 3 on page 61.) | 50,000 | 50,000 | 50,000 | 50,000
> J-Flow statistics |  |  |  |
> J-Flow–enabled VRs and VRFs, in any combination | 16 | 16 | 16 | 16
> Sampled interfaces per VR or VRF | 32 | 32 | 32 | 32
> Total sampled Interfaces per chassis | 512 | 512 | 512 | 512
> Martini circuits for layer 2 services over MPLS |  |  |  |
> Total Martini circuits per line module (See Note 6 on page 61.) | 8000 | 8000 | 8000 | 8000
> Total Martini circuits per chassis (See Note 7 on page 61.) | 16,000 | 16,000 | 16,000 | 32,767
> External Martini circuits per chassis | 16,000 | 16,000 | 16,000 | 32,767
> Internal Martini circuits (local cross-connects) per chassis | 16,000 | 16,000 | 16,000 | 32,767
> Mobile IP bindings per chassis | – | – | – | 48,000
> Multicast routes (IPv4 and IPv6) |  |  |  |
> Forwarding entries [(S,G) pairs] per chassis (See Note 8 on page 61.) | 16,384 | 16,384 | 16,384 | 16,384
> Outgoing interfaces per chassis (See Note 9 on page 61.) | 65,536 | 65,536 | 65,536 | 65,536
> Network Address Translation (NAT) |  |  |  |
> Static translations (simple or extended) per chassis | 96,000 | 96,000 | 96,000 | 96,000
> Dynamic simple translations (NAT) per SM (See Notes 10 and 11 on page 62.) | 400,000 | 400,000 | 400,000 | 400,000
> Dynamic extended translations (NAPT) per SM (See Notes 10 and 11 on page 62.) | 200,000 | 200,000 | 200,000 | 200,000
> Response Time Reporter simultaneous operations per VR | 500 | 500 | 500 | 500
> VRRP VRIDs per line module | See Ethernet VRRP VRIDs per line module on page 58.

> #### Policy and QoS Maximums

> Table 5 lists policy and QoS maximums for the ERX routers. The following notes are referred to in Table 5:

> 1. The OC48 line module supports only 131,071 entries. The GE-2 and GE-HDE line modules support only 65,535 entries.
> 2. For line modules other than the GE-2, GE-HDE, and OC48/STM16 line modules, the router supports two sizes of policies: 8127 policies, each with a maximum of 32 classifiers, and 16,255 policies, each with a maximum of 16 classifiers. A combination of the two sizes of policies is also supported, in which case the total number of policies is between 8127 and 16,255, depending on the actual configuration.
> 3. The GE-2, GE-HDE, and OC48/STM16 line modules support CAM classifiers instead of hardware policy assignments. For most configurations, each classifier entry in a policy consumes one CAM entry. However, a policy that has only the default classifier consumes no CAM resources. Policies that use CAM hardware classifiers consume one interface attachment resource, regardless of the number of classifier entries in a policy.
> 4. For each rule that is sent from the SRC server using COPS messages to the SRC client, which is a router running JunosE Software, an entry is created in the policy table of the SRC client. A portion of the memory on the SRC client is needed to hold these policy rule entries that are transmitted to the SRC client for enforcing the policy decisions that are sent from the SRC server. The maximum number of memory blocks that is allocated to the SRC client functioning on the router for the policy rules that are sent from the SRC server is 256,000.

> Table 5: Policy and QoS Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> QoS queues per line module | 49,000 | 49,000 | 49,000 | 49,000
> QoS profiles configurable per chassis | 1000 | 1000 | 1000 | 1000
> QoS profile attachments per chassis | 96,000 | 96,000 | 96,000 | 96,000
> QoS profile attachments per line module | 16,000 | 16,000 | 16,000 | 16,000
> QoS shapers per line module | 64,000 | 64,000 | 64,000 | 64,000
> Classification rules per policy | 512 | 512 | 512 | 512
> Policy classification (CLACL) entries per line module (See Note 1 on page 64.) | 256,000 | 256,000 | 256,000 | 256,000
> Policy rules supported by the SRC client (See Note 4 on page 64.) | 256,000 | 256,000 | 256,000 | 256,000
> Unique hardware policy assignments per line module for modules other than the GE-2, GE-HDE, and OC48/STM16 (See Note 2 on page 64.) | 8127/16,255 | 8127/16,255 | 8127/16,255 | 8127/16,255
> CAM entries (See Note 3 on page 64.) |  |  |  |
> GE-2 | 64,000 | – | – | 64,000
> GE-HDE | 64,000 | – | – | 64,000
> OC48/STM16 | – | – | – | 128,000
> Policy egress interface attachments per line module |  |  |  |
> Combined IP and IPv6 interface attachments | 8191 | 8191 | 8191 | 8191
> Combined ATM, Frame Relay, GRE, L2TP (LNS only), MPLS, and VLAN interface attachments | 8191 | 8191 | 8191 | 8191
> Policy ingress interface attachments per line module |  |  |  |
> Combined IP and IPv6 interface attachments on GE-2, GE-HDE, and OC-48/STM16 line modules | 16,383 | – | – | 16,383
> Combined IP and IPv6 interface attachments on all other line modules | 16,000 | 16,000 | 16,000 | 16,000
> Combined ATM, Frame Relay, GRE, L2TP (LNS only), MPLS, and VLAN interface attachments | 8191 | 8191 | 8191 | 8191
> Rate limiters |  |  |  |
> Egress per line module | 24,575 | 24,575 | 24,575 | 24,575
> Ingress per line module | 24,575 | 24,575 | 24,575 | 24,575
> Policy statistics blocks |  |  |  |
> Egress per line module | 256,000 | 256,000 | 256,000 | 256,000
> Ingress per line module | 256,000 | 256,000 | 256,000 | 256,000
> Parent groups per line module |  |  |  |
> GE-2, GE-HDE, and OC3/OC12 ATM line modules (Egress and Ingress) | 24,575 | 24,575 | 24,575 | 24,575
> All other line modules (Egress and Ingress) | 8191 | 8191 | 8191 | 8191
> Software lookup blocks |  |  |  |
> Per line module | 16,383 | 16,383 | 16,383 | 16,383
> Secure policies (for packet mirroring) |  |  |  |
> Per line module | 1022 | 1022 | 1022 | 1022
> Per chassis | 2400 | 2400 | 2400 | 2400

> #### Tunneling Maximums

> Table 6 lists tunneling maximums for the ERX routers. The following notes are referred to in Table 6:

> 1. The SM supports any combination of DVMRP, GRE, and L2TP tunnels up to a maximum of 8000 tunnels; however, no more than 4000 tunnels can be DVMRP or GRE tunnels in any combination. The ISM supports any combination of DVMRP, GRE, and L2TP tunnels over IPSec, up to a maximum of 5000 tunnels; however, no more than 4000 tunnels can be DVMRP or GRE tunnels.
> 2. You can have no more than 8000 L2TP/IPSec sessions per chassis.
> 3. For more information about supported L2TP sessions and tunnels, see JunosE Broadband Access Configuration Guide, Chapter 12, L2TP Overview.

> Table 6: Tunneling Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> DVMRP (IP-in-IP) tunnels per chassis | 4000 | 4000 | 4000 | 4000
> DVMRP (IP-in-IP) tunnels per line module (See Note 1 on page 67.) |  |  |  |
> GE-2 with shared tunnel-server ports provisioned | 4000 | – | – | 4000
> GE-HDE with shared tunnel-server ports provisioned | 4000 | – | – | 4000
> IPSec Service Module (DVMRP/IPSec tunnels) | 4000 | 4000 | 4000 | 4000
> Service Module (SM) | 4000 | 4000 | 4000 | 4000
> GRE tunnels per chassis | 4000 | 4000 | 4000 | 4000
> GRE tunnels per line module (See Note 1 on page 67.) |  |  |  |
> GE-2 with shared tunnel-server ports provisioned | 4000 | – | – | 4000
> GE-HDE with shared tunnel-server ports provisioned | 4000 | – | – | 4000
> IPSec Service Module (GRE/IPSec tunnels) | 4000 | 4000 | 4000 | 4000
> Service Module (SM) | 4000 | 4000 | 4000 | 4000
> IPSec manual secure tunnels per chassis | 256 | 256 | 256 | 256
> IPSec transform sets per chassis | 1000 | 1000 | 1000 | 1000
> IPSec transforms per transform set | 6 | 6 | 6 | 6
> IPSec tunnels per chassis | 10,000 | 10,000 | 10,000 | 20,000
> IPSec tunnels per IPSec Service Module | 5000 | 5000 | 5000 | 5000
> L2TP sessions per chassis (See Notes 2 and 3 on page 67.) | 16,000 | 16,000 | 16,000 | 32,000
> L2TP sessions per line module (See Notes 1 and 3 on page 67.) |  |  |  |
> GE-2 with shared tunnel-server ports provisioned | 8000 | – | – | 8000
> GE-HDE with shared tunnel-server ports provisioned | 8000 | – | – | 8000
> IPSec Service Module (ISM; L2TP/IPSec sessions) | 5000 | 5000 | 5000 | 5000
> Service Module (SM) | 16,000 | 16,000 | 16,000 | 16,000
> L2TP tunnels per chassis | 8000 | 8000 | 8000 | 8000
> L2TP tunnels per line module (See Notes 1 and 3 on page 67.) |  |  |  |
> GE-2 with shared tunnel-server ports provisioned | 8000 | – | – | 8000
> GE-HDE with shared tunnel-server ports provisioned | 8000 | – | – | 8000
> IPSec Service Module (L2TP/IPSec tunnels) | 5000 | 5000 | 5000 | 5000
> Service Module | 8000 | 8000 | 8000 | 8000

> #### Subscriber Management Maximums

> Table 7 lists subscriber management maximums for the ERX routers. The following notes are referred to in Table 7:

> 1. DHCP relay proxy maintains a list of active DHCP clients up to a maximum of 100,000 clients per chassis for all virtual routers. DHCP relay does not maintain a list of DHCP clients.

> DHCP relay proxy is notified of DHCP client deletions and subsequently deletes the client's host routes. In contrast, DHCP relay is not notified of DHCP client deletions, so the host routes for deleted clients remain in DHCP relay until you permanently delete them with the set dhcp relay discard-access-routes command. A maximum of 100,000 host routes for DHCP clients can be stored for all DHCP relay and DHCP relay proxy instances (that is, for all virtual routers).

> 2. The ERX1440 router supports a maximum of 48,000 interface columns of all types combined. You can use either all dynamic interfaces or a combination of dynamic and static interfaces to achieve this maximum. For bridged Ethernet, IP network, and PPP interfaces, the ERX1440 router supports a maximum of 32,000 static major interfaces. Although the ERX1440 router supports a maximum of 48,000 static major interfaces for PPPoE, the PPPoE static limit is enforced at the subinterface level, which has a limit of 32,000.

> The ERX705, ERX710, and ERX1410 routers support a maximum of 32,000 interfaces of all types combined; the ERX310 router supports a maximum of 16,000 interfaces of all types combined. For these routers, the interfaces can be any combination of dynamic or static.

> The JunosE Software supports up to 10,000 PPP interfaces with EAP authentication negotiation configured. Performance and scalability is unchanged when EAP is not configured.

> 3. For DHCPv6 local server, up to 32,000 subscribers and clients are supported on PPP/ATM and PPPoE/ATM with dynamic interfaces. Interface flapping tests have been qualified for 8000 subscribers and interfaces.

> Table 7: Subscriber Management Maximums
> Feature | ERX310 | ERX705 and ERX710 | ERX1410 | ERX1440
> --- | --- | --- | --- | ---
> DHCP external server clients (per chassis for all virtual routers; and per virtual router) (See Note 1 on page 69.) | 100,000 | 100,000 | 100,000 | 100,000
> DHCP local server (See Note 2 on page 69.) |  |  |  |
> Client bindings per chassis | 96,000 | 96,000 | 96,000 | 96,000
> Client interfaces per chassis | 16,000 | 32,000 | 32,000 | 48,000
> Local address pools per virtual router | 4000 | 4000 | 4000 | 4000
> IP addresses per local address pool | 32,000 | 32,000 | 32,000 | 32,000
> DHCPv6 local server |  |  |  |
> Clients (See Note 3 on page 69.) | 32,000 | 32,000 | 32,000 | 32,000
> DHCP relay and relay proxy client (See Notes 1 and 2 on page 69.) |  |  |  |
> DHCP client host routes for DHCP relay and DHCP relay proxy combined (per chassis for all virtual routers; and per virtual router) | 100,000 | 100,000 | 100,000 | 100,000
> DHCP relay proxy clients (per chassis for all virtual routers; and per virtual router) | 100,000 | 100,000 | 100,000 | 100,000
> Interfaces (per chassis for all virtual routers; and per virtual router) | 16,000 | 32,000 | 32,000 | 48,000
> Local authentication server |  |  |  |
> Local user databases per chassis | 100 | 100 | 100 | 100
> Users per local user database | 100 | 100 | 100 | 100
> Users for all local user databases | 100 | 100 | 100 | 100
> RADIUS requests |  |  |  |
> Concurrent RADIUS authentication requests | 4000 | 4000 | 4000 | 32,000
> Concurrent RADIUS accounting requests | 4000 | 4000 | 4000 | 96,000
> RADIUS route-download server downloaded routes per chassis | 32,000 | 32,000 | 32,000 | 32,000
> Service Manager |  |  |  |
> Service definitions | 2048 | 2048 | 2048 | 2048
> Service sessions (active) | 131,072 | 131,072 | 131,072 | 131,072
> Active subscriber sessions | 16,000 | 32,000 | 32,000 | 48,000
> SRC Software and SDX Software |  |  |  |
> COPS client instances | 200 | 200 | 200 | 200
> SRC clients | 200 | 200 | 200 | 200
> SRC interfaces | 16,000 | 32,000 | 32,000 | 48,000
> Subscriber interfaces (See Note 2 on page 69.) |  |  |  |
> Dynamic subscriber interfaces per chassis' | 16,000 | 32,000 | 32,000 | 48,000
> Dynamic subscriber interfaces per line module | 8000 | 8000 | 8000 | 8000
> Static subscriber interfaces per chassis | 16,000 | 32,000 | 32,000 | 48,000
> Static subscriber interfaces per line module | 8000 | 8000 | 8000 | 8000

> | Informational Note: The system maximum and line card maximum values mentioned in the tables are for single dimension scaling only. We recommend that you test scenarios which require scaling of multiple features to the maximum values concurrently, before deploying. For example, on ERX1440 routers we support 48,000 PPP subscribers and 1, 500, 000 BGP 4 routes (NLRI). These values are independent of each other. We recommend that you test if the system can concurrently support 48,000 PPP subscribers and 1,500,000 BGP 4 routes (NLRI), before deploying.

Copyright © 2011, Juniper Networks, Inc. Report An Error