JunosE 11.0.2 Release Notes
30
Known Behavior
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. 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.
