JUNOSe 11.0.1 Release Notes
30
Known Behavior
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)#
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.
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.
