User manual JUNIPER NETWORKS JUNOSE 11.1.0 REV 4-29-2010

[. . . ] JUNOSeTM Software for E SeriesTM Broadband Services Routers Release Notes Release 11. 1. 0 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-04-29 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered 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. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. [. . . ] Do not configure a multicast group with more than 10, 219 outgoing interfaces (OIFS) on the same ES2 10G LM. [Defect ID 81768] 34 Known Behavior Release 11. 1. 0 Packet Mirroring The ES2 10G LM supports the packet mirroring feature when the module is paired with the ES2-S2 10GE PR IOA, the ES2-S1 GE-8 IOA, or the ES2-S3 GE-20 IOA. When you use the ES2 10G LM with these IOAs, CLI-based interface-specific mirroring is not supported. When both interface-specific mirroring and user-specific mirroring are configured on the same interface, the interface-specific secure policies take precedence. The interface-specific secure policies, which you manually attach using the CLI, override and remove any existing secure polices that were attached by a trigger action. If the interface-specific secure polices are subsequently deleted, the original trigger-based secure policies are not restored. 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 link being selected fails or is disconnected. Therefore, to provide continued connectivity if the link fails when using ECMP, enable the ip proxy-arp unrestricted command on the next-hop router for each ECMP interface. As a result, when the link fails, the router sends an ARP request to identify the MAC address of the analyzer device and gets a response over the new link. Policy Management The ES2 10G LM does not support the deprecated next-hop command. You cannot configure classifier lists that reference multiple fields for a VLAN policy list on the ES2 10G Uplink LM or the ES2 10G LM, with the exception of traffic-class and color. The system incorrectly classifies VLAN policies that classify using multiple fields. For example, an invalid policy list that references multiple fields uses both color and user-packet-class, or one classifier list using color and another using user-packet-class. In rare cases, some policy configurations that use CAM hardware classifiers from releases earlier than Release 7. 1. 0 can fail because they exceed the total hardware classifier entry size of 128 bits that was introduced in Release 7. 1. 0. For more information and examples of previous configurations, see JUNOSe Policy Management Configuration Guide, Chapter 8, Policy Resources. Multiple Forwarding Solution Rules for a Single Classifier List in a Policy Before Release 5. 2. 0, it was possible to configure a policy with multiple rules that specified forwarding solutions where all of these rules were associated with a single classifier list. Beginning with Release 5. 2. 0, the CLI no longer accepts this configuration. Multiple forwarding rules behavior for releases numbered lower than Release 5. 2. 0: Known Behavior 35 JUNOSe 11. 1. 0 Release Notes If multiple forward or filter rules were configured to reference the same classifier list in a single policy, then all rules except the first rule configured were marked as eclipsed in the show policy command display. If a policy were configured with one rule from the [forward, filter] pair and one rule from the [next-hop, next-interface] pair, and if both rules referenced the same classifier list, then no visible eclipsed marking occurred. However, these two rules were mutually exclusive, and only one of them defined the forwarding behavior. The rule action that was applied was in the order (from highest to lowest preference): next interface, filter, next hop, forward. [. . . ] These values are subject to limitations on available SRP module memory, which varies according to your router configuration. Depending on your configuration, the router may support more routing table entries or fewer routing table entries than this value. In any case, you can choose to limit the number of routes that can be added to the routing table on a per-VR or per-VRF basis by means of the maximum routes command. The maximum number of ANCP adjacencies can be scaled over a maximum of 100 virtual routers. [. . . ]