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

Juniper JUNOSE SOFTWARE 10.2.2 - RELEASE NOTES 6-4-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.2.2
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Published: 2010-06-04

Advertisement

Table of Contents
loading

Related Manuals for Juniper JUNOSE SOFTWARE 10.2.2 - RELEASE NOTES 6-4-2010

Summary of Contents for Juniper JUNOSE SOFTWARE 10.2.2 - RELEASE NOTES 6-4-2010

  • Page 1: Release Notes

    JUNOSe Software ™ for E Series Broadband Services Routers ™ Release Notes Release 10.2.2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-06-04...
  • 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.2.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.2.2 Release Notes Hardware ....................20 HDLC....................... 21 IP......................22 IPSec ....................... 23 IS-IS ......................24 L2TP ......................24 Line Module Redundancy ................ 25 MLPPP..................... 26 MPLS ....................... 26 Multicast....................26 Packet Mirroring ..................26 Policy Management ................. 27 PPP......................
  • Page 7 Table of Contents Stateful SRP Switchover (High Availability) and IP Tunnels ...... 49 Subscriber Interfaces ................49 Subscriber Management ................50 System ....................51 System Logging ..................51 TCP ......................51 Unified ISSU .................... 51 Resolved Known Problems ................52 ATM......................
  • Page 8 JUNOSe 10.2.2 Release Notes viii Table of Contents...

  • Page 9: Release 10.2.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.2.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.2.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.2.2 Release Overview These Release Notes cover Release 10.2.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.2.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: Unified Issu

    JUNOSe 10.2.2 Release Notes POS module combinations on ERX14xx models, ERX7xx models, and the ERX310 router: OCx/STMx POS line module with OC3-4 I/O module OCx/STMx POS line modules with OC12/STM4 I/O module OC48 line module with OC48 FRAME APS I/O module In the current release, this feature is available for early field test purposes only.

  • Page 17: Unsupported Features

    The JUNOSe Release 10.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.2 Deprecated Command Command Mode Preferred Command traffic-class Policy List Configuration traffic-class in Classifier Group Configuration mode tunnel mpls label-dist Interface Configuration, None Tunnel Profile Configuration tunnel mpls autoroute announce Interface Configuration, None Tunnel Profile Configuration unframed Controller Configuration user-packet-class Policy List Configuration user-packet-class in...
  • Page 26 JUNOSe 10.2.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.2.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.2.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: Hdlc

    Release 10.2.2 SRP modules with only 1 GB of memory do not work reliably in ERX7xx and ERX14xx routers running JUNOSe Release 8.1.0 or higher, and may experience system resets due to an out of memory condition. However, the ERX310 router still supports 1 GB of memory in the SRP-SE10 module.
  • Page 30 JUNOSe 10.2.2 Release Notes When you upgrade from certain releases to JUNOSe Release 9.2.0p1-0 or higher-numbered releases, descriptions configured for IP interfaces or IP subinterfaces are not retained across the upgrade when the descriptions are shorter than 9 characters in length. Additionally, VRF descriptions are not retained across the upgrade when the combined length of the VRF description and the VRF name is shorter than 9 characters.

  • Page 31: Ipsec

    Release 10.2.2 When you want to use a configuration script to configure IP shared interfaces that reference a physical interface, you must issue the service show configuration format 2 command before you generate the script. If the default show configuration format (format 1) is enabled instead, the generated script cannot properly configure the IP shared interfaces because they are created before the physical interfaces.

  • Page 32: Is-Is

    JUNOSe 10.2.2 Release Notes During a warm restart after a system failover, the SRP module can take several minutes to resume the normal exchange of UDP/IP packets to applications. During this restart time, the E Series router does not send or receive dead peer detection (DPD) keepalives, which are used to verify connectivity between the router and its peers.

  • Page 33: Line Module Redundancy

    Release 10.2.2 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: Policy Management

    Release 10.2.2 When both interface-specific mirroring and user-specific mirroring are configured on the same interface, the interface-specific secure policies take precedence. The interface-specific secure policies, which you manually attach using the CLI, override and remove any existing secure polices that were attached by a trigger action.
  • Page 36 JUNOSe 10.2.2 Release Notes Multiple forwarding rules behavior for Release 5.2.0 and higher-numbered releases: Beginning with Release 5.2.0, the multiple rules behavior is designed so that when a forwarding solution conflict occurs within a policy, such as those described earlier, the second forwarding solution overwrites the preceding solution.

  • Page 37: Ppp

    Release 10.2.2 In rare cases, some policy configurations that use CAM hardware classifiers from releases earlier than Release 7.1.0 can fail because they exceed the total hardware classifier entry size of 128 bits that was introduced in Release 7.1.0. For more information and examples of previous configurations, see JUNOSe Policy Management Configuration Guide, Chapter 8, Policy Resources.

  • Page 38: Radius

    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 39: Ssh

    Release 10.2.2 The SNMPv1-formatted versions of the following Juniper Networks traps incorrectly contain ...x.y.z.0 in the SNMPv1-Trap-PDU enterprise field. That is, a zero is mistakenly appended to the correct enterprise OID value. Trap Name Expected Enterprise OID Enterprise OID Sent by SNMP Agent junidApsEventSwitchover .1.3.6.1.4.1.4874.3.2.2.1.2...

  • Page 40: Subscriber Interfaces

    JUNOSe 10.2.2 Release Notes Stateful SRP switchover remains inactive for 20 minutes after an initial cold-start or cold-restart of the router. This delay enables the system to reach a stable configuration before starting stateful SRP switchover. If you want to override the 20-minute timer, turn high availability off by using the mode file-system-synchronization command, and then on again by using the mode high-availability command.

  • Page 41: System

    Release 10.2.2 A packet-triggered subscriber interface is created when the router receives a packet with an IP source address that does not match any entries in the demultiplexer table. When the router detects an unmatched packet, it generates a trigger event that determines whether to create a dynamic subscriber interface or configure an existing interface.

  • Page 42: System Logging

    JUNOSe 10.2.2 Release Notes System Logging If you enable engineering logs and set the control network logs to a level of notice or lower (down from the default of error), you might see erroneous controlNetwork log messages like the following that are generated because SNMP polling on line modules (correctly) detects no fabric: [Defect ID 43168] NOTICE 09/01/2002 18:47:52 CEST controlNetwork (slot 11): Control Bus Master slave error 0x5 while accessing slot...
  • Page 43 Release 10.2.2 When a mirror rule that triggers on username is employed for packet mirroring of dynamic IP subscribers over ATM, removal of the rule does not disable packet mirroring. [Defect ID 175356] Work-around: Use a mirror rule that triggers on account session ID rather than on username.

  • Page 44: Bfd

    JUNOSe 10.2.2 Release Notes When 16,000 PPPoA interfaces are configured on an OCx/STMx ATM line module paired with an OC3-4 I/O module in an ERX14xx model, ERX7xx model, or ERX310 router, Ping traffic passing through the line module on the restarting router experiences an outage of 103 seconds, which is beyond the maximum limit, after a unified ISSU from JUNOSe Release 9.2.0p1-0 to 9.3.0b0-12.

  • Page 45: Dhcp

    Release 10.2.2 DHCP DHCP packets are not forwarded to the DHCP server over dynamically created interfaces when all of the following are true: [Defect ID 180343] DHCP relay or DHCP relay proxy is configured on the router. The client-facing interfaces are created dynamically using bridged Ethernet over static ATM PVCs.

  • Page 46: Dos Protection

    JUNOSe 10.2.2 Release Notes DoS Protection A Telnet session closes when sending ipLocalBGP protocol traffic at a rate in the range 4096–4200 packets per second (pps) with suspicious control flow detection enabled. [Defect ID 81974] Work-around: When the traffic drops below 4096 pps, open a new Telnet session.
  • Page 47 Release 10.2.2 Specifying S-VLAN ranges that partially overlap does not work. [Defect ID 81886/81918] For example, the following configuration fails because S-VLAN 22 falls within the previously specified S-VLAN range of 21–23. host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 427 712 host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 22 22 101 110 Work-around: You can do either of the following to avoid this problem.

  • Page 48: Igmp

    JUNOSe 10.2.2 Release Notes IGMP IGMPv3 proxy is not supported. [Defect ID 46038] The E Series router IGMPv3 proxy does not operate correctly in the presence of IGMPv2 queriers. [Defect ID 46039/46045] Work-around: If an IGMPv2 router is present on the network, do not configure version 3 with the ip igmp-proxy version command on that network interface.

  • Page 49: Ipsec

    Release 10.2.2 Logical port 20 on the ES2-S3 GE-20 IOA is reserved for the hardware multicast packet replication feature. Logical port 20 and the hardware multicast replication feature are not supported on the ES2-S3 GE-20 IOA in this release. [Defect ID 84727] After an SRP stateful switchover completes on an ERX1410 router configured with a single VPN routing and forwarding instance (VRF) and Network Address Translation (NAT), the SRP module that becomes active after the switchover...

  • Page 50: L2Tp

    JUNOSe 10.2.2 Release Notes If LSPs are announced into IS-IS, then the IS-IS routes cannot be used for multicast RPF checks, because LSPs are unidirectional. [Defect ID 28526] Work-around: Configure static RPF routes with native hops when LSPs are autoroute announced to IS-IS. L2TP After a unified ISSU completes on a router functioning as an L2TP access concentrator (LAC), traffic outages occur on the L2TP network server...

  • Page 51: Mpls

    Release 10.2.2 The clear ip mobile binding nai @realm command does not work. [Defect ID 178652] Work-around: Use the following version of the command instead: clear ip mobile binding nai user@realm The setup rate for Mobile IP client sessions decreases when you repeatedly bring a large number of sessions down and back up.

  • Page 52: Multicast

    JUNOSe 10.2.2 Release Notes Multicast When you configure more than 10,219 outgoing interfaces (OIFs) on the same ES2 10G LM in a single multicast group, the configuration of the multicast group’s OIF membership from the SRP module to the line module exceeds the size of a single message and is sent in fragments.

  • Page 53: Pppoe

    Release 10.2.2 When an MD-Port-Number value greater than 65,535 is sent to an E120 or E320 router by means of a COA request, the value that is displayed in the UDP header of mirrored packets is the actual value minus 65,536. For example, an MD-Port-Number of 65,540 is displayed in the mirrored packet as 4.

  • Page 54: Qos

    JUNOSe 10.2.2 Release Notes 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 CLI.

  • Page 55: Rsvp-Te

    Release 10.2.2 On a router that has both an ES2 10G LM and an ES2 4G LM installed, the byte count reported by the show fabric-queue egress-slot command is incorrect. The reported packet count is correct. [Defect ID 80965] On the E120 and E320 routers, you cannot attach QoS profiles to L2TP tunnels by means of the CLI because the CLI does not pass the router ID to QoS.

  • Page 56: Service Manager

    JUNOSe 10.2.2 Release Notes Service Manager The CLI fails to display any output when you include the optional service-session serviceName keyword and variable in the show service-management owner-session command. [Defect ID 181269] Work-around: Do not include this optional argument. The service session information is displayed properly when you issue the show service-management owner-session command without including the optional service-session serviceName keyword and variable.

  • Page 57: Stateful Srp Switchover (High Availability) And Ip Tunnels

    Release 10.2.2 When multiple IPv6 interfaces are configured with policies attached from SRC, only some of the IPv6 interfaces have the policies attached. [Defect ID 179498] Changing the SSCC status (enable/disable) while IPv6 interfaces are configured might cause the SRP to reset. [Defect ID 179537] Stateful SRP Switchover (High Availability) and IP Tunnels A packet loss sometimes occurs during stateful SRP switchover when you use the ping command on a router that is configured for OSPF graceful restart, and...

  • Page 58: Subscriber Management

    JUNOSe 10.2.2 Release Notes Subscriber Management Dynamic subscriber interfaces continue to remain in the down or not present operational state in either of the following scenarios: [Defect ID 81269] If you configured a dynamic interface column, such as a dynamic bridged Ethernet interface, dynamic VLAN interface, or an ATM interface, and when any one of the following conditions is satisfied: The major interface is bounced (shut down and reenabled)

  • Page 59: System

    Release 10.2.2 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 60: Resolved Known Problems

    JUNOSe 10.2.2 Release Notes 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 61: Forwarding

    Release 10.2.2 Forwarding LM10A or LM10+ crashes when removing merge policies; file: aptationLayer.cc; line: 7515; task: scheduler. [Defect ID 185102] Packets with router alert IP option configured are sent to SRP though the source addresses in the packets are not local and the associated protocol is disabled. [Defect ID 88859] Unable to send message type X to address (15a15 0) because ICC returned error code Y log message not clear.

  • Page 62: Ospf

    JUNOSe 10.2.2 Release Notes OSPF After executing the clear ipv6 ospf process command, interfaces in the DOWN state appear in the show ipv6 ospf database output. [Defect ID 90478] OSPF adjacency might flap when ISSU is performed with OSPF default Hello and Dead interval timers.
  • Page 63 Release 10.2.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 64 JUNOSe 10.2.2 Release Notes The 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 65 Release 10.2.2 Both the DHCP relay and relay proxy applications began supporting unified ISSU in JUNOSe Release 9.2.0. Therefore, you need not unconfigure these applications from all virtual routers to perform a unified ISSU operation for JUNOSe Release 9.2.0 and higher-numbered releases. DHCP relay proxy continues processing of DHCP release requests during the unified ISSU to maintain server-client synchronization.
  • Page 66 JUNOSe 10.2.2 Release Notes In the Configuring Data MDTs section in Chapter 3, Configuring PIM for IPv4 Multicast of the JUNOSe Multicast Routing Configuration Guide, the procedures for configuring the pe13DataMdtSend access-list are incorrect. For correct procedures to configure the default Multicast Distribution Trees (MDT) and the data MDTs for configuring the access list, see Appendix C, Configuring the Default and Data MDTs in the JUNOSe 10.2.1 Release Notes.
  • Page 67 Release 10.2.2 The information on this functionality and associated command is missing from the following guides in the JUNOSe documentation set: JUNOSe Broadband Access Configuration Guide—Configuring the SRC Client section in Chapter 1, Configuring Remote Access, and Monitoring SRC Client Conection Status section in Chapter 2, Monitoring and Troubleshooting Remote Access JUNOSe Command Reference Guide N to Z...
  • Page 68 JUNOSe 10.2.2 Release Notes In addition, the Note in this command section inaccurately states that the E Series router supports graceful restart only as a receiving peer and not as a restarting peer. However, E Series routers have supported graceful restart as restarting peers, in addition to functioning as receiving peers, since JUNOSe Release 5.1.0.

  • Page 69: 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 70: Erx310, Erx7Xx, And Erx14Xx System Maximums

    JUNOSe 10.2.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 71: 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 72 JUNOSe 10.2.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 73 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 74: Link Layer Maximums

    JUNOSe 10.2.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 75 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 76 JUNOSe 10.2.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 77 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 78 JUNOSe 10.2.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 79: 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 80 JUNOSe 10.2.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 81 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 82 JUNOSe 10.2.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 68. ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 83: 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 84 JUNOSe 10.2.2 Release Notes Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 CAM entries (See Note 3 on page 75.) 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 85: Tunneling Maximums

    Appendix A: System Maximums 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 86 JUNOSe 10.2.2 Release Notes 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 77.) L2TP sessions per line module (See Notes 1 and 3 on page 77.) GE-2 with shared tunnel-server ports provisioned...

  • Page 87: Subscriber Management Maximums

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

  • Page 90: E120 And E320 System Maximums

    JUNOSe 10.2.2 Release Notes 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 91: Physical And Logical Density Maximums

    Appendix A: System Maximums 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 92 JUNOSe 10.2.2 Release Notes 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 93: Link Layer Maximums

    Appendix A: System Maximums 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 10G Uplink LM, you can have configurations with up to 100,000 static entries that support 100,000 DHCP relay proxy clients.
  • Page 94 JUNOSe 10.2.2 Release Notes 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 95 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 Bridged Ethernet interfaces per chassis 64,000 96,000 (See Notes 2 and 3 on page 85.) Bridged Ethernet interfaces per line module 16,000 16,000 (OCx/STMx ATM) Dynamic interfaces Active autosensed dynamic interface columns per 64,000 96,000...
  • Page 96 JUNOSe 10.2.2 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLANs per IOA (See Note 7 on page 85.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM) (See Note 5 on page 85.) ES2-S1 GE-8 IOA 16,384 16,384 (with ES2 4G LM or ES2 10G LM)
  • Page 97 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 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 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...
  • Page 98 JUNOSe 10.2.2 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 PPPoE subinterfaces per chassis 64,000 96,000 (See Notes 2 and 3 on page 85.) PPPoE subinterfaces per line module ES2 4G LM 16,000 16,000 ES2 10G LM 16,000 16,000 ES2 10G ADV LM...

  • Page 99: Routing Protocol Maximums

    Appendix A: System Maximums 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 100 JUNOSe 10.2.2 Release Notes 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 91.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 101 Appendix A: System Maximums Table 11: Routing Protocol Maximums (continued) Feature E120 E320 IPv6 routing table entries 100,000 100,000 (See Note 3 on page 91.) 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 102: Policy And Qos Maximums

    JUNOSe 10.2.2 Release Notes 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 103 Appendix A: System Maximums 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 104 JUNOSe 10.2.2 Release Notes 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 105 Appendix A: System Maximums Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Parent groups (ingress) per line module ES2 4G LM 8191 8191 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 106: Tunneling Maximums

    JUNOSe 10.2.2 Release Notes 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 107 Appendix A: System Maximums 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 98.) L2TP tunnels per ES2-S1 Service IOA 16,000 16,000 (See Note 1 and Note 2 on page 98.) E120 and E320 System Maximums...

  • Page 108: Subscriber Management Maximums

    JUNOSe 10.2.2 Release Notes 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 109 Appendix A: System Maximums Table 14: Subscriber Management Maximums (continued) Feature E120 E320 DHCP relay and relay proxy client (See Notes 1 and 2 on page 100.) 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...
  • Page 110 JUNOSe 10.2.2 Release Notes E120 and E320 System Maximums...

  • Page 111: Appendix B Module Name Cross-Reference Information

    Appendix B Module Name Cross-Reference Information This appendix provides information on the label name, software display name, and model number of ERX modules. This information supplements the ERX Module Guide. Module Name Cross-Reference Information on page 103 Module Name Cross-Reference Information Use Table 15 on page 103 to find the label name, software display name, and model number of a module.
  • Page 112 JUNOSe 10.2.2 Release Notes Table 15: Module Naming Reference for ERX Routers (continued) Label Name Software Display Name Model Number GE-HDE GE-HDE-8 ERX-GE-MOD OC3/STM1 GE/FE 2xOC3-ATM 1xGE I/O ERX-OCXGE-MOD Service Modules IPSEC SERVICE IPsec ERX-IPSECURE-MOD SERVICE MODULE SERVICE MODULE ERX-SERVICE-MOD I/O Modules 4xDS3 ATM I/O DS3-4P I/O...

  • Page 113: Appendix C Transferring Dsl Line Rate Information From An Access Node To Src Software

    Appendix C Transferring DSL Line Rate Information from an Access Node to SRC Software This appendix describes support for collection of updated DSL line rate parameters from an access node and transfer of this information from the Common Open Policy Service (COPS) or SRC client to the COPS server with other COPS messages. Configuring the SRC Client to Retrieve DSL Information from Access Nodes on page 105 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the...
  • Page 114 JUNOSe 10.2.2 Release Notes The access node passes the DSL line rate parameters, whenever they change, to the SRC client. The SRC client appends updated parameters to the COPS messages that it sends to the COPS server or SRC server. A COPS server processes the following topology parameters that it receives from the SRC client in the updated COPS messages: junoseIpInterfaceMode...
  • Page 115 Appendix C: Transferring DSL Line Rate Information from an Access Node to SRC Software Even if you confirm the prompt to enable the SRC client to forcibly send updated DSL line rate parameters to the COPS server, the COPS server that is running a release of SRC software earlier than Release 3.0.0 ignores the updated line rate details that it receives and processes only the other information in the COPS messages.

  • Page 116: To The Cops Server

    JUNOSe 10.2.2 Release Notes Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the COPS Server Display whether the SRC client is enabled to retrieve updated DSL line rate details Purpose from ANCP and send them to the SRC client with corresponding COPS messages. The command output refers to the SRC client by its former name, SSC client.

  • Page 117: Junose Command Reference Guide Update

    Appendix C: Transferring DSL Line Rate Information from an Access Node to SRC Software NOTE: Only the field that has been newly added by this feature in the output of the show sscc info command is described here. For a complete version of the descriptions of all the other fields that are displayed in the output of this command, see JUNOSe Broadband Access Configuration Guide, Chapter 2, Monitoring and Troubleshooting Remote Access.
  • Page 118 JUNOSe 10.2.2 Release Notes sscc update-policy-request enable...

This manual is also suitable for:

Junose 10.2.2

Table of Contents