Table of Contents
Advertisement
PPP
PPPoE
QoS
In rare cases, some policy configurations that use CAM hardware classifiers
from releases earlier than Release 7.1.0 can fail because they exceed the total
hardware classifier entry size of 128 bits that was introduced in Release 7.1.0.
For more information and examples of previous configurations, see JUNOSe
Policy Management Configuration Guide, Chapter 8, Policy Resources.
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.
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.
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.
In Release 7.2.0 and higher-numbered releases, you can configure the simple
shared shaper to select scheduler nodes in a named traffic-class group as active
constituents.
By default, simple implicit shared shapers activate scheduler nodes in named
traffic-class groups. The implicit constituent selection process is now the same
for both simple and compound shared shapers.
This is a change in default behavior. For releases before Release 7.2.0, you
could not configure scheduler nodes as active constituents of the simple shared
shaper, except for the best-effort node.
To recover the default behavior available before Release 7.2.0, or to select
active constituents that are different, use simple explicit shared shapers to
select best-effort nodes only.
Release 10.2.2
29
Known Behavior
Advertisement
Table of Contents
