User manual JUNIPER NETWORKS JUNOSE 11.0.2 RELEASE NOTES

[. . . ] JunosETM Software for E SeriesTM Broadband Services Routers Release Notes Release 11. 0. 2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-11-09 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. [. . . ] The SNMPv1-formatted versions of the following Juniper Networks traps incorrectly contain . . . x. y. z. 0 in the SNMPv1-Trap-PDU enterprise field. That is, a zero is mistakenly appended to the correct enterprise OID value. Trap Name junidApsEventSwitchover junidApsEventModeMismatch junidApsEventChannelMismatch junidApsEventPSBF junidApsEventFEPLF juniAddressPoolHighAddrUtil juniAddressPoolAbatedAddrUtil juniAddressPoolNoAddresses juniDhcpLocalServerPoolHighAddrUtil juniDhcpLocalServerPoolAbatedAddrUtil juniDhcpLocalServerPoolNoAddresses pimNeighborLoss Expected Enterprise OID . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 3. 61. 1 Enterprise OID Sent by SNMP Agent . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 3. 61. 1. 0 Work-around: Use the OIDs that the SNMP agent sends. 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. [Defect ID 61232] 34 Known Behavior Release 11. 0. 2 SRC Software and SDX Software The SRC client does not prevent you from changing the name of the router while the client is connected to the SAE, resulting in SAE issues such as lost IP addresses and stale users. [Defect ID 77102] Work-around: To change the router name while the SRC client is connected to the SAE, shut down the SRC client, change the name, then re-enable the SRC client. SSH 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. You must manually re-enable SSH either by accessing the console VTY or creating a Telnet session to the router. Stateful SRP Switchover (High Availability) When IP tunnels are configured on a router enabled for stateful SRP switchover, and the Service Module (SM) carrying these tunnels is reloaded, stateful SRP switchover transitions to the pending state. Stateful SRP switchover remains in the pending state for 10 minutes following the successful reloading of the SM. This amount of time allows for IP tunnel relocation and for the tunnels to become operational again on the SM. If an SRP switchover occurs while in the pending state, the router performs a cold restart. 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. NOTE: Rapid call setup rates are most important following an outage that causes all subscribers to drop, because many of the dropped subscribers will immediately attempt to reconnect. This type of outage occurs far less frequently with stateful SRP switchover. We have ongoing development activities to characterize and improve call setup rates in future releases. Stateful SRP switchover remains inactive for 20 minutes after an initial cold-start or cold-restart of the router. This delay enables the system to reach a stable configuration before starting stateful SRP switchover. If you want to override the 20-minute timer, turn high availability off by using the mode file-system-synchronization command, and then on again by using the mode high-availability command. Known Behavior 35 JunosE 11. 0. 2 Release Notes After a stateful SRP switchover, each layer of the interface columns must reconstruct its interfaces from the mirrored information. While the interfaces are being reconstructed the SRP module cannot send or receive frames, including the protocol frames that signal graceful restart behavior with OSPF and IS-IS peers. If the configured hold time is too short, peers might mistakenly declare the adjacency down during the time in which the graceful restart is taking place. [Defect ID 65132] 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. [. . . ] 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 E120 and E320 System Maximums 99 JunosE 11. 0. 2 Release Notes 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 99. ) 1, 048, 576 1, 048, 576 IP network interfaces (IPv4 and IPv6) Per chassis (See Note 2 on page 99. ) 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 99. ) Routing table entries (See Note 4 on page 99. ) ANCP Adjacency Scaling (See Note 5 on page 99. ) 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 100 E120 and E320 System Maximums Appendix A: System Maximums Table 11: Routing Protocol Maximums (continued) Feature IPv6 routing table entries (See Note 3 on page 99. ) 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 99. ) 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 99. ) Outgoing interfaces per chassis (See Note 8 on page 99. ) 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 97. See Ethernet VRRP VRIDs per line module on page 97. E120 and E320 System Maximums 101 JunosE 11. 0. 2 Release Notes Policy and QoS Maximums Table 12 lists policy and QoS maximums for the E120 router and the E320 router. The following notes are referred to in Table 12: 1. For more information about system resource requirements for nodes, queues, and shadow nodes, see JunosE Quality of Service Configuration Guide, Chapter 15, QoS Profile Overview. [. . . ]