Juniper JUNOSE 11.0.2 - RELEASE NOTES Release Note
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE 11.0.2 RELEASE NOTES
  6. Release note
Juniper JUNOSE 11.0.2 - RELEASE NOTES Release Note

Juniper JUNOSE 11.0.2 - RELEASE NOTES 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 11.0.2
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Published: 2010-11-09

Advertisement

Table of Contents
loading

Related Manuals for Juniper JUNOSE 11.0.2 - RELEASE NOTES

Summary of Contents for Juniper JUNOSE 11.0.2 - RELEASE NOTES

  • Page 1: Release Notes

    JunosE Software ™ for E Series Broadband Services Routers ™ Release Notes Release 11.0.2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-11-09...
  • 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 11.0.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 11.0.2 Release Notes GRE ......................22 Hardware ....................22 HDLC....................... 23 IP......................23 IPSec ....................... 25 IS-IS ......................26 L2TP ......................26 Line Module Redundancy ................ 27 MLPPP..................... 27 MPLS ....................... 28 Multicast....................28 Packet Mirroring ..................29 Policy Management ................. 29 PPP......................
  • Page 7 Table of Contents SRC Software and SDX Software ............. 51 Stateful SRP Switchover (High Availability) and IP Tunnels ...... 52 Subscriber Management ................52 System ....................53 TCP ......................54 Unified ISSU .................... 54 Resolved Known Problems ................56 ARP ......................56 BGP ......................
  • Page 8 JunosE 11.0.2 Release Notes viii Table of Contents...

  • Page 9: Release 11.0.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 11.0.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 11.0.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 11.0.2 Release Overview These Release Notes cover Release 11.0.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 8 Unsupported Features on page 9 Release Software Protocols on page 10 SRC Software and SDX Software Compatibility Matrix on page 12...
  • Page 14 The 11.0.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

    Release 11.0.2 Release Highlights Release 11.0.2 is a maintenance release and includes the feature described in this section. Category Feature IPv6 Support for IPv6 Neighbor Discovery Router Advertisements with Service Modules on ERX Routers on page 7 IPv6 Support for IPv6 Neighbor Discovery Router Advertisements with Service Modules on ERX Routers Service line modules and IPSec service modules (collectively referred to as Service Modules) on ERX14xx models, ERX7xx models, and the ERX310 router...

  • Page 16: Early Field Trial Features

    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 17: System Maximums

    The JunosE Release 11.0.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 11.0.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 11.0.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 11.0.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

    IPv4 transport. This behavior is compliant with RFC 2545 but might have interoperability issues with other implementations that depend on a link-local 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. Known Behavior...

  • Page 22: Bgp/Mpls Vpns

    JunosE 11.0.2 Release Notes The following message might be displayed under certain conditions: bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting inbound TCP connection The message is generated when an unconfigured peer attempts to establish a TCP session with an E Series router and a valid route to the source address of the peer is absent from the router’s routing table.

  • Page 23: Bridged Ethernet

    Release 11.0.2 Bridged Ethernet The CLI erroneously permits you to configure bridge1483 encapsulation over AAL5MUX IP even though that configuration is not supported. [Defect ID 35013] 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 24 JunosE 11.0.2 Release Notes Deprecated Command Command Mode Preferred Command forward next-hop Policy List Configuration forward next-hop in Classifier Group Configuration mode forward next-interface Policy List Configuration forward interface in Classifier Group Configuration mode hostname Domain Map Tunnel client-name Configuration Still available in Global Configuration mode hssi description...
  • Page 25 Release 11.0.2 Deprecated Command Command Mode Preferred Command loopback Domain Map Configuration local-interface Still available in Controller Configuration and Interface Configuration modes loopback remote { remote line fdl Controller Configuration ansi | remote line fdl bellcore | remote line inband remote payload [ fdl ] [ ansi ] } mark Policy List Configuration...

  • Page 26: Dhcp

    JunosE 11.0.2 Release Notes Deprecated Command Command Mode Preferred Command show ike identity User Exec, Privileged Exec show ipsec identity show ike policy-rule User Exec, Privileged Exec show ipsec ike-policy-rule show ike sa User Exec, Privileged Exec show ipsec ike-sa show ip dhcp-external binding Privileged Exec show dhcp binding...

  • Page 27: Dhcp External Server

    Release 11.0.2 When you upgrade from a release numbered lower than Release 7.1.0, all DHCP host routes previously stored in NVS are deleted. After the upgrade, DHCP clients must reacquire their IP addresses, which results in the new host routes being correctly stored in NVS. DHCP External Server If you are using DHCP external server and a burst of client releases occurs during a unified ISSU, some of the client releases might not be processed.

  • Page 28: Ethernet

    JunosE 11.0.2 Release Notes DHCP external server may not be able to bind all DHCP clients when all of the following conditions exist: DHCP external server and either DHCP relay or relay proxy are configured in separate virtual routers on an E320 router. The client-facing and server-facing interfaces for DHCP external server and either DHCP relay or relay proxy are configured on the same ES2 4G LM.

  • Page 29: Flash

    Release 11.0.2 To bridge unicast known-DA packets at line rate on both 2-Gbps ports of the GE-2 line module or the GE-HDE module when paired with the GE-2 SFP I/O module, the minimum packet size must be at least 144 bytes. When installed in the ERX1440 router, the GE-2 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...

  • Page 30: Forwarding

    JunosE 11.0.2 Release Notes Forwarding A memory leak of about two percent can occur on the ES2 10G LM and result in a module reset when a large number of successive SRP switchovers take place with active DHCP clients. [Defect ID 86245] VPLS forwarding does not function properly when any of the following conditions occur: [Defect ID 79856] MLPPP interfaces are used...

  • Page 31: Hdlc

    Release 11.0.2 When you configure 1:5 line module redundancy by using either the 4XOC3 APS MULTIMODE or 4XOC3 APS SINGLE MODE I/O module, the spare R-Mid OCX I/O module you install must have assembly number 350-00094-01 Rev. A01 or later. Spare R-Mid OCX I/O modules with an earlier assembly number are not supported for 1:5 redundancy configurations that use either the 4XOC3 APS MULTIMODE or 4XOC3 APS SINGLE MODE I/O module.
  • Page 32 JunosE 11.0.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 33: Ipsec

    Release 11.0.2 The enhancement to the CLI to support unnumbered reference to any kind of interface rather than just loopback interfaces has consequences such as the following: [Defect ID 47743] If the references to shared interfaces appear in the show configuration output before the configuration for the interfaces they refer to, trying to restore such a configuration with a script generated from show configuration generates errors like the following:...

  • Page 34: Is-Is

    JunosE 11.0.2 Release Notes IS-IS When IS-IS is configured on a static PPP interface, the IS-IS neighbor does not come up if you remove the IP address from the interface and then add the IP address back to the interface. Work-around: When you remove and add back the IP address, you must also remove the IS-IS configuration from the interface and then add the configuration back to the interface by issuing the no router isis and router isis...

  • Page 35: Line Module Redundancy

    Release 11.0.2 NAT dynamic translation generation affects the LNS session creation time. When NAT dynamic translations and LNS sessions are created simultaneously, NAT dominates the CPU cycles of the tunnel-service module, resulting in a delay in the LNS session creation rate. The LNS session creation rate returns to its normal rate when NAT dynamic translations are no longer being generated.

  • Page 36: Mpls

    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 37: Packet Mirroring

    Release 11.0.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 38 JunosE 11.0.2 Release Notes The ES2 10G LM does not support the deprecated next-hop command. You cannot configure classifier lists that reference multiple fields for a VLAN policy list on the ES2 10G Uplink LM or the ES2 10G LM, with the exception of traffic-class and color.

  • Page 39: Ppp

    Release 11.0.2 Example 1—In this example, the filter rule action overwrites the forward rule, and is therefore applied. host1(config)#policy-list wstPolicyList host1(config-policy-list)#forward classifier-group svaleClacl1 host1(config-policy-list)#filter classifier-group svaleClacl1 WARNING: This rule has replaced a previously configured rule. host1(config-policy-list)#exit host1(config)# Example 2—In this example, three forwarding solution conflicts result in rules being overwritten.

  • Page 40: Qos

    JunosE 11.0.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 41: Radius

    Release 11.0.2 An error message regarding the qos-parameter instance QosParameterDefinition is erroneously generated on an ERX1440 router when it is configured for L2C and QoS RAM and receives TLV 144 (DSL Type). The parameter instantiation actually functions properly. [Defect ID 80620] 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 42: 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. Some Juniper Networks SNMPv1-formatted traps contain an incorrect object identifier (OID) in the SNMPv1-Trap-PDU enterprise field.

  • Page 43: Src Software And Sdx Software

    Release 11.0.2 SRC Software and SDX Software The SRC client does not prevent you from changing the name of the router while the client is connected to the SAE, resulting in SAE issues such as lost IP addresses and stale users. [Defect ID 77102] Work-around: To change the router name while the SRC client is connected to the SAE, shut down the SRC client, change the name, then re-enable the SRC client.

  • Page 44: Subscriber Interfaces

    JunosE 11.0.2 Release Notes After a stateful SRP switchover, each layer of the interface columns must reconstruct its interfaces from the mirrored information. While the interfaces are being reconstructed the SRP module cannot send or receive frames, including the protocol frames that signal graceful restart behavior with OSPF and IS-IS peers.

  • Page 45: System

    Release 11.0.2 System When you copy the running configuration to NVS, the E Series router verifies whether it has available space equal to at least twice the size of the .cnf file. If the space is insufficient, you cannot complete the copy. [Defect ID 40655] Work-around: Make sufficient space on the NVS by deleting .rel or .cnf files.

  • Page 46: System Logging

    JunosE 11.0.2 Release Notes System Logging The show configuration category management syslog virtual-router default command incorrectly displays logs for multiple syslog destinations when you add a log to only one syslog destination. The show log configuration command shows the correct configuration. [Defect ID 84082] 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...
  • Page 47 Release 11.0.2 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 48: Bfd

    JunosE 11.0.2 Release Notes 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).

  • Page 49: Dhcp External Server

    Release 11.0.2 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 50: Forwarding

    JunosE 11.0.2 Release Notes 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 51: Icr

    Release 11.0.2 The ES2 10G LM does not support framed routes configured for dynamic subscriber interfaces. [Defect ID 83154] On the ES2 10G LM, a VLAN ID of 0 assigned to an interface can prevent packets from being properly forwarded. [Defect ID 176125] 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...
  • Page 52 JunosE 11.0.2 Release Notes 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. (Version 2 is the default.) When more than about 100,000 mapped OIF entries are configured on a virtual router, issuing the no virtual router command for this and other virtual...

  • Page 53: Ipsec

    Release 11.0.2 When you change the demultiplexer type on a primary interface that has 1024 demultiplexer table entries, the ICC ping threshold times out due to the removal of the old entries and the addition of the new ones. [Defect ID 182218] After an SRP stateful switchover completes on an ERX1410 router configured with a single VPN routing and forwarding instance (VRF) and Network Address...

  • Page 54: Mld

    JunosE 11.0.2 Release Notes MLDv2 proxy is not supported. [Defect ID 46038] The E Series router MLDv2 proxy does not operate correctly in the presence of MLDv1 queriers. [Defect ID 46039/46045] Work-around: If an MLDv1 router is present on the network, configure version 1 with the ipv6 mld-proxy version command on that network interface.

  • Page 55: Mpls

    Release 11.0.2 When mobility bindings are present and you delete the Mobile IP home agent with the no virtual router command, Mobile IP sends a RADIUS Acct-Stop message with no accounting statistics for the subscribers. [Defect ID 179081] Work-around: Issue the clear ip mobile binding all command before you issue the no virtual router command.

  • Page 56: Policy Management

    JunosE 11.0.2 Release Notes Flow sampling stops after a cold switchover on a router that is configured with 16 VRs and 32 interfaces per VR, when all flows are passing through the configuration (32 flows per VR). [Defect ID 74477] Work-around: After the cold switchover is completed, reissue the ip flow-sampling-mode packet-interval 10 command on each VR, even though the command is present in the configuration.

  • Page 57: Pppoe

    Release 11.0.2 When you modify a rate-limit profile in Global Configuration mode after the system is in a scaled state, changes to the rate-limit profile fail owing to lack of adequate policy resources. However, the changed value of the rate-limit profile is displayed in the output of the show rate-limit profile command.

  • Page 58: Rsvp-Te

    JunosE 11.0.2 Release Notes 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] When QoS resources such as failure nodes and statistics bins are exhausted because of insufficient memory available on the line module, the failures are properly logged, but additional log messages are generated every 10 minutes...

  • Page 59: Service Manager

    Release 11.0.2 Service Manager After you activate an independent IPv6 service and issue either of the following commands on the default virtual router or any other virtual router, except the one on which the subscriber session is active, no output is displayed in the CLI interface: [Defect ID 181929] show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier...

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

    JunosE 11.0.2 Release Notes 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 is connected to a helper router in the OSPF IPv6 broadcast network and another helper router in the OSPF IPv6 backbone area.

  • Page 61: System

    Release 11.0.2 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) The major interface is shut down, which cause the dynamic VLAN...

  • Page 62: Tcp

    JunosE 11.0.2 Release Notes The SRP module resets in any of the following circumstances on an E320 router that has a line module configured with 5000 ANCP adjacencies: [Defect ID 176916] When you issue the issu initialization command from the console and then reload the line module from a Telnet session.
  • Page 63 Release 11.0.2 ATM line modules might reset after a unified ISSU when you attempt to add memory to a VLAN subinterface in a large bridged Ethernet configuration. [Defect ID 178798] Under certain conditions, a unified ISSU from JunosE Release 9.2.0p1-0 to the current release fails, and causes the SRP module and the ES2 4G LM to reset.

  • Page 64: Resolved Known Problems

    JunosE 11.0.2 Release Notes Resolved Known Problems The following problems were reported open in Release 11.0.1 and have been resolved in this 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 65: Ethernet

    Release 11.0.2 Ethernet LM4: reset type: panic; task: scheduler; file: vsm.cc - Vsm::addAciData [Defect ID 90723] LM4 reset type: panic, file: thernetHF1072.cc, line: 204, task: scheduler, Ethernet::autoConfigVlanReceive [Defect ID 90857] On executing the show configuration include-defaults > test.scr command the following message is displayed on the CLI: [Defect ID 90425] Please wait...

  • Page 66: Ipsec

    JunosE 11.0.2 Release Notes IPSec IPSec with NAT reports inboundSa = invalidAlgorithm when show ipsec tunnel detail command is used. [Defect ID 90642] IPv6 IPv6 ND over dynamic interface does not work on ERX if it acts as LNS. [Defect ID 88378] L2TP ERX does not respond to L2TP control packet during ISSU.

  • Page 67: Policy Management

    Release 11.0.2 Policy Management Policy might fail to attach during subscriber login on LM10A if massive policy update is in progress. [Defect ID 90739] “qos-parameter” is not cleaned up properly during stress tests. [Defect ID 90326] Service-manager qos-parameter value when modified by CoA/service-manager is not cleaned up.

  • Page 68: Errata

    JunosE 11.0.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 Obtaining Documentation section in the About the Documentation chapter of every JunosE document erroneously indicates that MIBs are available on the JunosE Software CDs.
  • Page 69 Beginning with JunosE Software Release 11.0.0, we are no longer providing a set of software CD-ROMs nor can you order software CDs. You can create your own software discs by downloading the compressed image bundle from the Download Software page on the Juniper Networks website at https://www.juniper.net/customers/csc/software. Errata...
  • Page 70 OSPF MIB from the JunosE Software CDs. You can access detailed notes about all MIBs only from the software image bundle that is available for downloading from the Juniper Networks website. This changed method of accessing MIBs is because software CDs, associated with your router model, are not supplied in Release 11.0.0.
  • Page 71 Release 11.0.2 In the Creating Multicast VPNs Using Default MDT section in Chapter 3, Configuring PIM for IPv4 Multicast of the JunosE Multicast Routing Configuration Guide, the command line configuration examples in Step 8, Step 9, and Step 10 are incorrect. The following steps present the correct information: Step 8: Configure the IP interface (Tv) in PE2:CE1 as a numbered or unnumbered PIM sparse-mode interface.
  • Page 72 JunosE 11.0.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: In the show ipv6 mld command section, the field name "learned groups" (which denotes the number of multicast groups that the virtual router has discovered) in the bulleted list of field descriptions and output example for this command is incorrect.
  • Page 73 Release 11.0.2 The correct behavior of BGP sessions, when you remove the BFD configuration for the last client tied to a BFD session, is as follows: If you remove the BFD configuration while the BGP sessions and the BFD protocol session are up, BFD moves to the Admin Down state and communicates the change to the peer to enable the client protocols to handle this transition in a seamless manner without going down.
  • Page 74 JunosE 11.0.2 Release Notes Use the ip-router-name command in Domain Map Configuration mode to assign an IPv4 virtual router. The no version restores the default router. An example of the ip-router-name command is as follows: host1(config)#aaa domain-map xyz.com host1(config-domain-map)#ip-router-name ipv4vr NOTE: The ip-router-name command replaces the router-name command, which has been deprecated and may be removed completely in a future release.
  • Page 75 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 76 JunosE 11.0.2 Release Notes The syntax for this command is: show memory-management protection [detail] [filter] The command can be used only in the support mode and is not user configurable. In the JunosE System Event Logging Reference Guide, for the radiusClient event category, the Error field incorrectly includes the following errors: Internal allocation error of base RADIUS server table Invalid virtual router for user's context...

  • 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 11.0.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 11.0.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 11.0.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 11.0.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 11.0.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 11.0.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 11.0.2 Release Notes Table 4: Routing Protocol Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 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 11.0.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: 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 94 JunosE 11.0.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 85.) L2TP sessions per line module (See Notes 1 and 3 on page 85.) GE-2 with shared tunnel-server ports provisioned...

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

  • Page 98: E120 And E320 System Maximums

    JunosE 11.0.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 99: 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 100 JunosE 11.0.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 101: 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 10 G Uplink LM, you can have configurations with up to 100,000 static entries that support 100,000 DHCP relay proxy clients.
  • Page 102 JunosE 11.0.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 103 Appendix A: System Maximums 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 93.) Bridged Ethernet interfaces per line module 16,000 16,000 (OCx/STMx ATM)
  • Page 104 JunosE 11.0.2 Release Notes 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 93.) Ethernet VLANs per IOA (See Note 7 on page 93.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM)
  • Page 105 Appendix A: System Maximums 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 106 JunosE 11.0.2 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 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 64,000 96,000 (See Notes 2 and 3 on page 93.)

  • Page 107: 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 108 JunosE 11.0.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 99.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 109 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 99.) 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 110: Policy And Qos Maximums

    JunosE 11.0.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 111 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 112 JunosE 11.0.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 113 Appendix A: System Maximums 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 114: Tunneling Maximums

    JunosE 11.0.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 115 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 106.) L2TP tunnels per ES2-S1 Service IOA 16,000 16,000 (See Note 1 and Note 2 on page 106.) E120 and E320 System Maximums...

  • Page 116: Subscriber Management Maximums

    JunosE 11.0.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 117 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 108.) 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 118 JunosE 11.0.2 Release Notes E120 and E320 System Maximums...

Table of Contents