■
Distribute excess bandwidth among different services for a subscriber (MX
Series routers with Trio MPC/MIC interfaces)
—Service providers often use
tiered services that must carry excess bandwidth as traffic patterns vary. By
default, excess bandwidth between a configured guaranteed rate and shaping
rate is shared equally among all queues, which might not be optimal for all
subscribers to a service. You can control the distribution of this excess bandwidth
with the
excess-rate
statement. To configure the excess rate for a traffic control
profile, include the
excess-rate
statement at the
[edit class-of-service
traffic-control-profiles
tcp-name
]
hierarchy level and apply the traffic control profile
at the
[edit interfaces]
hierarchy level. To configure the excess rate for a queue,
include the
excess-rate
and
excess-priority
statements at the
[edit class-of-service
scheduler
scheduler-name
]
hierarchy level.
[
Class of Service
]
■
Scheduler node scaling (MX Series routers with Trio MPC/MIC interfaces)
—The
hardware supports multiple levels of scheduler nodes. In per-unit-scheduling
mode, each logical interface (unit) can have four or eight queues and has a
dedicated level 3 scheduler node. The logical interfaces share a common level
2 node (one per port). In hierarchical-scheduling mode, a set of logical interfaces,
each with four or eight queues, has a level 2 CoS profile and one of its logical
interface children has a level 3 CoS profile. To better control system resources
in hierarchical-scheduling mode, you can limit the number of hierarchical levels
in the scheduling hierarchy to two. In this case, all logical interfaces and interface
sets with CoS profiles share a single (dummy) level 2 node, thereby increasing
the maximum number of logical interfaces with CoS profiles (the interface sets
must be at level 3). To configure scheduler node scaling, include the
maximum-hierarchy-levels
statement at the
[edit interfaces xe-
fpc
/
pic
/
port
hierarchical-scheduler]
hierarchy level. The only supported value is 2.
[
Class of Service
,
Network Interfaces
]
■
Forwarding-class aliases (M320 and T Series routers)
—Enable you to configure
up to 16 forwarding classes and 8 queues, with multiple forwarding classes
assigned to single queues. To configure, include the
class
and
queue-num
statements at the
[edit class-of-service forwarding-classes]
hierarchy level.
[
Class of Service
]
■
VLAN shaping on aggregate devices (MX Series routers with Trio MPC/MIC
interfaces)
—VLAN shaping (per-unit scheduling) is supported on aggregated
Ethernet interfaces when link protection is enabled on the aggregated Ethernet
interface. When VLAN shaping is configured on aggregate Ethernet interfaces
with link protection enabled, the shaping is applied to the active child link. To
configure link protection on aggregated Ethernet interfaces, include the
link-protection
statement at the
[edit interfaces ae
x
aggregated-ether-options]
hierarchy level. Traffic passes only through the designated
primary
link. This
includes transit traffic and locally generated traffic on the router. When the
primary link fails, traffic is routed through the backup link. You also can reverse
traffic, from the designated backup link to the designated primary link. To revert
back to sending traffic to the primary designated link when traffic is passing
through the designated backup link, use the
revert
command; for example,
request
interfaces revert ae0
. To configure a primary and a backup link, include the
primary
and
backup
statements at the
[edit interfaces ge-
fpc
/
pic
/
port
gigether-options 802.3ad ae
x
]
hierarchy level or the
[edit interfaces xe-
fpc
/
pic
/
port
fastether-options 802.3ad ae
x
]
hierarchy level. To disable link protection, delete
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
7
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
