Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE 10.0.3 - S 4-30-2010
  6. Release note
Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

For e series broadband services routers
Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Release Notes

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 and is the answer not in the manual?

Questions and answers

Related Manuals for Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010

Summary of Contents for Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010

  • Page 1: Release Notes

    JUNOSe Software ™ for E Series Broadband Services Routers ™ Release Notes Release 10.0.3 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-04-30...
  • 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 10.0.3 Release Installation ..................1 Upgrading to Release 5.3.0 or a Higher-Numbered Release ....... 1 Upgrading from Release 5.1.1 or Lower-Numbered Releases to Release 6.x.x or Higher-Numbered Releases ........2 Moving Line Modules Between Releases ............ 2 SRP Module Memory Requirements ............
  • Page 6 JUNOSe 10.0.3 Release Notes Hardware ....................20 HDLC....................... 21 IP......................21 IPSec ....................... 23 IS-IS ......................24 L2TP ......................24 Line Module Redundancy ................ 25 MLPPP..................... 25 MPLS ....................... 26 Multicast....................26 Packet Mirroring ..................26 Policy Management ................. 27 PPP......................
  • Page 7 Table of Contents SNMP ...................... 48 SONET..................... 48 SRC Software and SDX Software ............. 48 Stateful SRP Switchover (High Availability) and IP Tunnels ...... 49 Subscriber Interfaces ................49 Subscriber Management ................49 System ....................49 System Logging ..................50 TCP ......................
  • Page 8 JUNOSe 10.0.3 Release Notes Appendix B Module Name Cross-Reference Information Module Name Cross-Reference Information..........107 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..................109 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the COPS Server .............112 JUNOSe Command Reference Guide Update ..........113 sscc update-policy-request enable ..............113...

  • Page 9: Release 10.0.3

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

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

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

  • Page 11: Srp Module Memory Requirements

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

  • Page 12: Self-Help Online Tools And Resources

    JUNOSe 10.0.3 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

    The 10.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 14 JUNOSe 10.0.3 Release Notes Task Document Install the router ERX Hardware Guide E120 and E320 Hardware Guide Learn about modules ERX Module Guide ERX End-of-Life Module Guide E120 and E320 Module Guide Get up and running quickly E Series Installation Quick Start poster or ERX Quick Start Guide E120 and E320 Quick Start Guide Configure the router...

  • Page 15: Release Highlights

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

  • Page 16: Unified Issu

    The JUNOSe Release 10.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 17: Policy Management

    Release 10.0.3 ipv6 pim query-interval route map mdt-data-delay tunnel group-address-pool mdt-data-holdown tunnel source Policy Management Policy Exception Rule and the ES2 10G LM The ES2 10G LM does not support the HTTP redirect feature. In addition, you cannot attach policy actions with the exception rule to an IP policy classifier group.

  • Page 18: Multiprotocol Label Switching (Mpls)

    JUNOSe 10.0.3 Release Notes Intermediate System–to–Intermediate System (IS-IS) Layer 2 Virtual Private Networks (L2VPNs) Mobile IP Open Shortest Path First (OSPF) version 2 and version 3 Protocol Independent Multicast Protocol (PIM), including PIM dense mode, PIM sparse mode, PIM dense-sparse mode, and PIM source-specific multicast Routing Information Protocol (RIP) version 2 Virtual Private LAN Service (VPLS) Virtual Router Redundancy Protocol (VRRP)

  • Page 19: Security Protocols

    Release 10.0.3 Security Protocols Internet Key Exchange (IKE) Internet Security Association and Key Management Protocol (ISAKMP) IP Authentication Header (AH) IP Encapsulating Security Payload (ESP) Network Address Translation (NAT) 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.

  • Page 20: Atm

    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 21: Cli

    Release 10.0.3 If the router is under a heavy load, the show profile command might take longer than usual to execute. Work-around: You can either delay examination of profiles until the router is less busy, or save a copy of the profile to a text file off the router. In Interface Configuration mode for a major interface, the CLI displays options for protocols that are not supported by that interface type.
  • Page 22 JUNOSe 10.0.3 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 23 Release 10.0.3 Deprecated Command Command Mode Preferred Command loopback remote { remote line fdl Controller Configuration ansi | remote line fdl bellcore | remote line inband remote payload [ fdl ] [ ansi ] } mark Policy List Configuration mark in Classifier Group Configuration mode mark-de Policy List Configuration...

  • Page 24: Dhcp

    JUNOSe 10.0.3 Release Notes Deprecated Command Command Mode Preferred Command show ip dynamic-interface-prefix Privileged Exec, User Exec None show ip mirror interface Privileged Exec show secure policy-list show license l2tp-session User Exec, Privileged Exec None t1 lineCoding Controller Configuration None. This command never had any effect.

  • Page 25: Dhcp External Server

    Release 10.0.3 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. [Defect ID 180178] When the DHCP relay agent application and the DHCP external server application are configured in the same virtual router, using the ip dhcp-external server-sync command on an unnumbered IP interface does not function as expected.

  • Page 26: Dynamic Interfaces

    JUNOSe 10.0.3 Release Notes 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. DHCP external server is configured to create dynamic subscriber interfaces. When these three conditions exist simultaneously, the ES2 4G LM may not be able to successfully process all DHCP packets.

  • Page 27: Ethernet

    Release 10.0.3 Ethernet The hashing algorithm that selects the LAG member link is associated with the IP address of the subscriber client to support QoS. Consequently, a particular flow is always hashed to the same link. When a member link is removed from a LAG bundle, traffic rate is disrupted and traffic flow is reduced.

  • Page 28: Flash

    JUNOSe 10.0.3 Release Notes The show interface gigabitEthernet command output does not display the following line of output for Gigabit Ethernet modules that do not support SFPs, such as the GE Single Mode I/O module and GE I/O Multi Mode I/O modules: Primary/Secondary link signal detected Primary/Secondary link signal not detected Flash...

  • Page 29: Hdlc

    Release 10.0.3 PCMCIA NVS Card Caution Before you insert or remove PCMCIA NVS (flash) cards from a running CAUTION: router, we strongly recommend that you halt the SRP module or shut down the router. Failure to do this can result in file corruption in one or both cards. The 4XOC3 APS MULTIMODE and 4XOC3 APS SINGLE MODE I/O modules are incompatible with the following versions of the OCx/STMx ATM and OCx/STMx POS line modules:...
  • Page 30 JUNOSe 10.0.3 Release Notes 8.1.x, 8.2.x, and 9.x.x builds created before July 23, 2008 Examples of descriptions that are not retained across the upgrade: host1(config-if)#ip description 12345678 host1(config)#ip vrf 123 host1(config-vrf)#description 45678 Examples of descriptions that are retained across the upgrade: host1(config-if)#ip description longdescription host1(config)#ip vrf longername host1(config-vrf)#description 45678...

  • Page 31: Ipsec

    Release 10.0.3 When you issue the show ip forwarding-table command for a particular slot, it is normal and appropriate behavior when the Status field indicates Valid while the Load Errors field is increasing daily for that VR. The Load Errors field records any failed routing table distribution attempt as an error.

  • Page 32: Is-Is

    JUNOSe 10.0.3 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 33: Line Module Redundancy

    Release 10.0.3 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 34: 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 35: Policy Management

    Release 10.0.3 Typically, when configuring packet mirroring, you configure a static route to reach the analyzer device through the analyzer port. If the analyzer port is an IP-over-Ethernet interface, you must also configure a static Address Resolution Protocol (ARP) entry to reach the analyzer device. However, because only a single static ARP entry can be installed for a given address at any given time, when you are using equal-cost multipath (ECMP) links to connect to the analyzer device, the static ARP configuration does not provide failover if the...
  • Page 36 JUNOSe 10.0.3 Release Notes For example, if a policy had both a next-interface and a filter rule, then the next interface was applied. If a policy had a next-hop and a filter rule, then the filter rule was applied. Multiple forwarding rules behavior for Release 5.2.0 and higher-numbered releases: Beginning with Release 5.2.0, the multiple rules behavior is designed so that when a forwarding solution conflict occurs within a policy, such as...

  • Page 37: Ppp

    Release 10.0.3 The GE-2 line module does not support dynamic IP interfaces over static PPP interfaces when the PPPoE subinterface is also static. The OC3/STM1 GE/FE line module does not support dynamic IP interfaces over static PPP interfaces when the ATM interface column is also static. PPPoE On the ES2 4G LM, ES2 10G LM, and ES2 10G Uplink LM, data packets for PPPoE are not counted at the PPPoE interface.

  • Page 38: Radius

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

  • Page 39: Src Software And Sdx Software

    Release 10.0.3 Trap Name Expected Enterprise OID Enterprise OID Sent by SNMP Agent juniAddressPoolHighAddrUtil .1.3.6.1.4.1.4874.2.2.21.3 .1.3.6.1.4.1.4874.2.2.21.3.0 juniAddressPoolAbatedAddrUtil .1.3.6.1.4.1.4874.2.2.21.3 .1.3.6.1.4.1.4874.2.2.21.3.0 juniAddressPoolNoAddresses .1.3.6.1.4.1.4874.2.2.21.3 .1.3.6.1.4.1.4874.2.2.21.3.0 juniDhcpLocalServerPoolHighAddrUtil .1.3.6.1.4.1.4874.2.2.22.3 .1.3.6.1.4.1.4874.2.2.22.3.0 juniDhcpLocalServerPoolAbatedAddrUtil .1.3.6.1.4.1.4874.2.2.22.3 .1.3.6.1.4.1.4874.2.2.22.3.0 juniDhcpLocalServerPoolNoAddresses .1.3.6.1.4.1.4874.2.2.22.3 .1.3.6.1.4.1.4874.2.2.22.3.0 pimNeighborLoss .1.3.6.1.3.61.1 .1.3.6.1.3.61.1.0 Work-around: Use the OIDs that the SNMP agent sends. SRC Software and SDX Software When applying policies to interfaces that are managed by SRC, give careful consideration to using other policy management tools, such as CLI, RADIUS,...

  • Page 40: Stateful Srp Switchover (High Availability)

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

  • Page 41: Subscriber Interfaces

    Release 10.0.3 We recommend the following hold times for each protocol, based on the number of interfaces. Recommended Hold Time Recommended Hold Time Interface Count for OSPF for IS-IS 16000 or less 80 seconds 50 seconds 16001 to 32000 87 seconds 55 seconds 32001 to 48000 90 seconds...

  • Page 42: System Logging

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

  • Page 43: Known Problems And Limitations

    Release 10.0.3 Known Problems and Limitations When a mirror rule that triggers on username is employed for packet mirroring of dynamic IP subscribers over ATM, removal of the rule does not disable packet mirroring. [Defect ID 175356] Work-around: Use a mirror rule that triggers on account session ID rather than on username.
  • Page 44 JUNOSe 10.0.3 Release Notes When you use the no-authenticate keyword with the subscriber command to prevent subscriber authentication so that the subscriber information can be used for DHCP option 82, suboption 2, the SRP module can reset. This issue does not occur when you use the no-authenticate keyword with the subscriber command as a way to perform a RADIUS configuration.

  • Page 45: Bfd

    Release 10.0.3 The output of the show atm arp command displays only 4096 entries when the line module is configured with more than 4096 NBMA ARP entries. [Defect ID 68849] 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 46: Dhcp External Server

    JUNOSe 10.0.3 Release Notes The ip auto-detect ip-subscriber command is configured to enable packet detection (packet triggering) and to trigger creation of dynamic subscriber interfaces. 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.

  • Page 47: Ethernet

    Release 10.0.3 Ethernet When autonegotiation is enabled on GE interfaces with the speed automatically negotiate command, issuing the link selection command logs out subscribers. [Defect ID 87185] 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...

  • Page 48: Igmp

    JUNOSe 10.0.3 Release Notes host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 23 23 427 712 host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 22 22 101 110 Use fully overlapping ranges rather than partially overlapping ranges, as in the following example: host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 23 427 712 host1(config-if)#vlan bulk-config BulkCezarCnfg2 svlan-range 21 23 101 110 Ethernet statistics are incorrectly displayed for virtual port 8 of the ES2-S1 GE-8...

  • Page 49: Ipsec

    Release 10.0.3 IP interface statistics become inconsistent when a slot is reset, because some traffic (such as control traffic) might be destined for the SRP module and is therefore counted elsewhere. [Defect ID 26697] When a router configured with PIM on a virtual router undergoes multiple warm restarts, the router subsequently hangs when an IP profile is configured.

  • Page 50: Is-Is

    JUNOSe 10.0.3 Release Notes IS-IS IS-IS graceful restart (nonstop forwarding) does not work on the broadcast interface when the restarting router is the designated intermediate system (DIS). Graceful restart works properly when the restarting router is not the DIS. [Defect ID 61496] On a router configured with IS-IS and BFD, using the redundancy force srp command to force an SRP switchover sometimes brings down IS-IS and BFD.

  • Page 51: Mobile Ip

    Release 10.0.3 Mobile IP Traffic statistics for dynamic subscriber interfaces associated with mobile IP subscribers are not maintained as the subscribers move between mobile IP nodes. Consequently the reported interface statistics are only the values accumulated since the last time a mobile node moved. [Defect ID 174509] The clear ip mobile binding nai @realm command does not work.

  • Page 52: Multicast

    JUNOSe 10.0.3 Release Notes When you upgrade the router to JUNOSe Release 7.1.0 or a higher-numbered release from a release numbered lower than Release 7.1.0, remote ATM layer 2 over MPLS circuits (also known as MPLS shim interfaces) that use Martini encapsulation are erroneously signaled with the control word attribute setting “Control word is not preferred by default”.
  • Page 53 Release 10.0.3 If you have removed the last rule in a policy list, the router generates a warning only after you exit Policy List Configuration mode. If you have removed the last policy rule and then added a classifier group before you exit Policy List Configuration mode, the router does not generate a warning about removing the last rule.

  • Page 54: Pppoe

    JUNOSe 10.0.3 Release Notes When you enter the no ip policy-parameter hierarchical parameterName command or no ipv6 policy-parameter hierarchical parameterName command for a hierarchical policy-parameter type in Interface Configuration mode, the explicit reference of the parameter is removed successfully from the interface.

  • Page 55: Service Manager

    Release 10.0.3 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 you perform an SNMP walk of the juniQosQueueStatistics MIB, a timeout of up to 5 minutes ensues, during which the SRP module CPU utilization goes to 100 percent.

  • Page 56: Snmp

    JUNOSe 10.0.3 Release Notes show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier service-session serviceName This problem also occurs when a subscriber is authenticated using a RADIUS server for a combined IPv4 and IPv6 service in a dual stack. 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...

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

    Release 10.0.3 Stateful SRP Switchover (High Availability) and IP Tunnels 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.

  • Page 58: System Logging

    JUNOSe 10.0.3 Release Notes If your router is in Manual Commit mode, then you must issue the write memory command before you perform an SRP module switch or a manual reload. You must do this even when you have made no changes to the system configuration and the file systems are synchronized.

  • Page 59: Resolved Known Problems

    Release 10.0.3 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. [Defect ID 179975] Resolved Known Problems Release 10.0.3 is based on the 10.0.2p0-1 patch release and incorporates all problem resolutions found in that release.

  • Page 60: Dhcp Relay

    JUNOSe 10.0.3 Release Notes DhcpBasePlugIn::receivePacket() debugs displayed on line module for every DHCP packet received. [Defect ID 89934] SRP reset type: processor exception 0x300 task: dhcpRelay_dhcpRe doMacAddressChange [Defect ID 90059] SRP reset type: panic file: dhcpRelay.cc task: dhcpRelay_dhcpRe deleteMsnvRoutesWorker [Defect ID 90095] DHCP Relay SRP crash - reset type: panic task: dhcpRelay_dhcpRe file: dhcpRelay.cc line: 11249 [Defect ID 90123]...

  • Page 61: Hardware

    Release 10.0.3 ES2 10G LM experiencing memory leak in KTREE on LM10. [Defect ID 90088] LM10 leak in 24Byte STL pool object caused by rate-limits (Hw2LuTokenBucketNhDescriptorArrayFtii) [Defect ID 90155] Recovery for single-bit and double-bit ECC errors. [Defect ID 90242] EMEA:LM10 Reset: type: exception 0x700 (program); lr: Ktree::TwoWayBlockBase::adoptNextNode(bool, Ktree::Node * [Defect ID 90285] Hardware...

  • Page 62: Pppoe

    JUNOSe 10.0.3 Release Notes PPPoE When many PPPoE subscribers were attempting to reconnect on a line module, the RADIUS server experienced an outage. Some of the subscribers were unable to reconnect. Some subscribers recieved PADRs but no PADS could be sent. [Defect ID 90216] ES2 10G LM in slot 0 crashed - reset type: panic arg (0xda) file: templateRam.cc line: 305 [Defect ID 90093] Service Manager...

  • Page 63: Errata

    Release 10.0.3 Errata This section identifies errors found in the JUNOSe documentation. These errors are corrected in subsequent releases of the affected documentation. The Policy and QoS Maximums (for E120 and E320 routers) table in JUNOSe Release Notes, Appendix A, System Maximums for Releases 9.x, 10.x, and 11.0.x incorrectly states that the maximum number of policy classification (CLACL) entries for the ES2 10G Uplink LM is 131,171.
  • Page 64 JUNOSe 10.0.3 Release Notes Releases 9.2.0 and 9.2.1 Release 9.3.0 Release 10.0.0 The correct maximum number of SRC interfaces supported on the different ERX routers is as follows: 16,000 interfaces on the ERX310 router 32,000 interfaces on the ERX705 and ERX710 router 32,000 interfaces on the ERX1410 router 48,000 interfaces on the ERX1440 router The ERX Hardware Guide and E120 and E320 Hardware Guide fail to state the...
  • Page 65 Release 10.0.3 The Command-Line Editing Keys table in JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface fails to include the following key combinations: Ctrl+q—Resumes a Telnet or console session; use if the Telnet or console session appears frozen or unresponsive Ctrl+s—Suspends a Telnet or console session Esc+f—Moves the cursor forward one word In JUNOSe System Basics Configuration Guide, Chapter 4, Configuring SNMP, the...
  • Page 66 JUNOSe 10.0.3 Release Notes DHCP external server began supporting unified ISSU in JUNOSe Release 10.0.0. Therefore, you can perform unified ISSU even when the DHCP external server is configured on the virtual router for JUNOSe Release 10.0.0 and higher-numbered releases. The Monitoring Suspicious Control Flow section in JUNOSe System Basics Configuration Guide, Chapter 9, Passwords and Security, incorrectly contains a section titled show snmp interfaces.
  • Page 67 Release 10.0.3 The erroneous information appears in the following guides in the JUNOSe documentation set: JUNOSe Release 8.0.0—Reverting After a Failover section in JUNOSe Physical Layer Configuration Guide, Chapter 6, Configuring Ethernet Interfaces JUNOSe Releases 8.1.0, 8.2.0, and 9.0.0—Reverting After a Failover section in JUNOSe Physical Layer Configuration Guide, Chapter 5, Configuring Ethernet Interfaces JUNOSe Releases 9.1.0, 9.2.0, 9.3.0, and 10.0.0—Reverting After a Failover...
  • Page 68 JUNOSe 10.0.3 Release Notes The neighbor graceful-restart command section fails to state that using the no version of this command disables advertisement of the graceful restart capability for specified peers or peer groups only. The no form of this command does not affect global advertisement of the graceful restart capability.
  • Page 69 Release 10.0.3 The following tables replace the bulleted and numbered lists, which explain the process used for selection of address pools, in the Local Pool Selection and Address Allocation section under the Standalone Mode Overview main topic in JUNOSe Broadband Access Configuration Guide, Chapter 18, DHCP Local Server Overview.
  • Page 70 JUNOSe 10.0.3 Release Notes JUNOSe Broadband Access Configuration Guide, Chapter 19, Configuring DHCP Local Server fails to state the following additional information for the DHCP local server: Before you configure a DHCP local server, you must identify which mode to use (standalone DHCP mode or equal-access).
  • Page 71 Release 10.0.3 JUNOSe Broadband Access Configuration Guide, Chapter 2, Monitoring and Troubleshooting Remote Access, fails to include the following information for the output of the show radius servers command: If a RADIUS server was never configured on the virtual router, the command displays the following message: host1#show radius servers no radius servers configured...
  • Page 72 JUNOSe 10.0.3 Release Notes The JUNOSe Command Reference Guide A to M omits the following information for the interface loopback command: You cannot shut down a loopback interface. NOTE: We recommend that you configure a 32-bit subnet mask for the loopback interface.
  • Page 73 Release 10.0.3 The JUNOSe Command Reference Guide N to Z omits the following information for the qos-interface-parent command, beginning with JUNOSe Release 9.2.0 in which it was introduced: The qos-interface-parent command is available in Interface Configuration mode, as well as in QoS Interface Set Configuration and QoS Interface Superset Configuration modes.
  • Page 74 JUNOSe 10.0.3 Release Notes Errata...

  • 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 10.0.3 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 10.0.3 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 10.0.3 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 10.0.3 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 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 84 JUNOSe 10.0.3 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 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 10.0.3 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 10.0.3 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 10.0.3 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 10.0.3 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 10.0.3 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 10.0.3 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 10.0.3 Release Notes Table 9: Physical and Logical Density Maximums (continued) Feature E120 E320 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 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 10.0.3 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 or ES2 10G Uplink LM 128,000 128,000 (See Note 1 on page 91.)
  • 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 10.0.3 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 ES2-S1 GE-8 IOA 16,384 16,384 (with ES2 4G LM or ES2 10G LM) (See Note 5 on page 91.) ES2-S1 10GE IOA 16,384 16,384 (with ES2 4G LM) (See Note 5 on page 91.) ES2-S2 10GE PR IOA 4096...
  • Page 103 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 MLPPP bundles per line module The maximum number of MLPPP bundles supported per line module is the lesser of the maximum number of MLPPP bundles supported per chassis or of the maximum number of interfaces supported on the line module.
  • Page 104 JUNOSe 10.0.3 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 Transparent bridging and VPLS Bridge groups or VPLS instances per chassis 1024 1024 Bridge interfaces per line module in bridge groups or 8000 8000 VPLS instances Bridge interfaces per chassis in bridge groups or VPLS 32,000 32,000 instances...

  • 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 10.0.3 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 10.0.3 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 10.0.3 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Rate limiters (ingress) per line module ES2 4G LM 64,000 64,000 ES2 10G LM 64,000 64,000 ES2 10G Uplink LM 64,000 64,000 Policy statistics blocks (egress) per line module ES2 4G LM 256,000 256,000...

  • Page 111: Tunneling Maximums

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

  • Page 113: Subscriber Management Maximums

    Appendix A: System Maximums Subscriber Management Maximums Table 14 lists subscriber management maximums for the E120 router and the E320 router. The following notes are referred to in Table 14: 1. DHCP relay proxy maintains a list of active DHCP clients up to a maximum of 100,000 clients per chassis for all virtual routers.
  • Page 114 JUNOSe 10.0.3 Release Notes Table 14: Subscriber Management Maximums (continued) Feature E120 E320 DHCP relay and relay proxy client (See Notes 1 and 2 on page 105.) 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 115: 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 107 Module Name Cross-Reference Information Use Table 15 on page 107 to find the label name, software display name, and model number of a module.
  • Page 116 JUNOSe 10.0.3 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 117: 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 109 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the...
  • Page 118 JUNOSe 10.0.3 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 119 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 120: Monitoring The Status Of Transfer Of Updated Dsl Line Rate Parameters To The Cops Server

    JUNOSe 10.0.3 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 121: Junose Command Reference Guide Update

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

This manual is also suitable for:

Junose 10.0.3

Table of Contents