JunosE 11.1.1 Release Notes
30
Known Behavior
Copyright © 2010, Juniper Networks, Inc.
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)#
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.
