Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
By making a hierarchical policer a
within a logical interface. A hierarchical policer configured as a
supports aggregation within a physical interface. Please note that you still apply the
hierarchical policer at the interface and traffic of the families that do not have the
hierarchical policer will be policer. This is different from IQE PICs, where you apply a
hierarchical policer at the logical or physical interface.
For hierarchical policing of all traffic through a logical interface, a hierarchical policer
can be made a
logical-interface-policer
Similarly, you can achieve aggregation at the physical interface level.
[Network Interfaces, Class of Service, Policy]
DSCP classification for VPLS at the ingress PE (M320 with Enhanced Type III FPC
and M120)—Enables you to configure DSCP classification for VPLS at an ingress PE
for encapsulation types
vlan-vpls
define the DSCP classifier at the [
hierarchy level and apply the DSCP classifier at the [
unit-logical-unit-number classifiers]
in the routing instance.
[Class of Service]
Traffic Control Profile (TCP) support at the FRF.16 physical interface level—FRF.16
bundle interfaces support multiple data-link connection identifiers (DLCIs). The
bandwidth of each of these DLCIs was previously limited to one of the following:
An aggregate value based on the number of DLCIs under the FRF.16 interface
A specific percentage through a traffic control profile (TCP) configuration applied
at the logical interface level
When there is a small proportion of traffic or no traffic on an individual DLCI, the
respective member link interface bandwidth is underutilized. Support for TCP features
on the FRF.16 bundle (physical) interface level in Junos OS Release 10.4R2 addresses
this limitation. The supported features include:
Peak Information Rate (PIR)
scheduler-map
delay-buffer
To enable traffic control profiles to be applied at FRF.16 bundle (physical) interface
level, disable the per-unit scheduler, which is enabled by default, by including the
statement at the
no-per-unit-scheduler
To specify traffic control profile features applicable to FRF.16 bundle physical interfaces,
include the
,
shaping-rate
delay-buffer-rate
class-of-service traffic-control-profiles profile-name]
and
delay-buffer-rate
must be specified as a percentage.
To apply the TCP configuration to an FRF.16 bundle (physical) interface, include the
output-traffic-control-profile
interface-name]
hierarchy level.
logical-interface-policer
and applied to all families in the logical interface.
(IQ2 or IQ2E PICs) or
edit class-of-service classifiers dscp dscp-name
edit interfaces at-fpc-pic-port
hierarchy level. The ATM interface must be included
[edit interfaces interface-name]
, and
scheduler-map
hierarchy level. The
statement at the
[edit class-of-service interfaces
, you can achieve aggregation
physical-interface-policer
. To configure,
ATM II IQ PIC
]
hierarchy level.
statements at the
[edit
shaping-rate
7
Advertisement
Table of Contents
