User manual JUNIPER NETWORKS JUNOSE SOFTWARE 10.3.2 RELEASE NOTES 9-29-2010

[. . . ] JunosETM Software for E SeriesTM Broadband Services Routers Release Notes Release 10. 3. 2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-09-29 Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. [. . . ] You cannot delete the ipInterface log after you delete the corresponding IP interface. This does not prevent you from adding filters to other interfaces, nor does it prevent you from adding a filter to the same interface if you re-create it after deletion. [Defect ID 34842/45063] Work-around: Remove the filter before you remove the interface. Alternatively, if you remove the interface first, then you must remove all filters associated with all IP interfaces. System Logging If you enable engineering logs and set the control network logs to a level of notice or lower (down from the default of error), you might see erroneous controlNetwork log messages like the following that are generated because SNMP polling on line modules (correctly) detects no fabric: [Defect ID 43168] NOTICE 09/01/2002 18:47:52 CEST controlNetwork (slot 11): Control Bus Master slave error 0x5 while accessing slot Tunneling When you configure the GE-2 line module, the GE-HDE line module, or the ES2-S1 GE-4 IOA to operate as a shared tunnel-server module, the available bandwidth for tunnel services is limited to 0. 5 Gbps per module. 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. 34 Known Behavior Release 10. 3. 2 Known Problems and Limitations This section identifies the known problems and limitations in this release. For more information about known problems that were discovered at customer sites, you can log in to the JunosE Knowledge Base at https://www2. juniper. net/kb/, enter the defect ID number in the Search by Keyword field, and click Search. ANCP On an E320 router that has established 3000 ANCP adjacencies with a client and traffic is initiated, the following behavior occurs sporadically: All existing Telnet sessions are disconnected and no new Telnet sessions can be established for several minutes. [Defect ID 83872] ATM When 16, 000 PPPoA interfaces are configured on an OCx/STMx ATM line module paired with an OC3-4 I/O module in an ERX14xx model, ERX7xx model, or ERX310 router, Ping traffic passing through the line module on the restarting router experiences an outage of 103 seconds, which is beyond the maximum limit, after a unified ISSU from JunosE Release 9. 2. 0p1-0 to 9. 3. 0b0-12. This outage does not occur when the same configuration is applied on a Gigabit Ethernet interface. [Defect ID 179794] When you reload an ATM line module that is configured with NBMA circuits as passive OSPF interfaces and that has established OSPF adjacencies and IBGP peers (configured on Gigabit Ethernet interfaces), the transmission of OSPF hello packets might be affected until all the NBMA interfaces have initialized. [Defect ID 46157] Work-around: Either remove the passive OSPF interface statements on the NBMA interfaces, or statically configure the OSPF cost on the NBMA interfaces. 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. The ATM peak cell rate (PCR) does not appear in the L2TP Calling Number AVP for the first PPP session when the ATM shaping parameters were configured by RADIUS return attributes. [Defect ID 60933] 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. [Defect ID 67157] 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] Known Problems and Limitations 35 JunosE 10. 3. 2 Release Notes When you use the no-authenticate keyword with the subscriber command to prevent subscriber authentication so that the subscriber information can be used for DHCP option 82, suboption 2, the SRP module can reset. This issue does not occur when you use the no-authenticate keyword with the subscriber command as a way to perform a RADIUS configuration. [Defect ID 69865] When you perform an snmpWalk on the juniAtmSubIfVccTable, a response is received for only a few of the total configured ATM subinterfaces when both of the following are true: the router has a line module that has some ATM-related configuration and the line module is in the disabled state. [Defect ID 80020] The baseline interface atm command fails for a VCD assigned by the router to F4 OAM circuits. [. . . ] There is no per-VR limit; all multicast routes can be on a single VR or present across multiple VRs. The maximum number of interfaces can be achieved by any combination; for example, two streams each being replicated to 32, 768 interfaces; 16, 384 streams each being replicated four times; or any other combination. Table 11: Routing Protocol Maximums Feature BFD Sessions per line module for ES2 4G LM Sessions per line module for all modules other than ES2 4G LM 100 50 100 50 E120 E320 100 E120 and E320 System Maximums Appendix A: System Maximums Table 11: Routing Protocol Maximums (continued) Feature ECMP maximum paths to a destination BGP, IS-IS, MPLS, OSPF, RIP 16 16 E120 E320 IPv4 forwarding table entries per chassis (See Note 1 on page 100. ) 1, 048, 576 1, 048, 576 IP network interfaces (IPv4 and IPv6) Per chassis (See Note 2 on page 100. ) Per ES2 4G LM Per ES2 10G LM Per ES2 10G ADV LM Per ES2 10G Uplink LM 16, 000 16, 000 32, 000 8000 16, 000 16, 000 32, 000 8000 64, 000 96, 000 IPv4 routing protocol scaling and peering densities (See Note 3 on page 100. ) Routing table entries (See Note 4 on page 100. ) ANCP Adjacency Scaling (See Note 5 on page 100. ) BGP-4 peering sessions BGP-4 routes (NLRI) IP next hops (egress FECs); used to represent the IP addresses of next-hop routers on Ethernet interfaces MPLS next hops (egress FECs) when graceful restart is not enabled MPLS next hops (egress FECs) when graceful restart is enabled MPLS forwarding entries when graceful restart is not enabled MPLS forwarding entries when graceful restart is enabled IS-IS adjacencies IS-IS routes MPLS LDP LSPs when graceful restart is not enabled MPLS LDP LSPs when graceful restart is enabled 3000 1, 500, 000 1, 000, 000 500, 000 250, 000 64, 000 32, 000 150 20, 000 10, 000 5000 3000 1, 500, 000 1, 000, 000 500, 000 250, 000 64, 000 32, 000 150 20, 000 10, 000 5000 10, 000 5000 1000 25, 000 5000 5000 500, 000 500, 000 MPLS RSVP-TE LSPs when graceful restart is not enabled 10, 000 MPLS RSVP-TE LSPs when graceful restart is enabled OSPF adjacencies OSPF routes 5000 1000 25, 000 E120 and E320 System Maximums 101 JunosE 10. 3. 2 Release Notes Table 11: Routing Protocol Maximums (continued) Feature IPv6 routing table entries (See Note 3 on page 100. ) E120 100, 000 E320 100, 000 J-Flow statistics J-Flow­enabled VRs and VRFs, in any combination Sampled interfaces per VR or VRF Total sampled Interfaces per chassis 16 32 512 16 32 512 Martini circuits for layer 2 services over MPLS Total Martini circuits per line module Total Martini circuits per chassis (See Note 6 on page 100. ) External Martini circuits per chassis 16, 000 32, 767 32, 767 16, 000 16, 000 16, 000 32, 767 Internal Martini circuits (local cross-connects) per chassis 16, 000 Mobile IP bindings per chassis ­ 96, 000 Multicast routes (IPv4 and IPv6) Forwarding entries [(S, G) pairs] per chassis (See Note 7 on page 100. ) Outgoing interfaces per chassis (See Note 8 on page 100. ) 65, 536 65, 536 16, 384 16, 384 Response Time Reporter simultaneous operations per VR 500 500 Response Time Reporter maximum tests per chassis (SRP-100 or SRP-320) ­ 500 Response Time Reporter maximum tests per virtual router (SRP-100 or SRP-320) ­ 100 VRRP VRIDs per line module See Ethernet VRRP VRIDs per line module on page 98. See Ethernet VRRP VRIDs per line module on page 98. 102 E120 and E320 System Maximums Appendix A: System Maximums Policy and QoS Maximums Table 12 lists policy and QoS maximums for the E120 router and the E320 router. The following notes are referred to in Table 12: 1. For more information about system resource requirements for nodes, queues, and shadow nodes, see JunosE Quality of Service Configuration Guide, Chapter 15, QoS Profile Overview. [. . . ]