JUNOSe 11.1.0 Release Notes
38
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. [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.
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.
RADIUS
JUNOSe Software provides extended commands for configuring the formats of
the RADIUS NAS-Port attribute (attribute 5) and the RADIUS Calling-Station-ID
attribute (attribute 31) when the physical port value is greater than 7.
When the physical port value is greater than 7:
An incorrectly configured NAS-Port attribute format results if you use either
the
radius nas-port-format 0ssssppp
or
radius nas-port-format ssss0ppp
command.
An incorrectly configured Calling-Station-ID attribute results if you use
either the
radius calling-station-format fixed-format
command or the
radius calling-station-format fixed-format-adapter-embedded
command.
Work-around
: Use the following commands on routers that have line modules
with more than 7 physical ports:
