JunosE 11.0.2 Release Notes
32
Known Behavior
QoS
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.
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.
When you are configuring compound shared shaping using explicit
constituents and you explicitly specify both a scheduler node and a queue
stacked above the node as constituents of the shared shaper, the system selects
the scheduler node (but not the queue) as the constituent.
The router cannot resolve inconsistent requests caused by two QoS profiles
that modify the same scheduler property inconsistently. [Defect ID 61485]
Work-around
: Avoid using two QoS profiles that modify the same scheduler
property inconsistently, such as setting different values for the shaping rate for
the same S-VLAN node.
When you perform an SNMP walk of the juniQosQueueStatistics MIB, a timeout
of up to 5 minutes ensues, during which the SRP module CPU utilization goes
to 100 percent. [Defect ID 62252]
Egress strict-priority packets may experience high latency on OC3/STM1 ATM
interfaces associated with the LM if you have shaped the port rate to more than
148.5 Mbps. [Defect ID 80378]
Work-around
: To ensure low strict-priority latency, shape the port rate to no
more than 148.5 Mbps.
