User manual JUNIPER NETWORKS JUNOSE FOR E SERIES BROADBAND SERVICES ROUTERS RELEASE NOTES 11.1.1

[. . . ] JunosE Software for E Series Broadband Services Routers TM TM Release Notes Release 11. 1. 1 Published: 2010-12-07 Copyright © 2010, Juniper Networks, Inc. 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 inPacketOctetDiscards counter in the output of the show atm vc atm interface vcd command includes both inBytesDropped and inBytesUnknownProtocol statistics. The inBytesUnknownProtocol statistics should be displayed by a separate counter. At the major interface level, the inPacketDiscards counter includes both inPacketsDropped and inPacketUnknownProtocol statistics. The inPacketUnknownProtocol statistics should be displayed by a separate counter. [Defect ID 44286] BFD 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). [Defect ID 174271] CLI When you issue a run show ppp command, the CLI changes the configuration level of the command line to Global Configuration mode rather than remaining at the level from which you issued the command. [Defect ID 52165] Work-around: Reissue the commands necessary to reenter the desired mode. The logout subscribers all command may not log out all of the DHCP subscribers. Although the bindings and DHCP addresses are cleared, the show subscribers summary command may display some of the DHCP subscribers. [Defect ID 180176] Work-around: Try using the dhcp delete-binding all command. If this does not clear the subscribers, you may want to reload the line module to avoid further issues. DHCP DHCP packets are not forwarded to the DHCP server over dynamically created interfaces when all of the following are true: [Defect ID 180343] - DHCP relay or DHCP relay proxy is configured on the router. - The client-facing interfaces are created dynamically using bridged Ethernet over static ATM PVCs. - 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 - Ensure that DHCP external server is configured in the virtual router. 38 Known Problems and Limitations Copyright © 2010, Juniper Networks, Inc. Release 11. 1. 1 - 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. DHCP External Server With the unique client ID option enabled, when two clients with the same MAC address or client ID are on an interface (where one client is connected over a router and relay and the other client is connected directly), sending a release request from one of the clients might terminate another client. [Defect ID 179759] The DHCP renew counter and release counter (displayed with the show ip dhcp-external statistics command) are doubled rather than incremented for each renew and release sent. [Defect ID 78802] When DHCP clients on an S-VLAN over bridged Ethernet stack configuration send a decline message to a router that has DHCP relay and DHCP external server configured in the same VR, the clients bindings are not removed from the DHCP external server. [Defect ID 87086] When DHCP relay and DHCP external server are configured in the same VR with server-sync enabled, bindings are not created in the DHCP external server when DHCP clients on an ATM bulk configuration interface stack and dynamic VLAN over Ethernet stack sends a renew message. [Defect ID 87087] DoS Protection A Telnet session closes when sending ipLocalBGP protocol traffic at a rate in the range 4096­4200 packets per second (pps) with suspicious control flow detection enabled. [Defect ID 81974] Work-around: When the traffic drops below 4096 pps, open a new Telnet session. Ethernet When autonegotiation is enabled on Gigabit Ethernet 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 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. [Defect ID 74104] Forwarding When performing MAC validation to match subscriber demux entries with ARP host entries, the ES2 10G LM does an exact match, rather than a longest prefix match. The subscriber demux entry source address must be a /32 value matching the IP address of an ARP entry in order to validate the MAC address against that ARP entry. [. . . ] The ES2-S1 Service IOA 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. For more information about supported L2TP sessions and tunnels, see JunosE Broadband Access Configuration Guide, Chapter 11, L2TP Overview. 2. Table 13: Tunneling Maximums Feature DVMRP (IP-in-IP) tunnels per chassis E120 4000 E320 4000 DVMRP (IP-in-IP) tunnels per line module with shared tunnel-server ports provisioned 4000 4000 DVMRP (IP-in-IP) tunnels per ES2-S1 Service IOA (See Note 1 on page 100. ) 4000 4000 GRE tunnels per chassis 4000 4000 GRE tunnels per line module with shared tunnel-server ports provisioned 4000 4000 GRE tunnels per ES2-S1 Service IOA (See Note 1 on page 100. ) 4000 4000 L2TP sessions per chassis (See Note 2 on page 100. ) 60, 000 60, 000 L2TP sessions per line module with shared tunnel-server ports provisioned (See Note 2 on page 100. ) 8000 8000 L2TP sessions per ES2-S1 Service IOA (See Note 2 on page 100. ) 16, 000 16, 000 L2TP tunnels per chassis for SRP-100 16, 000 16, 000 L2TP tunnels per chassis for SRP-320 with ES2 4G LM 32, 000 32, 000 L2TP tunnels per line module with shared tunnel-server ports provisioned (See Note 2 on page 100. ) 8000 8000 100 E120 and E320 System Maximums Copyright © 2010, Juniper Networks, Inc. Appendix A: System Maximums Table 13: Tunneling MaximumsTable continued on next page Feature L2TP tunnels per ES2-S1 Service IOA (See Note 1 and Note 2 on page 100. ) E120 16, 000 E320 16, 000 Copyright © 2010, Juniper Networks, Inc. E120 and E320 System Maximums 101 JunosE 11. 1. 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. [. . . ]