1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE SOFTWARE 10.3.2 - S 9-29-2010
  6. Release note

Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010 Release Note

For e series broadband services routers
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
JunosE
Software
™
for E Series
Broadband Services Routers
™

Release Notes

Release 10.3.2
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Published: 2010-09-29

Advertisement

Table of Contents
loading

Related Manuals for Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010

Summary of Contents for Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010

  • Page 1: Release Notes

    JunosE Software ™ for E Series Broadband Services Routers ™ Release Notes Release 10.3.2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-09-29...
  • Page 2 SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use...
  • Page 3 The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any commercial network access services. The foregoing license is not transferable or assignable by Customer.
  • Page 4 Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html.

  • Page 5: Table Of Contents

    Table of Contents Release 10.3.2 Release Installation ..................1 Upgrading to Release 5.3.0 or a Higher-Numbered Release ....... 1 Upgrading from Release 5.1.1 or Lower-Numbered Releases to Release 6.x.x or Higher-Numbered Releases ........2 Moving Line Modules Between Releases ............ 2 SRP Module Memory Requirements ............
  • Page 6 JunosE 10.3.2 Release Notes GRE ......................21 Hardware ....................21 HDLC....................... 22 IP......................22 IPSec ....................... 24 IS-IS ......................24 L2TP ......................25 Line Module Redundancy ................ 25 MLPPP..................... 26 MPLS ....................... 26 Multicast....................26 Packet Mirroring ..................27 Policy Management ................. 27 PPP......................
  • Page 7 Table of Contents SONET..................... 49 SRC Software and SDX Software ............. 50 Stateful SRP Switchover (High Availability) and IP Tunnels ...... 50 Subscriber Management ................51 System ....................52 System Logging ..................52 TCP ......................52 Unified ISSU .................... 52 Resolved Known Problems ................
  • Page 8 JunosE 10.3.2 Release Notes viii Table of Contents...

  • Page 9: Release 10.3.2

    Complete procedures for installing the system software are available in JunosE System Basics Configuration Guide, Chapter 3, Installing JunosE Software. New software releases are available for download from the Juniper Networks website at http://www.juniper.net/customers/support. You can use the downloaded image bundle to create your own software CDs.

  • Page 10: Upgrading From Release 5.1.1 Or Lower-Numbered Releases To Release 6.X.x Or Higher-Numbered Releases

    8, Maintaining the Router Moving Line Modules Between Releases The Juniper Networks ERX1440 Broadband Services Router employs a 40-Gbps SRP module and a new midplane. Release 3.3.2 was the first software release to support the 40-Gbps SRP module and midplane. Before you can transfer a compatible line module from a Juniper Networks ERX705, ERX710, or ERX1410 Broadband Services Router to an ERX1440 router, you must first load Release 3.3.2 or a higher...

  • Page 11: Srp Module Memory Requirements

    Release 10.3.2 SRP Module Memory Requirements For Release 5.3.0 and higher-numbered software releases on ERX14xx models, ERX7xx models, and the Juniper Networks ERX310 Broadband Services Router, see ERX Module Guide, Table 1, ERX Module Combinations, for detailed information about memory requirements.

  • Page 12: Self-Help Online Tools And Resources

    JunosE 10.3.2 Release Notes Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/ Search for known bugs: http://www2.juniper.net/kb/...

  • Page 13: Release Overview

    Release 10.3.2 Release Overview These Release Notes cover Release 10.3.2 of the system software for the Juniper Networks E Series Broadband Services Routers and contain the following sections: Release Highlights on page 7 Early Field Trial Features on page 7 Unsupported Features on page 9 Release Software Protocols on page 10 SRC Software and SDX Software Compatibility Matrix on page 12...
  • Page 14 The 10.3.x documentation set consists of several manuals and is available only in electronic format. You can print your own documentation using the PDF and HTML formats available at the Juniper Networks Technical Documentation Web site at www.juniper.net/techpubs. Refer to the following table to help you decide which document to use.

  • Page 15: Release Highlights

    The features described in this section are present in the code but have not yet been fully qualified by Juniper Networks. These features are available only for field test purposes in this release. If you use any of these features before they have been fully qualified, it is your responsibility to ensure that the feature operates correctly in your targeted configuration.

  • Page 16: Dhcp

    JunosE 10.3.2 Release Notes DHCP Support for DHCP External Server, DHCP Local Server, DHCP Relay, and DHCP Relay Proxy on POS Access Interfaces The following packet over SONET (POS) module combinations on E Series routers now support configuration of the DHCP external server, DHCP local server, DHCP relay, and DHCP relay proxy applications, alone or in combination, when the POS module is the access interface: POS module combinations on the E120 router and the E320 router:...

  • Page 17: Unified Issu

    The JunosE Release 10.3.x documentation set describes some features that are present in the code but that have not yet been fully qualified by Juniper Networks. If you use any of these features before they have been fully qualified, it is your responsibility to ensure that the feature operates correctly in your targeted configuration.

  • Page 18: Stateful Srp Switchover (High Availability)

    JunosE 10.3.2 Release Notes Stateful SRP Switchover (High Availability) Stateful SRP Switchover for Certain Applications The stateful SRP switchover feature has not been qualified for the following applications: Remote Access DHCP proxy client L2TP dialout Release Software Protocols The following list identifies the major software protocols supported in this release. For detailed information about any protocol, see the configuration guides.

  • Page 19: Multiprotocol Label Switching (Mpls)

    Release 10.3.2 Multiprotocol Label Switching (MPLS) Border Gateway Protocol (BGP-4) Label Distribution Protocol (LDP) Resource ReSerVation Protocol – Traffic Engineering Extensions (RSVP-TE) Network Management Protocols Simple Network Management Protocol (SNMP) versions 1, 2c, and 3 Routing Protocols Border Gateway Protocol (BGP-4) Distance Vector Multicast Routing Protocol (DVMRP) Internet Group Membership Protocol (IGMP) Intermediate System–to–Intermediate System (IS-IS)

  • Page 20: Src Software And Sdx Software Compatibility Matrix

    JunosE 10.3.2 Release Notes SRC Software and SDX Software Compatibility Matrix The SRC software offers the features of the SDX software on the C Series Controllers, a range of hardware platforms that use the Linux operating system. In contrast, the SDX software runs on Solaris workstations. The SRC software contains the features found in the associated SDX release plus additional features described in the SRC Release Notes.

  • Page 21: Bgp

    IPv6 address in the next-hop field on a directly connected external BGP peering. Work-around: Enable EBGP multihop configuration on the remote (non–Juniper Networks) peer. The following message might be displayed under certain conditions: bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting...

  • Page 22: Cli

    JunosE 10.3.2 Release Notes In Interface Configuration mode for a major interface, the CLI displays options for protocols that are not supported by that interface type. When you issue the reload command on an ERX310 router, the command might display a warning message that erroneously indicates that a synchronizing operation will be performed.
  • Page 23 Release 10.3.2 Deprecated Command Command Mode Preferred Command hostname Domain Map Tunnel client-name Configuration Still available in Global Configuration mode hssi description Interface Configuration hssi force dte acknowledge Interface Configuration hssi internal-clock Interface Configuration ignore dcd Interface Configuration ignore link-state-signals Interface Configuration [ no ] ike cr Global Configuration...
  • Page 24 JunosE 10.3.2 Release Notes Deprecated Command Command Mode Preferred Command mark-de Policy List Configuration mark-de in Classifier Group Configuration mode mark-exp Policy List Configuration mark-exp in Classifier Group Configuration mode mark-user-priority Policy List Configuration mark-user-priority in Classifier Group Configuration mode mpls ldp discovery Interface Configuration This command has no effect...

  • Page 25: Dhcp

    Release 10.3.2 Deprecated Command Command Mode Preferred Command traffic-class Policy List Configuration traffic-class in Classifier Group Configuration mode tunnel mpls autoroute announce Interface Configuration, None Tunnel Profile Configuration tunnel mpls label-dist Interface Configuration, None Tunnel Profile Configuration unframed Controller Configuration user-packet-class Policy List Configuration user-packet-class in...
  • Page 26 JunosE 10.3.2 Release Notes When the DHCP relay agent application and the DHCP external server application are configured in the same virtual router, using the ip dhcp-external server-sync command on an unnumbered IP interface does not function as expected. When you issue the ip dhcp-external server-sync command in this configuration to create subscriber state information based on lease renewals when the external DHCP server and the router are unsynchronized, the router does not forward the ACK request from the DHCP...

  • Page 27: Dynamic Interfaces

    Release 10.3.2 When these three conditions exist simultaneously, the ES2 4G LM may not be able to successfully process all DHCP packets. Although all clients may get bounded in DHCP relay or relay proxy, some clients may not get bounded in DHCP external server.

  • Page 28: Flash

    JunosE 10.3.2 Release Notes When installed in the ERX1440 router, the GE-HDE line module delivers full bandwidth of 4 GB per line module (2 GB at the ingress and 2 GB at the egress) only when installed in slot 2 or slot 4, and when the SRP-40G+ module is used in the router.

  • Page 29: Gre

    Release 10.3.2 When you shut down the only outgoing IP interface to the IP destinations of GRE/IP tunnels, the tunnels remain in the up state rather than transitioning to down. As a consequence, all IP routes that use these tunnels as next hops also remain in the routing table.

  • Page 30: Hdlc

    JunosE 10.3.2 Release Notes HDLC By design, on the cOC12/STM4 module you cannot delete a serial interface while data for the interface is still enqueued. The enqueued data can drain only when the interface is operationally up. Therefore you must ensure that the interface is operationally up before you delete it.
  • Page 31 Release 10.3.2 If you have enabled ipInterface logging at a priority of debug, the acknowledgment that an interface has been deleted from the line modules can return to the SRP module after the layers beneath IP have deleted their interfaces. Consequently, the original name of the interface cannot be resolved or displayed in the log, and the system instead displays the ifIndex of the IP interface.

  • Page 32: Ipsec

    JunosE 10.3.2 Release Notes IPSec When you shut down the only outgoing IP interface to the IP destinations of IPSec tunnels, the tunnels remain in the up state rather than transitioning to down. As a consequence, all IP routes that use these tunnels as next hops also remain in the routing table.

  • Page 33: L2Tp

    Release 10.3.2 L2TP L2TP peer resynchronization enables an L2TP failed endpoint to resynchronize with its peer non-failed endpoint. The JunosE Software supports failover protocol and silent failover peer resynchronization methods. If you configure the silent failover method, you must keep the following considerations in mind: PPP keepalives—To ensure resynchronization of the session database, PPP keepalives must be enabled on the L2TP data path.

  • Page 34: Mlppp

    User Exec and Privileged Exec modes respectively. These commands are intended to be used in a Juniper Networks internal lab environment for testing without a traffic generator. Do not configure a multicast group with more than 10,219 outgoing interfaces (OIFS) on the same ES2 10G LM.

  • Page 35: Packet Mirroring

    Release 10.3.2 Packet Mirroring The ES2 10G LM supports the packet mirroring feature when the module is paired with the ES2-S2 10GE PR IOA, the ES2-S1 GE-8 IOA, or the ES2-S3 GE-20 IOA. When you use the ES2 10G LM with these IOAs, CLI-based interface-specific mirroring is not supported.
  • Page 36 JunosE 10.3.2 Release Notes Multiple Forwarding Solution Rules for a Single Classifier List in a Policy Before Release 5.2.0, it was possible to configure a policy with multiple rules that specified forwarding solutions where all of these rules were associated with a single classifier list.

  • Page 37: Ppp

    Release 10.3.2 Example 2—In this example, three forwarding solution conflicts result in rules being overwritten. The filter rule is the last rule configured, and is therefore applied. host1(config)#policy-list bostTwo host1(config-policy-list)#forward classifier-group clacl5 host1(config-policy-list)#next-hop 1.1.1.1 classifier-group clacl5 WARNING: This rule has replaced a previously configured rule. host1(config-policy-list)#next-interface atm 1/0.0 classifier-group clacl5 WARNING: This rule has replaced a previously configured rule.

  • Page 38: Radius

    JunosE 10.3.2 Release Notes In JunosE Releases 7.1.x, 7.2.x, and 7.3.x, you can attach a QoS profile to Ethernet interfaces that are configured in a link aggregation group (LAG) interface. However, beginning with JunosE Release 8.0.1, you can attach a QoS profile directly to the LAG interface.

  • Page 39: Snmp

    MIB directory in the SW_Image_CD-2 folder of the JunosE Software image bundle, which you downloaded from the Juniper Networks website, that contains the release file for E120 and E320 routers. .

  • Page 40: Stateful Srp Switchover (High Availability)

    JunosE 10.3.2 Release Notes Stateful SRP Switchover (High Availability) Additional processing is required to maintain and mirror the necessary state information that enables subscriber sessions to stay up across an SRP failover. As a result, the performance of other control plane functions is reduced. Specifically, call setup rates are lower than in previous releases.

  • Page 41: Subscriber Interfaces

    Release 10.3.2 When IP tunnels are configured on a router enabled for stateful SRP switchover, and the Service Module (SM) carrying these tunnels is reloaded, stateful SRP switchover transitions to the pending state. Stateful SRP switchover remains in the pending state for 10 minutes following the successful reloading of the SM. This amount of time allows for IP tunnel relocation and for the tunnels to become operational again on the SM.

  • Page 42: System Logging

    JunosE 10.3.2 Release Notes In a router with a redundancy group that does not span quadrants (for example, a three-slot redundancy group that spans slots 0, 1, and 2 in an ERX1410 chassis), the potential bandwidth of the redundant module is erroneously included in the quadrant bandwidth calculation.

  • Page 43: Known Problems And Limitations

    Release 10.3.2 Known Problems and Limitations This section identifies the known problems and limitations in this release. For more information about known problems that were discovered at customer sites, you can log in to the JunosE Knowledge Base at https://www2.juniper.net/kb/, enter the defect ID number in the Search by Keyword field, and click Search.
  • Page 44 JunosE 10.3.2 Release Notes When you use the no-authenticate keyword with the subscriber command to prevent subscriber authentication so that the subscriber information can be used for DHCP option 82, suboption 2, the SRP module can reset. This issue does not occur when you use the no-authenticate keyword with the subscriber command as a way to perform a RADIUS configuration.

  • Page 45: Bfd

    Release 10.3.2 After you have shut down the interface to the next hop (for the route that is used to establish the BFD session), output for the show bfd session command erroneously indicates the shutdown interface as Management Interface (FastEthernet 6/0). [Defect ID 174271] Bridged Ethernet The CLI erroneously permits you to configure bridge1483 encapsulation over AAL5MUX IP even though that configuration is not supported.

  • Page 46: Dhcp External Server

    JunosE 10.3.2 Release Notes DHCP External Server With the unique client ID option enabled, when two clients with the same MAC address or client ID are on an interface (where one client is connected over a router and relay and the other client is connected directly), sending a release request from one of the clients might terminate another client.

  • Page 47: Forwarding

    Release 10.3.2 Forwarding The DoS protection egress rate is not accurate for the ES2 10G LM or the ES2 10G Uplink LM. [Defect ID 86925] When performing MAC validation to match subscriber demux entries with ARP host entries, the ES2 10G LM does an exact match, rather than a longest prefix match.

  • Page 48: Icr

    JunosE 10.3.2 Release Notes When you attach certain hierarchical policies to subinterfaces as input policies, secondary input policies, and output policies, incoming traffic loss can occur when the number of subinterfaces to which the policies are attached exceeds 4600. [Defect ID 86741] Ethernet statistics are incorrectly displayed for virtual port 8 of the ES2-S1 GE-8 IOA when that module is paired with the ES2 10G LM or the ES2 10G Uplink LM.

  • Page 49: Igmp

    Release 10.3.2 If you saved the running configuration of the router as a script file (.scr) and execute the script to apply the settings on the router, ICR partition configuration commands in the .scr file might fail to add group members to the partition. This problem happens when the subscriber configuration in the .scr file is placed before the ICR partition configuration.

  • Page 50: Ipsec

    JunosE 10.3.2 Release Notes Deleting a VRF with 32,000 static subscriber interfaces fails to complete. [Defect ID 82670] Work-around: Use a macro to delete all static subscriber interfaces before you delete a VRF. IP interface statistics become inconsistent when a slot is reset, because some traffic (such as control traffic) might be destined for the SRP module and is therefore counted elsewhere.

  • Page 51: Is-Is

    Release 10.3.2 IPSec tunnels created over Fast Ethernet interfaces fail to come up. [Defect ID 179256] Work-around: After you create the tunnel, bounce the tunnel interface by issuing the shutdown/no shutdown command sequence. The tunnel comes up successfully. IS-IS On a router configured with IS-IS and BFD, using the redundancy force srp command to force an SRP switchover sometimes brings down IS-IS and BFD.

  • Page 52: Mobile Ip

    JunosE 10.3.2 Release Notes Mobile IP The @realm variable and the @ keyword alone do not work for the show ip mobile binding command. [Defect ID 178653] Work-around: You can use the user@realm syntax instead to display the binding for a specific user, as in this example: host1#show ip mobile binding nai xyz@example.com Alternatively, you can display the entire Mobile IP binding table by issuing the show ip mobile binding command without additional options.

  • Page 53: Multicast

    Release 10.3.2 When you issue a traceroute or trace mpls command to trace the paths of router packets over MPLS interfaces on an ES2 10G LM or ES2 10G Uplink LM, the results include an extra unknown host. [Defect ID 174537] When you upgrade the router to JunosE Release 7.1.0 or a higher-numbered release from a release numbered lower than Release 7.1.0, remote ATM layer 2 over MPLS circuits (also known as MPLS shim interfaces) that use Martini...
  • Page 54 JunosE 10.3.2 Release Notes When you attach a policy to an interface and the policy contains a classifier rule that is unsupported for that interface, the CLI generates a message and the policy is applied. However, if an existing policy is already attached to that interface, then support for the new policy is not checked and the invalid policy is applied to the interface without warning.

  • Page 55: Pppoe

    Release 10.3.2 PPPoE The E Series router erroneously accepts a PADI with a payload length of 0 instead of rejecting it and incrementing the PPPoE Invalid PAD packet length counter. [Defect ID 48356] You cannot paste a load-rebalance command string that uses the percent option into a console or Telnet session from show configuration output because the output displays the % sign rather than the percent keyword that was submitted with the command and the percent sign is not recognized by the...
  • Page 56 JunosE 10.3.2 Release Notes The CLI erroneously enables you to configure a QoS profile with the ethernet node group command. [Defect ID 80861] The dynamic shaping rate calculated by the simple shared shaper can vary because of the variation in the enqueue rate of the constituent queues. Even when the offered load is constant, the mechanism that calculates the enqueue rate introduces a slight variation, introducing a slight variation in the calculated dynamic shaping rate.

  • Page 57: Rsvp-Te

    Release 10.3.2 When 32,000 subscribers with 128,000 QoS queues are brought up on an ES2 10G or ES2 10G ADV LM, the LM resets if you modify the QoS profile that contains the best-effort IP or VLAN node rule, which references a scheduler profile configured with shared shaping rate, to a scheduler profile configured with legacy shaping rate.

  • Page 58: Src Software And Sdx Software

    JunosE 10.3.2 Release Notes You cannot use the highest sensitivity bit-error rate setting (a value of 9) associated with APS/MSP alarm when you issue the threshold sd-ber command to configure a cOCx/STMx line module with cOC12-APS-capable IOAs. [Defect ID 72861] Work-around: Use only a value in the range 5–8 when you issue the threshold sd-ber command for this module combination, as in the following example: host1(config)#controller sonet 2/1...

  • Page 59: Subscriber Management

    Release 10.3.2 E120 router or E320 router When you use the ping command with the IPv6 address of the helper router in the broadcast network as the destination address and the loopback address of the helper router in the backbone area as the source address, no packet loss occurs.

  • Page 60: System

    JunosE 10.3.2 Release Notes System You cannot use a configuration script to boot the E320 router. [Defect ID 80304] If you hot swap an IOA and then remove it again before that IOA’s OK or FAIL LED is illuminated, the associated line module can reset. [Defect ID 177313/177267] Work-around: Ensure that you firmly insert the IOA into the chassis when you hot swap IOAs.
  • Page 61 Release 10.3.2 When any of the subsystems is excluded for a JunosE release, a unified ISSU to that release fails to apply conversion code to all of the line modules. As a result, the line modules reset when they come up with that release. [Defect ID 179595] Work-around: To prevent the exclusion of a subsystem file from the release, do the following before you upgrade to a new JunosE release that supports unified...

  • Page 62: Resolved Known Problems

    JunosE 10.3.2 Release Notes Resolved Known Problems The following problems were reported open in Release 10.3.1 and have been resolved in this release, or have been resolved since the 10.3.1p0-3 patch release. For more information about particular resolved problems, you can log in to the JunosE Knowledge Base at https://www2.juniper.net/kb/, enter the defect ID number in the Search by Keyword field, and click Search.

  • Page 63: Dhcpv6 Server

    Release 10.3.2 DHCPv6 Server E320 routers do not discard DHCPv6 Solicit and Rebind messages. [Defect ID 90798] Output value of "lease timer" has HEX cases and DECIMAL cases, as seen in dhcpv6LsGeneral. [Defect ID 90799] JunosE does not send an error notification Reply to a DHCPv6 Request sent on link local unicast.

  • Page 64: Ipv6

    JunosE 10.3.2 Release Notes Executing BFD last-resort also enables RTR last-resort. [Defect ID 89510] 100% CPU utilization after issuing the show ip socket statistics det command. [Defect ID 90751] Few PPP sessions drop due to "aaa duplicate check" failure, even though the /32 route is not present in SRP routing table.

  • Page 65: Rsvp-Te

    Release 10.3.2 RSVP-TE SRP module reset type: processor exception 0x300 (read attempts) task: rsvp_msgQueue_1 pc: 0x4d0547f0 -> Rsvp::doEndPointsChange [Defect ID 90246] SRC Software and SDX Software On an ERX router configured for a LAG interface, the show sae interfaces and the show sae subscribers command outputs display NasPortID as the interface name of DSI interface created.

  • Page 66: Errata

    JunosE 10.3.2 Release Notes Errata This section identifies errors found in the JunosE documentation. These errors are corrected in subsequent releases of the affected documentation. The JunosE documentation for Release 6.0.5 and higher-numbered releases states that when you upgrade the JunosE Software from Release 5.1.1 or lower-numbered releases, you must perform the upgrade in two stages: first to an intermediate release and then to the higher-numbered release that you want to run.
  • Page 67 Release 10.3.2 The Link Layer Maximums table (for the E120 and E320 routers) in Appendix A, System Maximums, of the JunosE Release Notes, for the following releases incorrectly stated that the maximum number of Ethernet S-VLANs per ES2-S2 10GE PR IOA with an ES2 10G LM or ES2 10G Uplink LM was 32,768: Releases 10.2.0 and 10.2.1 Release 10.3.0 The correct limit for Ethernet S-VLANs per ES2-S2 10GE PR IOA on these LMs in...
  • Page 68 JunosE 10.3.2 Release Notes ERX Module Guide, Appendix A, Module Protocol Support incorrectly states that IPv6 multicast is supported on the following line modules: cOCx FO line module with cOC3/STM1 modules cOCx FO line module with cOC12/STM4 FO I/O modules COCx-F3 line modules with CT3/T3 12 I/O modules OCx/STMx ATM line modules with 4xDS3 ATM I/O modules CT3/T3-FO line modules with CT3/T3 12 I/O modules...
  • Page 69 Release 10.3.2 The Configuring VRRP section in JunosE System Basics Configuration Guide, Chapter 1, Planning Your Network and the Before You Configure IP section in JunosE IP, IPv6, and IGP Configuration Guide, Chapter 1, Configuring IP erroneously refer to the JunosE IP Services Configuration Guide. These references are corrected to refer to the JunosE Service Availability Configuration Guide.
  • Page 70 JunosE 10.3.2 Release Notes The ICR Overview section in JunosE 10.3.x Service Availability Configuration Guide, Chapter 6, Managing Interchassis Redundancy, does not accurately describe how the ICR master partition functions. The following paragraph accurately describes how the ICR master partition functions: The subscriber broadcasts a PPPoE Active Discovery Initiation (PADI) packet to both the master and backup router.
  • Page 71 Release 10.3.2 In JunosE Service Availability Configuration Guide, Chapter 4, Configuring a Unified In-Service Software Upgrade, the DHCP Relay Server row in the Application Support for Unified In-Service Software Upgrades table is incorrectly marked as unsupported for the unified ISSU operation. DHCP relay has supported unified ISSU since JunosE Release 9.2.0.
  • Page 72 JunosE 10.3.2 Release Notes In the Detecting Peer Reachability with BFD section in JunosE BGP and MPLS Configuration Guide, Chapter 1, Configuring BGP Routing, the neighbor-bfd-liveness-detection command subsection incorrectly states the following: If you remove the BFD configuration while the BGP sessions and the BFD protocol session are up, then the BGP session may flap because the remote BGP speaker cannot detect why the BFD session went down.
  • Page 73 The term "Tunnel-Service Module" used in the JunosE Broadband Access Configuration Guide and the JunosE Physical Layer Configuration Guide is no longer valid. Juniper Networks support for the Tunnel Service Module (TSM) ended on December 31, 2009. The term "Service Module" replaces any references to the TSM.
  • Page 74 JunosE 10.3.2 Release Notes In the Monitoring MLD section in JunosE Multicast Routing Configuration Guide, Chapter 6, Configuring Multicast Listener Discovery, the following corrections apply to the commands used to monitor MLD configuration: The description of the bgp graceful-restart command in the JunosE Command Reference A to M incorrectly states that graceful restart is enabled by default.
  • Page 75 Release 10.3.2 The tables in the Interface Types and Specifiers section of Chapter 1, Command Reference Topics, in the JunosE Command Reference Guide erroneously state that the maximum number of PPPoE subinterfaces per Ethernet (GE/FE) line module is 4094. The correct number for an ERX router is 8000 and for an E120 or E320 router, it is 16,000.
  • Page 76 JunosE 10.3.2 Release Notes Errata...

  • Page 77: Appendix A System Maximums

    For some entries, early field trial (EFT) values are presented in addition to supported values. These values have not been fully qualified by Juniper Networks and are mentioned only for field test purposes in this release. EFT values are enclosed within parentheses with an EFT designation;...

  • Page 78: Erx310, Erx7Xx, And Erx14Xx System Maximums

    JunosE 10.3.2 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 ERX705 and Feature ERX310...

  • Page 79: Physical And Logical Density Maximums

    Appendix A: System Maximums 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.
  • Page 80 JunosE 10.3.2 Release Notes Table 2: Physical and Logical Density Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Fast Ethernet (10/100) ports per chassis 32/40 32/96 (FE-8 I/O and FE-8 SFP I/O modules) Gigabit Ethernet ports per chassis 4/12 (GE I/O modules) Gigabit Ethernet ports per chassis –...
  • Page 81 Appendix A: System Maximums Table 2: Physical and Logical Density Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Logical density per module combination (specified line module and all supported I/O modules) Logical E1s per cOCx/STMx F0 line module 63 per 63 per 63 per 63 per...

  • Page 82: Link Layer Maximums

    JunosE 10.3.2 Release Notes 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.
  • Page 83 Appendix A: System Maximums Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 ATM bulk configuration overriding profile assignments per chassis 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...
  • Page 84 JunosE 10.3.2 Release Notes Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 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 –...
  • Page 85 Appendix A: System Maximums Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 HDLC interfaces per chassis 4000 10,000 24,000 24,000 HDLC interfaces per line module COCX-F3 cOCx/STMx F0 2000 2000 2000 2000 CT3/T3 F0 1992 1992 1992 1992...
  • Page 86 JunosE 10.3.2 Release Notes Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 PPP packet logging Aggregate dynamic and static PPP interfaces for which you can log PPP packets per chassis PPPoE service name tables PPPoE service name tables per chassis Service name tags per PPPoE service name table (including one empty service name tag) PPPoE subinterfaces...

  • Page 87: Routing Protocol Maximums

    Appendix A: System Maximums 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.
  • Page 88 JunosE 10.3.2 Release Notes 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.
  • Page 89 Appendix A: System Maximums Table 4: Routing Protocol Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 IS-IS adjacencies 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...
  • Page 90 JunosE 10.3.2 Release Notes Table 4: Routing Protocol Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Response Time Reporter simultaneous operations per VR VRRP VRIDs per line module ASIC See Ethernet VRRP VRIDs per line module ASIC on page 76. ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 91: Policy And Qos Maximums

    Appendix A: System Maximums 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.
  • Page 92 JunosE 10.3.2 Release Notes Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 CAM entries (See Note 3 on page 83.) GE-2 64,000 – – 64,000 GE-HDE 64,000 – – 64,000 OC48/STM16 – – – 128,000 Policy egress interface attachments per ASIC line module...
  • Page 93 Appendix A: System Maximums Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Secure policies (for packet mirroring) Per ASIC line module 1022 1022 1022 1022 Per chassis 2400 2400 2400 2400 ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 94: Tunneling Maximums

    JunosE 10.3.2 Release Notes 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.
  • Page 95 Appendix A: System Maximums Table 6: Tunneling Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 IPSec tunnels per IPSec Service Module 5000 5000 5000 5000 L2TP sessions per chassis 16,000 16,000 16,000 32,000 (See Notes 2 and 3 on page 86.) L2TP sessions per line module (See Notes 1 and 3 on page 86.) GE-2 with shared tunnel-server ports provisioned...

  • Page 96: Subscriber Management Maximums

    JunosE 10.3.2 Release Notes 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.
  • Page 97 Appendix A: System Maximums Table 7: Subscriber Management Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 DHCPv6 local server Clients 32,000 32,000 32,000 32,000 (See Note 3 on page 88.) DHCP relay and relay proxy client (See Notes 1 and 2 on page 88.) DHCP client host routes for DHCP relay and DHCP relay 100,000 100,000...
  • Page 98 JunosE 10.3.2 Release Notes Table 7: Subscriber Management Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Subscriber interfaces (See Note 2 on page 88.) Dynamic subscriber interfaces per chassis 16,000 32,000 32,000 48,000 Dynamic subscriber interfaces per line module 8000 8000 8000...

  • Page 99: E120 And E320 System Maximums

    Appendix A: System Maximums E120 and E320 System Maximums The following tables provide system maximums for the E120 router and the E320 router. General System Maximums Table 8 lists some general system maximums for the E120 router and the E320 router.

  • Page 100: Physical And Logical Density Maximums

    JunosE 10.3.2 Release Notes Physical and Logical Density Maximums Table 9 lists physical and logical density maximums for the E120 router and the E320 router. The following notes are referred to in Table 9: 1. Wire rate indicates the port density that supports maximum (wire-rate) performance.
  • Page 101 Appendix A: System Maximums Table 9: Physical and Logical Density Maximums (continued) Feature E120 E320 OC12/STM-4 POS ports per chassis (ES2-S1 OC12-2 STM4 POS IOAs) OC48/STM16 ports per chassis (ES2-S1 OC48 STM16 POS IOAs) Logical density per chassis Logical OC3/STM1 per chassis Logical OC12/STM4 per chassis Logical OC48/STM16 per chassis E120 and E320 System Maximums...

  • Page 102: Link Layer Maximums

    JunosE 10.3.2 Release Notes Link Layer Maximums Table 10 lists link layer maximums for the E120 router and the E320 router. The following notes are referred to in Table 10: 1. On the ES2 10G LM, ES2 10G ADV LM, or ES2 10 G Uplink LM, you can have configurations with up to 100,000 static entries that support 100,000 DHCP relay proxy clients.
  • Page 103 Appendix A: System Maximums Table 10: Link Layer Maximums Feature E120 E320 ARP entries per line module Dynamic entries per LM 32,768 32,768 Static entries per ES2 4G LM 32,768 32,768 Static entries per ES2 10G LM, ES2 10G ADV LM, or ES2 128,000 128,000 10G Uplink LM...
  • Page 104 JunosE 10.3.2 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 ATM VP tunnels per port, all supported modules Bridged Ethernet interfaces per chassis 64,000 96,000 (See Notes 2 and 3 on page 94.) Bridged Ethernet interfaces per line module 16,000 16,000 (OCx/STMx ATM)
  • Page 105 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLANs per chassis 64,000 96,000 (See Notes 2, 4, and 5 on page 94.) Ethernet VLANs per IOA (See Note 7 on page 94.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM)
  • Page 106 JunosE 10.3.2 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLAN overriding profile assignments per chassis Ethernet VRRP VRIDs per line module HDLC interfaces per chassis 24,000 24,000 HDLC interfaces per line module 8000 8000 MLPPP bundles per chassis 12,000 12,000 MLPPP bundles per line module...
  • Page 107 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 PPP packet logging Aggregate dynamic and static PPP interfaces for which you can log PPP packets per chassis PPPoE service name tables PPPoE service name tables per chassis Service name tags per PPPoE service name table (including one empty service name tag) PPPoE subinterfaces per chassis...

  • Page 108: Routing Protocol Maximums

    JunosE 10.3.2 Release Notes Routing Protocol Maximums Table 11 lists routing protocol maximums for the E120 router and the E320 router. The following notes are referred to in Table 11: 1. The total set of FTEs can be shared by interfaces, next hops, ECMP sets, VRs, and VRFs.
  • Page 109 Appendix A: System Maximums Table 11: Routing Protocol Maximums (continued) Feature E120 E320 ECMP maximum paths to a destination BGP, IS-IS, MPLS, OSPF, RIP IPv4 forwarding table entries per chassis 1,048,576 1,048,576 (See Note 1 on page 100.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 110 JunosE 10.3.2 Release Notes Table 11: Routing Protocol Maximums (continued) Feature E120 E320 IPv6 routing table entries 100,000 100,000 (See Note 3 on page 100.) J-Flow statistics J-Flow–enabled VRs and VRFs, in any combination Sampled interfaces per VR or VRF Total sampled Interfaces per chassis Martini circuits for layer 2 services over MPLS Total Martini circuits per line module...

  • Page 111: Policy And Qos Maximums

    Appendix A: System Maximums Policy and QoS Maximums Table 12 lists policy and QoS maximums for the E120 router and the E320 router. The following notes are referred to in Table 12: 1. For more information about system resource requirements for nodes, queues, and shadow nodes, see JunosE Quality of Service Configuration Guide, Chapter 15, QoS Profile Overview.
  • Page 112 JunosE 10.3.2 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Policy classification (CLACL) entries per line module ES2 4G LM 256,000 256,000 ES2 10G LM 131,071 131,071 ES2 10G ADV LM 131, 071 131, 071 ES2 10G Uplink LM 65,535 65,535 Policy egress interface attachments per line module...
  • Page 113 Appendix A: System Maximums Table 12: Policy and QoS Maximums (continued) Feature E120 E320 ES2 10G Uplink LM 16,383 16,383 IP interface attachments ES2 10G Uplink LM 8191 8191 VLAN interface attachments Rate limiters (egress) per line module ES2 4G LM 64,000 64,000 ES2 10G LM...
  • Page 114 JunosE 10.3.2 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Parent groups (ingress) per line module ES2 4G LM 49,151 49,151 ES2 10G LM 8191 8191 (internal parent groups only) ES2 10G ADV LM 8191 8191 (internal parent groups only ES2 10G Uplink LM 8191...

  • Page 115: Tunneling Maximums

    Appendix A: System Maximums Tunneling Maximums Table 13 lists tunneling maximums for the E120 router and the E320 router. The following notes are referred to in Table 13: 1. The ES2-S1 Service IOA supports any combination of DVMRP, GRE, and L2TP tunnels up to a maximum of 8000 tunnels;...
  • Page 116 JunosE 10.3.2 Release Notes Table 13: Tunneling Maximums (continued) Feature E120 E320 L2TP tunnels per line module with shared 8000 8000 tunnel-server ports provisioned (See Note 2 on page 107.) L2TP tunnels per ES2-S1 Service IOA 16,000 16,000 (See Note 1 and Note 2 on page 107.) E120 and E320 System Maximums...

  • Page 117: Subscriber Management Maximums

    Appendix A: System Maximums Subscriber Management Maximums Table 14 lists subscriber management maximums for the E120 router and the E320 router. The following notes are referred to in Table 14: 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.
  • Page 118 JunosE 10.3.2 Release Notes Table 14: Subscriber Management Maximums (continued) Feature E120 E320 DHCP relay and relay proxy client (See Notes 1 and 2 on page 109.) DHCP client host routes for DHCP relay and DHCP relay 100,000 100,000 proxy combined (per chassis for all virtual routers; and per virtual router) DHCP relay proxy clients (per chassis for all virtual 100,000...

This manual is also suitable for:

Junose 10.3.2

Table of Contents