Juniper JUNOSE SOFTWARE 11.0.1 - RELEASE NOTES 7-14-2010 Release Note
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE SOFTWARE 11.0.1 - S 7-14-2010
  6. Release note
Juniper JUNOSE SOFTWARE 11.0.1 - RELEASE NOTES 7-14-2010 Release Note

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

Advertisement

Table of Contents
loading

Related Manuals for Juniper JUNOSE SOFTWARE 11.0.1 - RELEASE NOTES 7-14-2010

Summary of Contents for Juniper JUNOSE SOFTWARE 11.0.1 - RELEASE NOTES 7-14-2010

  • Page 1: Release Notes

    JUNOSe Software ™ for E Series Broadband Services Routers ™ Release Notes Release 11.0.1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-07-14...
  • 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 Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. 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.1 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.1 Release Notes GRE ......................22 Hardware ....................22 HDLC....................... 23 IP......................23 IPSec ....................... 25 IS-IS ......................25 L2TP ......................26 Line Module Redundancy ................ 26 MLPPP..................... 27 MPLS ....................... 27 Multicast....................27 Packet Mirroring ..................28 Policy Management ................. 28 PPP......................
  • Page 7 Table of Contents SONET..................... 51 SRC Software and SDX Software ............. 51 Stateful SRP Switchover (High Availability) and IP Tunnels ...... 51 Subscriber Management ................52 System ....................53 System Logging ..................53 TCP ......................53 Unified ISSU .................... 54 Resolved Known Problems ................
  • Page 8 JUNOSe 11.0.1 Release Notes Routing Protocol Maximums ..............97 Policy and QoS Maximums..............100 Tunneling Maximums................104 Subscriber Management Maximums............106 Appendix B Module Name Cross-Reference Information Module Name Cross-Reference Information..........109 Appendix C Transferring DSL Line Rate Information from an Access Node to SRC Software Configuring the SRC Client to Retrieve DSL Information from Access Nodes..................111...

  • Page 9: Release 11.0.1

    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.1 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.1 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.1 Release Overview These Release Notes cover Release 11.0.1 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 10 Release Software Protocols on page 11 SRC Software and SDX Software Compatibility Matrix on page 13...
  • 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

    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 11.0.1 Release Notes The following command has been added to disable the learning option in the virtual router: no wait-for-gsmp-syn. The following command has been added to change the timer value: gsmp-syn-timeout "value" The following command has been added to change the timer to the default value of 60 seconds: no gsmp-syn-timeout In addition, the output of these two commands has been modified: show configuration...

  • Page 17: Ipv6

    Release 11.0.1 host1(config)#no ip dhcp-local limit pos To display the maximum number of IP address leases available for POS access interfaces, use the existing show ip dhcp-local limits command. For example: host1#show ip dhcp-local limits ***************************************** DHCP Local Server Address Limits ATM Limit - 48000 VLAN Limit...

  • Page 18: Unsupported Features

    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 19: Stateful Srp Switchover (High Availability)

    Release 11.0.1 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 20: Multiprotocol Label Switching (Mpls)

    JUNOSe 11.0.1 Release Notes Multiprotocol Label Switching (MPLS) Border Gateway Protocol (BGP-4) Label Distribution Protocol (LDP) Resource ReSerVation Protocol – Traffic Engineering Extensions (RSVP-TE) Layer 2 Protocols Asynchronous Transfer Mode (ATM) Bridged Ethernet Bridged IP Cisco High-Level Data Link Control (Cisco HDLC) Ethernet Extensible Authentication Protocol (EAP) Frame Relay...

  • Page 21: Src Software And Sdx Software Compatibility Matrix

    Release 11.0.1 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 22: 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 23: B-Ras

    Release 11.0.1 NAT does not function properly with secondary routing table lookup (fallback global) or global export mapping on the VRF. B-RAS Pool groups are not supported; although the ip local pool group command appears in the CLI, it is not supported. If the router is under a heavy load, the show profile command might take longer than usual to execute.
  • Page 24 JUNOSe 11.0.1 Release Notes Deprecated Command Command Mode Preferred Command fdl carrier Controller Configuration fdl string Controller Configuration fdl transmit Controller Configuration filter Policy List Configuration filter in Classifier Group Configuration mode forward next-hop Policy List Configuration forward next-hop in Classifier Group Configuration mode forward next-interface...
  • Page 25 Release 11.0.1 Deprecated Command Command Mode Preferred Command Policy List Configuration log in Classifier Group Configuration mode log severity debug Global Configuration log severity debug dhcpLocalProtocolDecode dhcpCapture 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 |...

  • Page 26: Dhcp

    JUNOSe 11.0.1 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.1 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.1 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.1 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 router.

  • Page 30: Gre

    JUNOSe 11.0.1 Release Notes 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 31: Hdlc

    Release 11.0.1 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 32 JUNOSe 11.0.1 Release Notes 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.

  • Page 33: Ipsec

    Release 11.0.1 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 34: L2Tp

    JUNOSe 11.0.1 Release Notes 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 35: 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 36: Packet Mirroring

    JUNOSe 11.0.1 Release Notes 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 37 Release 11.0.1 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. This typically was a configuration error, but the CLI accepted it.

  • Page 38: Ppp

    JUNOSe 11.0.1 Release Notes 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. host1(config-policy-list)#filter classifier-group clacl5 WARNING: This rule has replaced a previously configured rule. host1(config-policy-list)#exit host1(config)# NOTE:...

  • Page 39: Qos

    Release 11.0.1 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. As of JUNOSe Release 8.0.1, the software restricts you from attaching a QoS profile to any Ethernet interfaces that are members of a LAG.

  • Page 40: 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 41: Ssh

    Release 11.0.1 If the SRP module restarts when SSH is configured in a VR other than default, SSH can sometimes become disabled. This happens if SSH attempts to bind with a VR before the VR comes back up after the restart. In this event, a warning message is generated to alert you to the fact that SSH is disabled in that VR.

  • Page 42: Subscriber Interfaces

    JUNOSe 11.0.1 Release Notes Work-around: Increase the hold time to provide sufficient time for interface synchronization before the peers declare the adjacency down. For OSPF, use the ip ospf dead-interval command to set the hold time. We recommend that you use Bidirectional Forwarding Detection (BFD) with a longer OSPF dead interval to achieve fast failure detection.

  • Page 43: System Logging

    Release 11.0.1 E120 routers and E320 routers report a module as inactive when either: The primary line module has no IOAs. The primary line module has IOAs, but they have failed diagnostics. The standby line module has taken over for the primary line module, and has control of the IOAs.

  • Page 44: Known Problems And Limitations

    JUNOSe 11.0.1 Release Notes In releases numbered lower than Release 7.3.0, a dynamic tunnel-server port was located on port 8 of the GE-HDE line module and GE-8 I/O module. In Release 7.3.0 and higher-numbered releases, the dynamic tunnel-server port is located on port 9. When you upgrade to Release 7.3.0, any existing tunnel-server port configurations move from port 8 to port 9.
  • Page 45 Release 11.0.1 When you issue the no atm atm1483 auto-configure upperInterfaceType lockout-time command in Profile Configuration mode, the lockout time range does not revert to the default values. [Defect ID 66544] When one or more ATM1483 attributes appears in a profile, the show configuration include-defaults command fails to display the default values for all possible ATM1483 attributes.

  • Page 46: Bfd

    JUNOSe 11.0.1 Release Notes Work-around: Configure a CBR or a UBR plus PCR to create the circuit with the same parameters, depending on the desired priority for the traffic. CBR has a high priority and UBR plus PCR has a medium priority. 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...

  • Page 47: Dhcp External Server

    Release 11.0.1 Work-around: To avoid this defect, do all of the following: Do not use the ip auto-detect ip-subscriber command to enable packet triggering and to create dynamic subscriber interfaces Ensure that DHCP external server is configured in the virtual router. Ensure that the set dhcp relay inhibit-access-route-creation command is configured in the virtual router to prevent DHCP relay from installing host routes by default.

  • Page 48: File System

    JUNOSe 11.0.1 Release Notes Work-around: Use the following commands to enable auto link selection (GE port redundancy) and to switch from one port to the other port: (config-if)#no link selection (config-if)#link failover force File System When the primary SRP module is running JUNOSe Release 7.2.0 or higher-numbered release and the standby SRP module is running a release numbered lower than Release 7.2.0 (as in a downgrade situation), you cannot display the files for the standby SRP module.

  • Page 49: Icr

    Release 11.0.1 Work-around: You can do either of the following to avoid this problem. Specify each S-VLAN within the partially overlapping range as individual S-VLANs, as in the following example: host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 22 22 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 23 23 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 427 712 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 22 22 427 712...

  • Page 50: Igmp

    JUNOSe 11.0.1 Release Notes When you configure ICR settings using a CLI macro, ICR commands are run in quick succession. Sometimes, in such a scenario, the active SRP module resets if the event that causes the change of state of the VRRP instance reaches the ICR application before the ICR partition has been created.

  • Page 51: Ipsec

    Release 11.0.1 If you have a large configuration on a hybrid module combination (OC3/STM-1 GE/FE line module with the OC3-2 GE APS I/O module), boot from NVS, and issue the slot erase command before booting has completed, the line module resets.

  • Page 52: Is-Is

    JUNOSe 11.0.1 Release Notes In a network where you use the tunnel signalling command to specify that the security parameters and keys are configured manually for IPSec tunnels between VRs, the line modules reset when you delete and then re-create the IPSec tunnels.

  • Page 53: Mlppp

    Release 11.0.1 MLPPP Failure to meet all of the following conditions for fragmented packets can result in an incorrect operation during packet classification of the resulting reassembled packet: [Defect ID 50111] The initial fragment of a packet must either contain the entire MLPPP packet or be greater than 128 bytes.

  • Page 54: Multicast

    JUNOSe 11.0.1 Release Notes You cannot use an underscore character (_) in an MPLS tunnel name. [Defect ID 31291] 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 IGPs.

  • Page 55: Policy Management

    Release 11.0.1 The OC3/STM1 GE/FE line module might reset after sending Ethernet traffic into a VPLS network in a test environment when Ethernet packets are flooded to remote VPLS bridges. [Defect ID 74540] Policy Management On the E320 router, redirecting a large configuration with thousands of interfaces to a script file can take a long time, perhaps exceeding a half-hour depending on the configuration.

  • Page 56: Pppoe

    JUNOSe 11.0.1 Release Notes 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 57 Release 11.0.1 Work-around: Use node-controlled compound shared shaping configured on the best-effort scheduler node with EFA2-based ATM line modules. Egress strict-priority packets may experience high latency on OC3/STM1 ATM interfaces associated with the LM if you have shaped the port rate to more than 148.5 Mbps.

  • Page 58: Rsvp-Te

    JUNOSe 11.0.1 Release Notes The no qos-parameter-define definition command does not delete the specified QoS parameter definition. [Defect ID 176844] Work-around: Remove the interface and add the desired QoS parameters when you re-create the interface instead of deleting the definition. 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...

  • Page 59: Snmp

    Release 11.0.1 Work-around: To avoid this problem, use the show service-management owner-session ownerName ownerId command to display subscriber session information based on the session owner, instead of the show service-management subscriber-session subscriberName interface interfaceType command to display details on subscriber sessions. SNMP When you configure the router with an address pool that has two IP address ranges, only the range that you configured first is available via the MIB.

  • Page 60: Subscriber Management

    JUNOSe 11.0.1 Release Notes ERX7xx model, ERX14xx model, or ERX310 router: When you use the ping command with the IPv6 address of the helper router in the multicast area as the destination address and the loopback address of the helper router in the backbone area as the source address, a packet loss of 2 seconds occurs for the first stateful SRP switchover.

  • Page 61: System

    Release 11.0.1 If you configured a static interface column and removed the major interface These scenarios might occur if you administratively issue the shutdown and no shutdown commands on the major interface in which the dynamic interface column is configured. Work-around: Use the no interface ip ipAddress command to remove the dynamic subscriber interfaces.

  • Page 62: Unified Issu

    JUNOSe 11.0.1 Release Notes Unified ISSU 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 63: Resolved Known Problems

    Release 11.0.1 Resolved Known Problems Release 11.0.1 is based on the 11.0.1b0-2 patch release and incorporates all problem resolutions found in that release. For information about resolved problems in a patch release, customers with valid service agreements may log in to the JUNOSe Download Software page on the Customer Support Center Web site at https://www.juniper.net/support/csc/swdist-erx/.

  • Page 64: Dhcp

    JUNOSe 11.0.1 Release Notes DHCP In an SvLAN configuration the "show ip dhcp-local binding" command not shows the correct inner VLAN ID. [Defect ID 180125] SRP reset type exception 0x300 task: dhcpExternal pc- DhcpExternal::clientExpireTableErase() [Defect ID 89975] DhcpBasePlugIn::receivePacket() debugs displayed on line module for every DHCP packet received [Defect ID 89934] Slot-6 SRP reset type: panic file: dhcpRelay.cc task: dhcpRelay_dhcpRe lr: DhcpRelay::PbeSession::addClient [Defect ID 90261]...

  • Page 65: Forwarding

    Release 11.0.1 Forwarding Interrupt pc: 0x1450b64 - Fpf2DmaDriver::startRxDma(unsigned long) offset: 0x1c8 [Defect ID 179148] Memory Leak observed in NWT LAB While flapping DHCP and PPPoE subs on LM10. [Defect ID 185871] LM10A/LM10+ crashed while removing merge policies; file: aptationLayer.cc; line: 7515; task: scheduler. [Defect ID 185102] LM10 handling of an SEL event.

  • Page 66: Http

    JUNOSe 11.0.1 Release Notes LM10 Reset;file: aptationLayer.cc;line: 145;arg: 262144;PolicyMgrAgent::updatePolicyContext() [Defect ID 90374] OSPF adjacencies flapping on all cards when a card receiving multicast traffic is reloaded. [Defect ID 90323] GE interface in failed state where link is down but interface is up. [Defect ID 89942] LM4 line card reset type: panic msg "Node already on free list free list ptr = 0x0238e8e4;...

  • Page 67: Ipsec

    Release 11.0.1 IPSec Active SRP crash at task: ikepki file: osBitVector.cc line: 162 while 2k+ l2tp/ipsec tunnels are up. [Defect ID 178879] IPSEC module: reset type: panicfile: cicDriver.cctask: scheduler lr: CicDriver::encodeSaStamp. [Defect ID 90279] IS-IS ISIS in out-of-memory state and SRP-switch keeps ISIS remain down. [Defect ID 90482] L2TP SNMP walk on IfTable causes SRP to stall causing watchdog reset with L2tp...

  • Page 68: Rip

    JUNOSe 11.0.1 Release Notes LM-10A card in slot 0 crashed - reset type: panic arg (0xda) file: templateRam.cc line: 305. [Defect ID 90093] QoS has a limit of 4 Gbps on tenGigabitEthernet interface for maximum rate. [Defect ID 90097] Stale Qos-Profile bindings on L2TP sessions. [Defect ID 90338] Next Hop in default RIP route advertisement.

  • Page 69: Errata

    Release 11.0.1 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 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.1 In the Creating Multicast VPNs Using Default MDT section in Chapter 3, Configuring PIM for IPv4 Multicast of the JUNOSe Multicast Rounting 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.1 Release Notes The bgp graceful-restart command section incorrectly mentions that you can use the default keyword to restore the default condition, which causes the sending of advertisements of the graceful restart capability to be sent. However, the correct command behavior is that if you use the default keyword with the bgp graceful-restart command, advertisements of the graceful restart capability are not sent.
  • 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 11.0.1 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 75: 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 76: Erx310, Erx7Xx, And Erx14Xx System Maximums

    JUNOSe 11.0.1 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 77: 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 78 JUNOSe 11.0.1 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 79 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 80: Link Layer Maximums

    JUNOSe 11.0.1 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 81 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 82 JUNOSe 11.0.1 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 83 Appendix A: System Maximums Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Frame Relay virtual circuits per port COCX-F3 1000 1000 1000 1000 cOCx/STMx F0 1000 1000 1000 1000 OC48 (ERX1440 router only) – – –...
  • Page 84 JUNOSe 11.0.1 Release Notes Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 OCx/STMx/DS-3 ATM 8000 8000 8000 8000 OC3/STM-1 GE/FE 8000 8000 8000 8000 OCx/STMx POS OC48 (ERX1440 router only) – – – PPP packet logging Aggregate dynamic and static PPP interfaces for which you can log PPP packets per chassis PPPoE service name tables...

  • Page 85: 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 86 JUNOSe 11.0.1 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 87 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 88 JUNOSe 11.0.1 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 74. ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 89: 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 90 JUNOSe 11.0.1 Release Notes Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 CAM entries (See Note 3 on page 81.) 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 91: 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 92 JUNOSe 11.0.1 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 83.) L2TP sessions per line module (See Notes 1 and 3 on page 83.) GE-2 with shared tunnel-server ports provisioned...

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

  • Page 96: E120 And E320 System Maximums

    JUNOSe 11.0.1 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 97: 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 98 JUNOSe 11.0.1 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 99: 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 100 JUNOSe 11.0.1 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 101 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 91.) 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 102 JUNOSe 11.0.1 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLANs per IOA (See Note 7 on page 91.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM) (See Note 5 on page 91.) ES2-S1 GE-8 IOA 16,384 16,384 (with ES2 4G LM or ES2 10G LM)
  • Page 103 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 104 JUNOSe 11.0.1 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 91.) PPPoE subinterfaces per line module ES2 4G LM 16,000 16,000 ES2 10G LM 16,000 16,000 ES2 10G ADV LM...

  • Page 105: 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 106 JUNOSe 11.0.1 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 97.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 107 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 97.) 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 108: Policy And Qos Maximums

    JUNOSe 11.0.1 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 109 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 110 JUNOSe 11.0.1 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 111 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 112: Tunneling Maximums

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

  • Page 114: Subscriber Management Maximums

    JUNOSe 11.0.1 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 115 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 106.) 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 116 JUNOSe 11.0.1 Release Notes E120 and E320 System Maximums...

  • Page 117: 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 109 Module Name Cross-Reference Information Use Table 15 on page 109 to find the label name, software display name, and model number of a module.
  • Page 118 JUNOSe 11.0.1 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 119: 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 111 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the...
  • Page 120 JUNOSe 11.0.1 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 121 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 122: Monitoring The Status Of Transfer Of Updated Dsl Line Rate Parameters To The Cops Server

    JUNOSe 11.0.1 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 123: Junose Command Reference Guide Update

    Appendix C: Transferring DSL Line Rate Information from an Access Node to SRC Software Only the field that has been newly added by this feature in the output of the NOTE: 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 124 JUNOSe 11.0.1 Release Notes sscc update-policy-request enable...

This manual is also suitable for:

Junose 11.0.1

Table of Contents