Known Behavior
31
Release 11.0.2
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)#
PPP
The GE-2 line module does not support dynamic IP interfaces over static PPP
interfaces when the PPPoE subinterface is also static. The OC3/STM1 GE/FE
line module does not support dynamic IP interfaces over static PPP interfaces
when the ATM interface column is also static.
PPPoE
On the ES2 4G LM, ES2 10G LM, and ES2 10G Uplink LM, data packets for
PPPoE are not counted at the PPPoE interface. Instead, PPPoE data packets are
counted at the PPP interface that sits on the PPPoE interface. Use the
show
ppp interface
command to display the data packets. Control packets for PPPoE
are counted at the PPPoE interface; use the
show pppoe interface
command
to display the control packets.
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.
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.
