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. 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. Juniper Networks assumes no responsibility for any inaccuracies in this document. [. . . ] 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] The baseline interface atm command fails for a VCD assigned by the router to F4 OAM circuits. [Defect ID 174482] Unified ISSU is not supported when ILMI is configured on ATM interfaces. [Defect ID 176007/177297/177122] ATM line modules reset after unified ISSU completes at the LAC when an MLPPP bundle with three links are tunneled to the LNS. [Defect ID 178821] Copyright © 2010, Juniper Networks, Inc. Known Problems and Limitations 37 JunosE 11. 1. 1 Release Notes For PPPoE, the AAL5 inPacket Discards counter might increment erroneously during call setup when a packet is passed directly to PPPoE for negotiation rather than being discarded. [Defect ID 51757] Work-around: Incremental InPacketDiscards during call setup do not necessarily indicate a problem. However, we recommend you investigate an excessive count because that might indicate a connection that cannot be successfully brought up for some reason, such as RADIUS denials or improper configuration. 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. [. . . ] For all line modules the maximum number of IPv4 or IPv6 or VLAN policy attachments is determined by the maximum number of interfaces multiplied by the number of attachment resources that are currently used. The line modules support policy attachments based on the following considerations: - IPv4--Up to 2 ingress policy attachments and 1 egress policy attachment - Secure policy--Up to 1 ingress policy attachment and 1 egress policy attachment (ES2 10G LM and ES2 10G ADV LM only) - IPv6--Up to 2 ingress policy attachments and 1 egress policy attachment - IPv4 secure policy--The ES2 4G LM, the ES2 10G LM, and the ES2 10G ADV LM support up to 1 ingress policy attachment and 1 egress policy attachment - IPv6 secure policy--The ES2 4G LM supports up to 1 ingress policy attachment and 1 egress policy attachment - VLANs--Up to 1 ingress policy attachment and 1 egress policy attachment 3. IPv6 secure policies are not supported on the ES2 10G LM. 2. Table 12: Policy and QoS Maximums Feature QoS queues per line module (See Note 1 on page 96. ) E120 128, 000 E320 128, 000 QoS profiles configurable per chassis 1000 1000 QoS profile attachments per chassis 96, 000 96, 000 QoS profile attachments per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM 16, 000 16, 000 32, 000 16, 000 16, 000 32, 000 96 E120 and E320 System Maximums Copyright © 2010, Juniper Networks, Inc. Appendix A: System Maximums Table 12: Policy and QoS MaximumsTable continued on next page Feature QoS scheduler nodes per line module E120 64, 000 E320 64, 000 QoS shapers per line module 64, 000 64, 000 Classification rules per policy 512 512 Policy classification (CLACL) entries per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 256, 000 262, 143 131, 071 65, 535 256, 000 262, 143 131, 071 65, 535 Policy egress interface attachments per line module (See Note 2 on page 96. ) ES2 4G LM combined IP and IPv6 interface attachments ES2 4G LM combined ATM, GRE, L2TP (LAC only), MPLS, and VLAN interface attachments ES2 10G LM combined IP and IPv6 interface attachments ES2 10G LM VLAN interface attachments ES2 10G ADV LM IP interface attachments ES2 10G ADV LM VLAN interface attachments ES2 10G Uplink LM combined IP and IPv6 interface attachments ES2 10G Uplink LM VLAN interface attachments 8191 8191 16, 383 16, 383 32, 000 32, 000 32, 000 32, 000 16, 383 16, 383 16, 383 16, 383 16, 383 16, 383 16, 383 16, 383 Policy ingress interface attachments per line module (See Note 2 on page 96. ) ES2 4G LM combined IP and IPv6 interface attachments ES2 4G LM combined ATM, GRE, L2TP (LAC only), MPLS, and VLAN interface attachments ES2 10G LM IP interface attachments ES2 10G LM VLAN interface attachments 16, 383 16, 383 16, 383 16, 383 16, 383 16, 383 32, 767 32, 767 Copyright © 2010, Juniper Networks, Inc. E120 and E320 System Maximums 97 JunosE 11. 1. 1 Release Notes Table 12: Policy and QoS MaximumsTable continued on next page Feature ES2 10G ADV LM IP interface attachments ES2 10G ADV LM VLAN interface attachments ES2 10G Uplink LM IP interface attachments ES2 10G Uplink LM VLAN interface attachments 8191 8191 16, 383 16, 383 32, 000 32, 000 E120 64, 000 E320 64, 000 Rate limiters (egress) per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 Rate limiters (ingress) per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 64, 000 Policy statistics blocks (egress) per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 256, 000 256, 000 512, 000 256, 000 256, 000 256, 000 512, 000 256, 000 Policy statistics blocks (ingress) per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 256, 000 256, 000 512, 000 256, 000 256, 000 256, 000 512, 000 256, 000 Parent groups (egress) per line module ES2 4G LM ES2 10G LM (internal parent groups only) ES2 10G ADV LM (internal parent groups only ES2 10G Uplink LM (internal parent groups only) 8191 8191 8191 8191 49, 151 8191 49, 151 8191 98 E120 and E320 System Maximums Copyright © 2010, Juniper Networks, Inc. Appendix A: System Maximums Table 12: Policy and QoS MaximumsTable continued on next page Feature Parent groups (ingress) per line module ES2 4G LM ES2 10G LM (internal parent groups only) ES2 10G ADV LM (internal parent groups only ES2 10G Uplink LM (internal parent groups only) 8191 8191 8191 8191 49, 151 8191 49, 151 8191 E120 E320 Software lookup blocks per line module ES2 4G LM ES2 10G LM ES2 10G ADV LM ES2 10G Uplink LM 16, 383 16, 383 32, 000 16, 383 16, 383 16, 383 32, 000 16, 383 Secure policies (for packet mirroring) Per chassis Per line module (See Note 3 on page 96. ) 2400 1022 2400 1022 Copyright © 2010, Juniper Networks, Inc. E120 and E320 System Maximums 99 JunosE 11. 1. 1 Release Notes Tunneling Maximums Table 13 lists tunneling maximums for the E120 router and the E320 router. 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. [. . . ]