Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - RELEASE NOTES 2010-11-09 Release Note page 40

JunosE 11.3.0 Release Notes
32 Known Behavior
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. This typically was a configuration error, but the CLI accepted it.
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:
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.
Next-interface and next-hop rules were treated in the same manner. The
eclipsed rules were not applied.
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. The applied rule was the rule whose behavior was seen by
forwarded packets.
For example, if a policy had both a next-interface and a filter rule, then the
next interface was applied. If a policy had a next-hop and a filter rule, then
the filter rule was applied.
 Multiple forwarding rules behavior for Release 5.2.0 and higher-numbered
releases:
Beginning with Release 5.2.0, the multiple rules behavior is designed so that
when a forwarding solution conflict occurs within a policy, such as those
described earlier, the second forwarding solution overwrites the preceding
solution. That is, the last forwarding rule configured for the given classifier list
within a policy is the forwarding behavior that is used. Also, a warning message
is now displayed when this type of conflict occurs.
Example 1—In this example, the filter rule action overwrites the forward rule, and is
therefore applied.
host1(config)#policy-list wstPolicyList
host1(config-policy-list)#forward classifier-group svaleClacl1
host1(config-policy-list)#filter classifier-group svaleClacl1
WARNING: This rule has replaced a previously configured rule.
host1(config-policy-list)#exit
host1(config)#
Copyright © 2010, Juniper Networks, Inc.