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

Copyright © 2010, Juniper Networks, Inc.
Example 2—In this example, three forwarding solution conflicts result in rules being
overwritten. The filter rule is the last rule configured, and is therefore applied.
host1(config)#policy-list bostTwo
host1(config-policy-list)#forward classifier-group clacl5
host1(config-policy-list)#next-hop 1.1.1.1 classifier-group clacl5
WARNING: This rule has replaced a previously configured rule.
host1(config-policy-list)#next-interface atm 1/0.0 classifier-group clacl5
WARNING: This rule has replaced a previously configured rule.
host1(config-policy-list)#filter classifier-group clacl5
WARNING: This rule has replaced a previously configured rule.
host1(config-policy-list)#exit
host1(config)#
Informational Note:
When you upgrade the nonvolatile memory to Release 5.2.0 or
later, the upgrade removes eclipsed rules and rules whose behavior was not applied in
the previous release. This removal ensures that the postupgrade forwarding behavior
is the same as the preupgrade behavior.
Informational Note: If you upgrade to Release 5.2.0 or later and then configure your
router using a script generated before Release 5.2.0, the postupgrade and preupgrade
forwarding behaviors might not be the same. The new Release 5.2.0 configuration
behavior is applied—the last policy rule configured for a given classifier list that
specifies a forwarding behavior is the only rule remaining.
In JunosE Release 11.0.0 and higher-numbered releases, you must specify at least

one option by which the router defines a packet flow in order to configure classifier
control lists (CLACLs) for policy lists to be attached to VLAN interfaces. Although a
carriage return, <cr>, is displayed when you type a question mark (?) after entering
the vlan classifier list classifierName command without defining any other keyword
or CLACL option, an error message is displayed when you press Enter to configure the
VLAN CLACL with only the name. The error message states that a VLAN classifier list
cannot be configured without any classification criteria, such as color, traffic class,
user packet class, or user priority. You must specify at least one keyword or option to
configure VLAN CLACL successfully. [Defect ID 184139].
In JunosE releases earlier than Release 11.0.0, you could configure all CLACLs (except
those CLACLs that were attached to IP interfaces) without specifying an option or a
keyword. Because the policy management application treats only one default
classifier group (configured with an * in the policy list) as a valid setting, this
functionality change ensures that only one classifier that matches all packets can be
present in a VLAN policy list definition.
When you attach a policy to an interface and the policy contains a classifier rule that

is unsupported for that interface, the CLI generates a message and the policy is
applied. However, if an existing policy is already attached to that interface, then
support for the new policy is not checked and the invalid policy is applied to the
interface without warning. The results of this attachment are not predictable.
No logs are created if you use the policy-list option with the log severity

severityValue policyMgrPacketLog policy-list policyListName command when
logging policyMgrPacketLog events.
Release 11.3.0
Known Behavior 33