Copyright © 2010, Juniper Networks, Inc.
Known Behavior
31
Release 11.1.1
z
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.
z
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.
z
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.
PPP
z
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
z
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.
QoS
z
In JunosE Releases 7.1.x, 7.2.x, and 7.3.x, you can attach a QoS profile to Ethernet
interfaces that are configured in a link aggregation group (LAG) interface. However,
beginning with JunosE Release 8.0.1, you can attach a QoS profile directly to the LAG
interface. As of JunosE Release 8.0.1, the software restricts you from attaching a QoS
profile to any Ethernet interfaces that are members of a LAG. [Defect ID 84632]
Work-around
: Prior to upgrading from JunosE Releases 7.1.x, 7.2.x, or 7.3.x to JunosE
Release 8.0.x or higher-numbered releases, remove the QoS profile from the
Ethernet interface. When you have successfully upgraded to JunosE Release 8.0.x or
higher-numbered releases, reattach the QoS profile to the LAG interface.
