Config Guide Hierarchical Cos

®
Junos OS
Hierarchical Class of Service User Guide
Published
2020-03-18
ii
Juniper Networks, Inc.

1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks
are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right
to change, modify, transfer, or otherwise revise this publication without notice.
®
Junos OS Hierarchical Class of Service User Guide
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
iii
Table of Contents
About the Documentation | xiv
Documentation and Release Notes | xiv
Using the Examples in This Manual | xiv
Merging a Full Example | xv
Merging a Snippet | xvi
Documentation Conventions | xvi
Documentation Feedback | xix
Requesting Technical Support | xix
Self-Help Online Tools and Resources | xx
Creating a Service Request with JTAC | xx
1 Hierarchical Class of Service

Configuring Hierarchical Class of Service on MX Series 5G Universal Routing
Platforms | 2
Hierarchical Class of Service Overview | 2
Hierarchical Class of Service Network Scenarios | 6
Services to Subscribers | 6
Services to Businesses | 6
Wireless Backhaul | 7
Understanding Hierarchical Scheduling | 7
Hierarchical Scheduling Terminology | 8
Scheduler Node-Level Designations in Hierarchical Scheduling | 8
Hierarchical Scheduling at Non-Leaf Nodes | 9
Priority Propagation in Hierarchical Scheduling | 10
Configuring Hierarchical Schedulers for CoS | 13
Hierarchical Schedulers and Traffic Control Profiles | 14
Example: Building a Four-Level Hierarchy of Schedulers | 16
Configuring the Interface Sets | 17
Configuring the Interfaces | 17
Configuring the Traffic Control Profiles | 18
Configuring the Schedulers | 19

iv
Configuring the Drop Profiles | 20
Configuring the Scheduler Maps | 20
Applying the Traffic Control Profiles | 21
Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels | 22
Understanding Scheduling and Shaping of Traffic Routed to GRE Tunnels | 22
Configuration Overview | 23
Configuration Caveats | 23
Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed
to GRE Tunnels | 24
Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs | 43
Configuring Hierarchical Class of Service on MICs, MPCs, MLCs, and Aggregated Ethernet
Interfaces | 46
Understanding Hierarchical Scheduling for MIC and MPC Interfaces | 46
Scheduler Node Scaling for MIC and MPC Interfaces | 47
Hierarchical Scheduling Priority Levels for MIC and MPC Interfaces | 47
Guaranteed Bandwidth and Weight of an Interface Node on MIC and MPC Interfaces | 48
Hierarchical Scheduling for MIC and MPC Interfaces in Oversubscribed PIR Mode | 48
Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces | 49
Per-Unit Queuing and Hierarchical Queuing for MIC and MPC Interfaces | 51
Queuing Models Supported for MIC and MPC Interfaces | 52
Limited Scale Per-Unit Queuing MPCs | 52
Hierarchical Queuing MICs and MPCs | 52
Scheduler Node Levels for MIC and MPC Interfaces | 53
Scheduler Node Levels for Per-Unit Queuing MPCs | 53
Scheduler Node Levels for Hierarchical Queuing MICs and MPCs | 54
Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces Overview | 55
Queue Scaling for MPCs | 55
Managing Remaining Queues | 56
Jitter Reduction in Hierarchical CoS Queues | 58
Queue Jitter as a Function of the Maximum Number of Queues | 58
Default Maximum Queues for Hierarchical Queuing MICs and MPCs | 58
Shaping Rate Granularity as a Function of the Rate Wheel Update Period | 59
Example: Reducing Jitter in Hierarchical CoS Queues | 61

v
Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview | 68
Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces | 69
Example: Configuring Scheduling Modes on Aggregated Interfaces | 70
Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip | 76
2 Hierarchical CoS for Subscriber Management

Hierarchical Class of Service for Subscriber Management | 80
Hierarchical Class of Service for Subscriber Management Overview | 80
Understanding Hierarchical CoS for Subscriber Interfaces | 81
Two-Level Hierarchical Scheduling | 82
Three-Level Hierarchical Scheduling | 84
Interface Hierarchy Versus CoS Hierarchy | 86
Four-Level Hierarchical Scheduling | 87
Hardware Requirements for Dynamic Hierarchical CoS | 89
Configuring Static Hierarchical Scheduling in a Dynamic Profile | 91
Configuring Hierarchical CoS for a Subscriber Interface of Aggregated Ethernet Links | 92
Configuring Hierarchical CoS on a Static PPPoE Subscriber Interface | 94
Example: Maintaining a Constant Traffic Flow by Configuring a Static VLAN Interface with a
Dynamic Profile for Subscriber Access | 95
Applying CoS to Groups of Subscriber Interfaces | 110
CoS for Interface Sets of Subscribers Overview | 110
Guidelines for Configuring Dynamic Interface Sets in a Subscriber Access Network | 110
Configuring an Interface Set of Subscribers in a Dynamic Profile | 113
Example: Configuring a Dynamic Interface Set of VLAN Subscribers | 114
Example: Configuring a Dynamic Service VLAN Interface Set of Subscribers in a Dynamic

Profile | 132
Configuring Hierarchical Scheduling for MPLS Pseudowire Interfaces | 137
Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview | 137
CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces | 138
CoS Two-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces | 140
Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces | 142
vi
CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber Interfaces | 144
Three-Level Scheduling Hierarchy: Pseudowire Logical Interfaces over a Transport Logical

Interface | 144
Three-Level Scheduling Hierarchy : Pseudowire Service Logical Interfaces over a Pseudowire

Service Interface Set | 145
Three-Level Scheduling Hierarchy Combined Deployment Scenario | 146
Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces
(Logical Interfaces over a Transport Logical Interface) | 147
(Logical Interfaces over a Pseudowire Interface Set) | 149
Configuring Hierarchical Scheduling for L2TP | 153
CoS for L2TP LAC Subscriber Interfaces Overview | 153
Traffic from LAC to LNS | 154
LAC Tunnels: Traffic from LNS to LAC | 155
Configuring Dynamic CoS for an L2TP LAC Tunnel | 156
CoS for L2TP LNS Inline Services Overview | 157
Guidelines for Applying CoS to the LNS | 158
Hardware Requirements for Inline Services on the LNS | 158
Configuring an Inline Service Interface for L2TP LNS | 159
Configuring Dynamic CoS for an L2TP LNS Inline Service | 160
Preventing Bandwidth Contention on Subscriber Interfaces | 163
Hierarchical CoS Shaping-Rate Adjustments Overview | 163
Types of Shaping-Rate Adjustments | 164
Levels of Shaping-Rate Adjustments | 164
Shaping Rate Adjustments for Subscriber Local Loops Overview | 165

vii
Guidelines for Configuring Shaping-Rate Adjustments for Subscriber Local Loops | 166
Configuring the Minimum Adjusted Shaping Rate on Scheduler Nodes for Subscribers | 168
Overview | 168
Configuring a Static Minimum Adjusted Shaping Rate on Scheduler Nodes | 168
Configuring a Dynamic Minimum Adjusted Shaping Rate on Scheduler Nodes | 169
Configuring Shaping-Rate Adjustments on Queues | 169
Overview | 170
Configuring a Static Shaping-Rate Adjustment for Queues | 170
Configuring a Dynamic Shaping-Rate Adjustment for Queues | 171
Enabling Shaping-Rate Adjustments for Subscriber Local Loops | 172
Configuring Static Logical Interface Sets to Serve as CoS Hierarchical Scheduler Nodes for
Subscriber Loops | 173
Configuring the Logical Interfaces That Compose the Static Logical Interface Sets | 174
Configuring Hierarchical CoS on the Static Logical Interface Sets That Serve as Hierarchical
Scheduler Nodes for Subscriber Local Loops | 174
Configuring ANCP Functionality That Supports and Drives Shaping-Rate Adjustments for
Subscriber Local Loops | 177
Disabling Shaping-Rate Adjustments for Subscriber Local Loops | 178
Disabling Hierarchical Bandwidth Adjustment for Subscriber Interfaces with Reverse-OIF

Mapping | 179
Example: Configuring Hierarchical CoS Shaping-Rate Adjustments for Subscriber Local Loops | 180
Verifying the Configuration of Shaping-Rate Adjustments for Subscriber Local Loops | 183
Verifying the Configuration of ANCP for Shaping-Rate Adjustments | 184
Using Hierarchical CoS to Adjust Shaping Rates Based on Multicast Traffic | 185
Configuring Targeted Distribution of Subscribers on Aggregated Ethernet Interfaces | 188
Distribution of Demux Subscribers in an Aggregated Ethernet Interface | 188
Distribution Models | 188
Sample Targeted Distribution Topology | 189
Redundancy and Redistribution Mechanisms | 189
Considerations and Best Practices | 190
Providing Accurate Scheduling for a Demux Subscriber Interface of Aggregated Ethernet Links | 191
Configuring the Distribution Type for Demux Subscribers on Aggregated Ethernet Interfaces | 192
viii
Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet
Interface | 193
Configuring Rebalancing of Demux Subscribers in an Aggregated Ethernet Interface | 194
Configuring Periodic Rebalancing of Subscribers in an Aggregated Ethernet Interface | 194
Configuring Manual Rebalancing of Subscribers on an Aggregated Ethernet Interface | 195
Example: Separating Targeted Multicast Traffic for Demux Subscribers on Aggregated Ethernet
Interfaces | 196
Verifying the Distribution of Demux Subscribers in an Aggregated Ethernet Interface | 209
Configuring the Distribution Type for PPPoE Subscribers on Aggregated Ethernet Interfaces | 209
Verifying the Distribution of PPPoE Subscribers in an Aggregated Ethernet Interface | 210
Applying CoS Using Parameters Received from RADIUS | 212
Subscriber Interfaces That Provide Initial CoS Parameters Dynamically Obtained from RADIUS | 212
Dynamic Configuration of Initial CoS in Access Profiles | 213
Predefined Variables for Dynamic Configuration of Initial Traffic Shaping | 213
Predefined Variables for Dynamic Configuration of Initial Scheduling and Queuing | 214
Changing CoS Services Overview | 217
Types of CoS Variables Used in a Service Profile | 217
Static and Dynamic CoS Configurations | 218
Scenarios for Static and Dynamic Configuration of CoS Parameters | 218
CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber Sessions
Overview | 221
Supported Network Configurations | 221
Traffic-Control Profiles in Subscriber Interface Dynamic Profiles | 221
CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets and Member Subscriber
Sessions | 222
Guidelines for Configuring CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member
Subscriber Sessions | 223
Configuring Initial CoS Parameters Dynamically Obtained from RADIUS | 224
Configuring Static Default Values for Traffic Scheduling and Shaping | 225
Applying CoS Traffic-Shaping Attributes to Dynamic Interface Sets and Member Subscriber
Sessions | 227
CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets | 229
Example: Configuring Dynamic Hierarchical Scheduling for Subscribers | 235

ix
3 Configuration Statements and Operational Commands

Configuration Statements | 245
accept | 250
address-assignment (Address-Assignment Pools) | 252
authentication (DHCP Local Server) | 255
authentication (DHCP Relay Agent) | 257
authentication-order | 259
auto-configure | 261
adjust-minimum | 263
adjust-percent | 264
atm-service | 265
buffer-size (Schedulers) | 266
cbr | 268
classifiers (Definition) | 270
classifiers (Logical Interface) | 272
classifiers (Physical Interface) | 273
code-points (CoS) | 274
delay-buffer-rate | 276
demux0 (Dynamic Interface) | 278
demux-options (Dynamic Interface) | 280
demux-source (Dynamic IP Demux Interface) | 281
demux-source (Dynamic Underlying Interface) | 282
demux-source (Underlying Interface) | 283
dhcp-attributes (Address-Assignment Pools) | 284
dhcp-local-server | 291
dhcp-relay | 308
drop-probability (Interpolated Value) | 327
drop-probability (Percentage) | 328
drop-profile (Schedulers) | 329
drop-profile-map (Schedulers) | 330
drop-profiles | 331
dscp (CoS Classifiers) | 332
dscp (Rewrite Rules) | 333

x
dscp-ipv6 (CoS Rewrite Rules) | 335
dynamic-profile (DHCP Local Server) | 337
dynamic-profile (VLAN) | 339
dynamic-profiles | 340
egress-shaping-overhead | 354
excess-bandwidth-share | 356
excess-priority | 358
excess-rate (Dynamic Traffic Shaping) | 360
excess-rate-high (Dynamic Traffic Shaping) | 362
excess-rate-low (Dynamic Traffic Shaping) | 364
family | 366
family (Address-Assignment Pools) | 372
family (Dynamic Demux Interface) | 374
family (Dynamic PPPoE) | 376
family (Dynamic Standard Interface) | 378
fill-level (Drop Profiles) | 380
fill-level (Interpolated Value) | 381
filter (Configuring) | 382
flexible-vlan-tagging | 384
forwarding-classes (Class-of-Service) | 385
group (DHCP Local Server) | 386
guaranteed-rate | 392
hierarchical-scheduler | 394
hierarchical-scheduler (Subscriber Interfaces on MX Series Routers) | 395
ieee-802.1ad | 397
inet-precedence (CoS Classifiers) | 398
input-excess-bandwidth-share | 399
input-scheduler-map | 400
input-shaping-rate (Logical Interface) | 402
input-shaping-rate (Physical Interface) | 404
input-traffic-control-profile | 405
input-traffic-control-profile-remaining | 406
interface (DHCP Local Server) | 407
interface-set (Ethernet Interfaces) | 410

xi
interface-set (Hierarchical Schedulers) | 411
interface-set (IP Demux Interfaces) | 412
interfaces | 413
interfaces (CoS) | 415
interfaces (Static and Dynamic Subscribers) | 418
internal-node | 425
interpolate | 426
loss-priority (BA Classifiers) | 427
loss-priority (Scheduler Drop Profiles) | 428
max-queues | 430
max-queues-per-interface | 432
member-link-scheduler | 434
mode (Layer 2 Tunneling Protocol Shaping) | 435
output-traffic-control-profile | 437
output-traffic-control-profile-remaining | 439
overhead-accounting | 441
pap (Dynamic PPP) | 442
peak-rate | 443
per-unit-scheduler | 444
pool (Address-Assignment Pools) | 446
pppoe-options (Dynamic PPPoE) | 448
ppp-options (Dynamic PPP) | 449
priority (Schedulers) | 452
profile (Access) | 454
protocols | 461
proxy-arp | 465
qos-adjust-hierarchical | 467
queue (Global Queues) | 468
radius (Access Profile) | 469
radius-server | 473
range (Address-Assignment Pools) | 479
ranges (Dynamic VLAN) | 480
rewrite-rules (Definition) | 481
rewrite-rules (Interfaces) | 482

xii
routing-instances (Multiple Routing Entities) | 484
scheduler (Scheduler Map) | 486
scheduler-map (Interfaces and Traffic-Control Profiles) | 487
scheduler-maps (For Most Interface Types) | 488
schedulers (CoS) | 489
secret (RADIUS) | 491
server (Dynamic PPPoE) | 492
server-group | 493
shaping-rate (Applying to an Interface) | 495
shaping-rate (Schedulers) | 498
shaping-rate (Oversubscribing an Interface) | 500
shaping-rate-excess-high | 502
shaping-rate-excess-low | 504
shaping-rate-priority-high | 506
shaping-rate-priority-low | 508
shaping-rate-priority-medium | 510
shared-bandwidth-policer (Configuring) | 512
shared-instance | 513
shared-scheduler | 514
simple-filter (Applying to an Interface) | 515
simple-filter | 516
site-identifier (VPLS) | 518
stacked-interface-set (Dynamic Profiles) | 519
stacked-vlan-tagging | 521
term (Simple Filter) | 522
three-color-policer (Applying) | 524
three-color-policer (Configuring) | 525
traffic-control-profiles | 527
traffic-manager | 530
transmit-rate (Schedulers) | 535
transparent | 537
underlying-interface (demux0) | 538
underlying-interface (Dynamic PPPoE) | 540
unit | 541
xiii
unit (Dynamic Demux Interface) | 543
unit (Dynamic PPPoE) | 545
unnumbered-address (Dynamic PPPoE) | 547
unnumbered-address (Dynamic Profiles) | 548
unnumbered-address (Ethernet) | 550
user-prefix (DHCP Relay Agent) | 551
vlan-id (Dynamic Profiles) | 553
vlan-id (VLAN ID to Be Bound to a Logical Interface) | 554
vlan-model | 555
vlan-ranges | 556
vlan-tag | 558
vlan-tags | 559
vlan-tags-outer | 560
vlan-tags (Stacked VLAN Tags) | 561
Operational Commands | 563
show access-cac interface-set | 564
show class-of-service adjustment-control-profile | 567
show class-of-service classifier | 569
show class-of-service interface | 572
show class-of-service scheduler-map | 612
show class-of-service scheduler-hierarchy interface | 616
show class-of-service scheduler-hierarchy interface-set | 619
show interfaces | 621
show interfaces (PPPoE) | 728
show interfaces demux0 (Demux Interfaces) | 741
show interfaces queue | 753
show subscribers | 816

xiv
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xiv
Using the Examples in This Manual | xiv
Documentation Conventions | xvi
Documentation Feedback | xix
Requesting Technical Support | xix
Use this guide to understand and configure hierarchical class of service (CoS) features in Junos OS to
define service levels that provide different delay, jitter, and packet loss characteristics to particular
applications served by specific traffic flows. Applying CoS features to each device in your network ensures
quality of service (QoS) for traffic throughout your entire network.
Documentation and Release Notes
®
To obtain the most current version of all Juniper Networks technical documentation, see the product
documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.
If the information in the latest release notes differs from the information in the documentation, follow the
product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts.
These books go beyond the technical documentation to explore the nuances of network architecture,
deployment, and administration. The current list can be viewed at https://www.juniper.net/books.
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative
command. These commands cause the software to merge the incoming configuration into the current
candidate configuration. The example does not become active until you commit the candidate configuration.
xv
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example
is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In
this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf. Copy the
ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
xvi
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the
ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode
command:
[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the load merge
relative configuration mode command:
[edit system scripts]

user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xvii defines notice icons used in this guide.

xvii
Table 1: Notice Icons
Icon Meaning Description
Informational note Indicates important features or instructions.
Caution Indicates a situation that might result in loss of data or hardware

damage.
Warning Alerts you to the risk of personal injury or death.
Laser warning Alerts you to the risk of personal injury from a laser.
Tip Indicates helpful information.
Best practice Alerts you to a recommended use or implementation.
Table 2 on page xvii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention Description Examples
Bold text like this Represents text that you type. To enter configuration mode, type
the configure command:
user@host> configure
Fixed-width text like this Represents output that appears on user@host> show chassis alarms
the terminal screen.
No alarms currently active
Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
• Identifies RFC and Internet draft • Junos OS CLI User Guide

titles. • RFC 1997, BGP Communities
Attribute
xviii
Table 2: Text and Syntax Conventions (continued)
Italic text like this Represents variables (options for Configure the machine’s domain
which you substitute a value) in name:
commands or configuration
[edit]
statements.
root@# set system domain-name
domain-name
Text like this Represents names of configuration • To configure a stub area, include
statements, commands, files, and the stub statement at the [edit
directories; configuration hierarchy protocols ospf area area-id]
levels; or labels on routing platform hierarchy level.
components. • The console port is labeled
CONSOLE.
< > (angle brackets) Encloses optional keywords or stub <default-metric metric>;
variables.
| (pipe symbol) Indicates a choice between the broadcast | multicast

mutually exclusive keywords or
(string1 | string2 | string3)
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS
same line as the configuration only
statement to which it applies.
[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]
Indention and braces ( { } ) Identifies a level in the configuration [edit]

hierarchy. routing-options {
static {
; (semicolon) Identifies a leaf statement at a route default {
configuration hierarchy level. nexthop address;
retain;
}
}
}
GUI Conventions
xix
Table 2: Text and Syntax Conventions (continued)
Bold text like this Represents graphical user interface • In the Logical Interfaces box, select
(GUI) items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of In the configuration editor hierarchy,
menu selections. select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You can use either
of the following methods:
• Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper
Networks TechLibrary site, and do one of the following:
• Click the thumbs-up icon if the information on the page was helpful to you.
• Click the thumbs-down icon if the information on the page was not helpful to you or if you have
suggestions for improvement, and use the pop-up form to provide feedback.
• E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,

URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
xx
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
• JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
• Product warranties—For product warranty information, visit https://www.juniper.net/support/warranty/.
• JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week,
365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
• Find CSC offerings: https://www.juniper.net/customers/support/
• Search for known bugs: https://prsearch.juniper.net/
• Find product documentation: https://www.juniper.net/documentation/
• Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
• Download the latest versions of software and review release notes:

https://www.juniper.net/customers/csc/software/
• Search technical bulletins for relevant hardware and software notifications:

https://kb.juniper.net/InfoCenter/
• Join and participate in the Juniper Networks Community Forum:

https://www.juniper.net/company/communities/
• Create a service request online: https://myjuniper.juniper.net
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool:
https://entitlementsearch.juniper.net/entitlementsearch/
Creating a Service Request with JTAC
You can create a service request with JTAC on the Web or by telephone.
• Visit https://myjuniper.juniper.net.
• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see

https://support.juniper.net/support/requesting-support/.
1 PART
Hierarchical Class of Service
Configuring Hierarchical Class of Service on MX Series 5G Universal Routing

Platforms | 2
Configuring Hierarchical Class of Service on MICs, MPCs, MLCs, and Aggregated

Ethernet Interfaces | 46
2
CHAPTER 1
Configuring Hierarchical Class of Service on MX Series

5G Universal Routing Platforms
IN THIS CHAPTER
Priority Propagation in Hierarchical Scheduling | 10
Hierarchical Schedulers and Traffic Control Profiles | 14
Example: Building a Four-Level Hierarchy of Schedulers | 16
Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE
Tunnels | 24
Hierarchical Class of Service Overview
Hierarchical class of service (HCoS) is the ability to apply traffic schedulers and shapers to a hierarchy of
scheduler nodes. Each level of the scheduler hierarchy can be used to shape traffic based on different
criteria such as application, user, VLAN, and physical port.
This allows you to support the requirements of different services, applications, and users on the same
physical device and physical infrastructure.
HCoS is implemented primarily using traffic classifiers at the ingress and hierarchical schedulers and shapers
at the egress.
A classifier is a filter that labels traffic at the device ingress based on configurable parameters such as
application or destination. Traffic is classified into what is called a forwarding equivalence class (FEC). The
FEC defines a class of traffic that receives common treatment.
3
Schedulers, and their associated shapers, is the function that controls the traffic bandwidth, jitter (delay
variation), and packet loss priority at the egress of the device.
Hierarchical schedulers are used to apply multiple levels of scheduling and shaping with each level applied
to different classifications such as forwarding equivalence class, VLAN, and physical interface (port) as
shown in Figure 1 on page 3.
Figure 1: Hierarchical Scheduling Architecture
NOTE: Hierarchical class of service is also referred to as Hierarchical Quality of Service (HQoS)
in other vendor’s documentation.
A typical application of HCoS is to configure multiple levels of egress schedulers and shapers, at the
subscriber edge, using dynamic profiles to provide traffic shaping and prioritization at the subscriber VLAN
level and for multiple classes of traffic.
Dynamic profiles are a mechanism that allows you to dynamically apply schedulers and shapers to individual
subscribers or groups of subscribers.
4
To learn more about HCoS, the following topics are very helpful:
• Junos CoS on MX Series 5G Universal Routing Platforms Overview
• CoS Features and Limitations on MX Series Routers
• CoS Features of the Router Hardware, PIC, MIC, and MPC Interface Families
• How Schedulers Define Output Queue Properties
• Subscriber Access Network Overview
• CoS for Subscriber Access Overview
• Hierarchical Class of Service for Subscriber Management Overview on page 80
The Junos OS hierarchical schedulers support up to five levels of scheduler hierarchies on MX Series
devices when using enhanced queuing Dense Port Concentrators (DPCs) or fine-grained queuing Modular
Port Concentrators (MPCs), and Modular Interface Cards (MICs). It is important to know the capabilities
of your hardware with respect to HCoS. The following are a few tips to help you:
• Only certain hardware supports the five-level scheduler hierarchy of HCoS.
• The number of queues and logical interfaces supported is dependent upon exactly what hardware you
are using.
• The MX Series Packet Forwarding Engine handles guaranteed bandwidth and scheduler node weight
differently than other Packet Forwarding Engines.
• The fine-grained queuing MPCs and MICs have a certain granularity with respect to the shaping and
delay buffer values. The values used are not necessarily exactly the values configured.
To learn more about platform support for HCoS, use the Juniper Networks Feature Explorer
(https://pathfinder.juniper.net/feature-explorer/). In the Feature Explorer, search on hierarchical schedulers.
In addition, it is important to note the following:
• HCoS is most frequently used to enforce service level agreements at the subscriber edged using dynamic
traffic control profiles.
• Hierarchical schedulers can also be applied to Ethernet pseudowire interfaces, aggregated Ethernet
interfaces, Layer 2 Tunnel Protocol (L2TP) network server (LNS) inline services, and GRE tunnels.
• Hierarchical ingress policing is a feature that is complimentary to and often used in conjunction with
HCoS.
• There are other features in Junos OS that have similar sounding names.
NOTE: The hierarchical scheduler and shaper feature supported on the SRX Series devices is not
the HCoS feature described here.
5
Before planning HCoS for you network, you should learn about HCoS, define you needs, plan how you
want to implement HCoS, and test the operation in a simulated environment.
Table 3: Resources for Learning More About HCoS
Document Description
Day One: Deploying Basic QoS Juniper This book is a good resource for learning the basics of CoS on Juniper
Networks Books Networks devices.
Juniper MX-Series O'Reilly Media Learn about the advanced features of HCoS. This book provides an
in-depth description of how HCoS works and how it can be deployed.
It also provides a lab tested topology and configuration example.
Day One: Dynamic Subscriber Management Learn how to use HCoS in conjunction with dynamic traffic control
Juniper Networks Books profiles for subscriber management. This book also includes
troubleshooting.
QoS Enabled Networks John Wiley & Sons This book is an additional source for studying QoS.
Documentation related to HCoS is consolidated in the Hierarchical Class of Service User Guide.
RELATED DOCUMENTATION

6
Hierarchical Class of Service Network Scenarios
Hierarchical class of service (HCoS) can be used to provide granular control of traffic for a variety of
different applications.
NOTE: Hierarchical class of service is also referred to as Hierarchical Quality of Service (HQoS)
in other vendor’s documentation.
Hierarchical class of service is most frequently used in the following scenarios:
Services to Subscribers
Multiservice network operators face a challenge to provide different types of services on the same
infrastructure to residential and business subscribers. The network operator needs to make sure each
subscriber gets the network resources they paid for and each service gets the network resources it needs
to operate properly.
If no CoS is applied, one service could consume most of the bandwidth of the transmission infrastructure
and starve the other services.
Using hierarchical class of service, the network edge device can have up to five levels of scheduling and
prioritization. So the traffic can be shaped and prioritized per customer and per service type. Controlling
traffic in this way provides the ability to deliver the required service level for each subscriber for each
service type.
By allowing network operators to consolidate different services and multiple customers on the same
physical infrastructure, hierarchical class of service helps maximize the ability to offer revenue generating
services while simultaneously minimizing capital cost.
Services to Businesses
Hierarchical class of service is a valuable tool for service providers that support business customers who
are running applications with different prioritization and scheduling requirements over the same
infrastructure. In this scenario hierarchical class of service allows lower priority traffic to fully utilize the
available bandwidth on a port, while simultaneously ensuring low latency and guaranteed bandwidth to
higher priority traffic on the same port.
This allows a provider to consolidate different services on the same physical device and physical
infrastructure thus optimizing network resources while maintaining the required level of service.
All of this maximizes revenue and minimizes cost

7
Wireless Backhaul
In a cellular network the operator might want to offer business services along with its cell tower traffic.
One of the main challenges is to make sure that the time-sensitive cell traffic is not affected by the business
services running on the same infrastructure. Each type of traffic has its own priority flows and bandwidth
constraints. For example, wireless backhaul is very sensitive to fluctuations in the packet stream (Jitter)
because it relies on synchronization.
In this scenario, hierarchical class of service allows each type of traffic to receive the required resources
and quality of service while being delivered over the same infrastructure.
By consolidate different services on the same physical infrastructure, HCoS helps maximize revenue and
minimize cost.

Understanding Hierarchical Scheduling
IN THIS SECTION
Hierarchical Scheduling Terminology | 8
Scheduler Node-Level Designations in Hierarchical Scheduling | 8
Hierarchical Scheduling at Non-Leaf Nodes | 9
Hierarchical class of service (HCoS) is a set of capabilities that enable you to apply unique CoS treatment
for network traffic based on criteria such as user, application, VLAN, and physical port.
This allows you to support the requirements of different services, applications, and users on the same
physical device and physical infrastructure.
This topic covers the following information:

8
Hierarchical Scheduling Terminology
Hierarchical scheduling introduces some new CoS terms and also uses some familiar terms in different
contexts:
• Customer VLAN (C-VLAN)—A C-VLAN, defined by IEEE 802.1ad. A stacked VLAN contains an outer
tag corresponding to the S-VLAN, and an inner tag corresponding to the C-VLAN. A C-VLAN often
corresponds to CPE. Scheduling and shaping is often used on a C-VLAN to establish minimum and
maximum bandwidth limits for a customer. See also S-VLAN.
• Interface set—A logical group of interfaces that describe the characteristics of set of service VLANs,
logical interfaces, customer VLANs, or aggregated Ethernet interfaces. Interface sets establish the set
and name the traffic control profiles. See also Service VLAN.
• Scheduler— A scheduler defines the scheduling and queuing characteristics of a queue. Transmit rate,
scheduler priority, and buffer size can be specified. In addition, a drop profile may be referenced to
describe WRED congestion control aspects of the queue. See also Scheduler map.
• Scheduler map—A scheduler map is referenced by traffic control profiles to define queues. The scheduler
map establishes the queues that comprise a scheduler node and associates a forwarding class with a
scheduler. See also Scheduler.
• Stacked VLAN—An encapsulation on an S-VLAN with an outer tag corresponding to the S-VLAN, and
an inner tag corresponding to the C-VLAN. See also Service VLAN and Customer VLAN.
• Service VLAN (S-VLAN)—An S-VLAN, defined by IEEE 802.1ad, often corresponds to a network
aggregation device such as a DSLAM. Scheduling and shaping is often established for an S-VLAN to
provide CoS for downstream devices with little buffering and simple schedulers. See also Customer VLAN.
• Traffic control profile—Defines the characteristics of a scheduler node. Traffic control profiles are used
at several levels of the CLI, including the physical interface, interface set, and logical interface levels.
Scheduling and queuing characteristics can be defined for the scheduler node using the shaping-rate,
guaranteed-rate, and delay-buffer-rate statements. Queues over these scheduler nodes are defined by
referencing a scheduler map. See also Scheduler and Scheduler map.
• VLAN—Virtual LAN, defined on an Ethernet logical interface.
Scheduler Node-Level Designations in Hierarchical Scheduling
Scheduler hierarchies are composed of nodes and queues. Queues terminate the hierarchy. Nodes can be
either root nodes, leaf nodes, or internal (non-leaf) nodes. Internal nodes are nodes that have other nodes
as “children” in the hierarchy.
Scheduler hierarchies consist of levels, starting with Level 1 at the physical port. This chapter establishes
a four-level scheduler hierarchy which, when fully configured, consists of the physical interface (Level 1),
the interface set (Level 2), one or more logical interfaces (Level 3), and one or more queues (Level 4).
9
NOTE: Beginning with Junos OS Release 16.1, certain MPCs on MX Series devices support up
to five levels of scheduler hierarchies. The concepts presented in this topic apply similarly to five
scheduler hierarchy levels.
Table 4 on page 9 describes the possible combinations of scheduler nodes and their corresponding node
level designations for a hierarchical queuing MIC or MPC.
Table 4: Node Levels Designations in Hierarchical Scheduling
Hierarchical CoS Scheduler Nodes
Root Node Internal (Non-Leaf) Nodes Leaf Node

Scheduler Configuration for
Hierarchical CoS Level 1 Level 2 Level 3 Level 4
One or more traffic control profiles Physical interface — One or more One or more
configured on logical interfaces, but no logical interfaces queues
interface-sets configured
Interface-sets (collections of logical Physical interface — Interface-set One or more

interfaces) configured, but no queues
traffic-control profiles configured on
logical interfaces
Fully configured scheduler nodes Physical interface Interface-set One or more One or more
logical interfaces queues
The table illustrates how the configuration of an interface set or logical interface affects the terminology
of hierarchical scheduler nodes. For example, suppose you configure an interface-set statement with
logical interfaces (such as unit 0 and unit 2) and a queue. In this case, the interface-set is an internal node
at Level 2 of the scheduler node hierarchy. However, if there are no traffic control profiles attached to
logical interfaces, then the interface set is at Level 3 of the hierarchy.
Hierarchical Scheduling at Non-Leaf Nodes
Whereas standard CoS scheduling is based on the scheduling and queuing characteristics of a router’s
egress ports and their queues, hierarchical CoS scheduling is based on the scheduling and queuing
characteristics that span a hierarchy of scheduler nodes over a port. The hierarchy begins at Level 1, a
root node at the physical interface (port) level of the CLI hierarchy and terminates at Level 4, a leaf node
at the queue level. Between the root and leaf nodes of any scheduler hierarchy are one or more
internal nodes, which are non-root nodes that have other nodes as “children” in the hierarchy.
10
Whereas you configure standard CoS scheduling by applying a scheduler map to each egress port to specify
a forwarding class and a queue priority level, you configure hierarchical CoS scheduling with additional
parameters. To configure hierarchical CoS scheduling, you apply a scheduler map to the queue level (Level 4)
of a scheduler hierarchy, and you can apply a different traffic control profile at each of the other levels. A
traffic control profile specifies not only a scheduler map (forwarding class and queue priority level) but
also optional shaping rate (PIR), guaranteed transmit rate (CIR), burst rate, delay buffer rate, and drop
profile.
Release History Table
Release Description
16.1 Beginning with Junos OS Release 16.1, certain MPCs on MX Series devices support up
to five levels of scheduler hierarchies.
Priority Propagation in Hierarchical Scheduling
Priority propagation is performed for MX Series router output Interfaces on Enhanced Queuing DPCs,
MICs, and MPCs, and for M Series and T Series router output interfaces on IQ2E PICs. Priority propagation
is useful for mixed traffic environments when, for example, you want to make sure that the voice traffic
of one customer does not suffer due to the data traffic of another customer. Nodes and queues are serviced
in the order of their priority. The default priority of a queue is low, and you can explicitly configure a queue
priority by including the priority statement at the [edit class-of-service schedulers scheduler-name] hierarchy
level.
You cannot directly configure the priorities of all hierarchical scheduling elements. The priorities of internal
nodes, for example, are determined as follows:
• The highest priority of an active child, that is, a child currently containing traffic. (Interface sets only take
the highest priority of their active children.)
• Whether the node is above its configured guaranteed rate (CIR) or not (this is only relevant if the physical
interface is in CIR mode).
Each queue has a configured priority and a hardware priority. The usual mapping between the configured
priority and the hardware priority is shown in Table 5 on page 11.
11
Table 5: Queue Priority
Configured Priority Hardware Priority
Strict-high 0
High 0
Medium-high 1
Medium-low 1
Low 2
MPCs also have configurable CLI priorities of excess-priority high, excess-priority medium-high, excess-priority
medium-low, and excess-priority low. These priorities only take effect above the guaranteed rate.
In CIR mode, the priority for each internal node depends on whether the highest active child node is above
or below the guaranteed rate. The mapping between the highest active child’s priority and the hardware
priority below and above the guaranteed rate is shown in Table 6 on page 11.
Table 6: Internal Node Queue Priority for CIR Mode
Configured Priority of Highest Hardware Priority Below Hardware Priority Above

Active Child Node Guaranteed Rate Guaranteed Rate
Strict-high 0 0
High 0 3
Medium-high 1 3
Medium-low 1 3
Low 2 3
Excess-priority high* N/A 3
Excess-priority medium-high* N/A 3
Excess-priority medium-low* N/A 4
Excess-priority low* N/A 4
* MPCs only
12
In PIR-only mode, nodes cannot send if they are above the configured shaping rate. The mapping between
the configured priority and the hardware priority is for PIR-only mode is shown in Table 7 on page 12.
Table 7: Internal Node Queue Priority for PIR-Only Mode
Configured Priority Hardware Priority
Strict-high 0
High 0
Medium-high 1
Medium-low 1
Low 2
A physical interface with hierarchical schedulers configured is shown in Figure 2 on page 12. The configured
priorities are shown for each queue at the top of the figure. The hardware priorities for each node are
shown in parentheses. Each node also shows any configured shaping rate (PIR) or guaranteed rate (CIR)
and whether or not the queues is above or below the CIR. The nodes are shown in one of three states:
above the CIR (clear), below the CIR (dark), or in a condition where the CIR does not matter (gray).
Figure 2: Hierarchical Schedulers and Priorities
In the figure, the strict-high queue for customer VLAN 0 (cvlan 0) receives service first, even though the
customer VLAN is above the configured CIR (see Table 6 on page 11 for the reason: strict-high always
has hardware priority 0 regardless of CIR state). Once that queue has been drained, and the priority of the
node has become 3 instead of 0 (due to the lack of strict-high traffic), the system moves on to the medium
queues next (cvlan 1 and cvlan 3), draining them in a round robin fashion (empty queue lose their hardware
priority). The low queue on cvlan 4 (priority 2) is sent next, because that mode is below the CIR. Then the
high queues on cvlan 0 and cvlan2 (both now with priority 3) are drained in a round robin fashion, and
finally the low queue on cvlan 0 is drained (thanks to svlan 0 having a priority of 3).
13
CoS on Enhanced IQ2 PICs Overview

Enhanced Queuing DPC CoS Properties
CoS Features and Limitations on MIC and MPC Interfaces
Configuring Hierarchical Schedulers for CoS
In metro Ethernet environments, a virtual LAN (VLAN) typically corresponds to a customer premises
equipment (CPE) device and the VLANs are identified by an inner VLAN tag on Ethernet frames (called
the customer VLAN, or C-VLAN, tag). A set of VLANs can be grouped at the DSL access multiplexer
(DSLAM) and identified by using the same outer VLAN tag (called the service VLAN, or S-VLAN, tag). The
service VLANs are typically gathered at the Broadband Remote Access Server (B-RAS) level.Hierarchical
schedulers let you provide shaping and scheduling at the service VLAN level as well as other levels, such
as the physical interface. In other words, you can group a set of logical interfaces and then apply scheduling
and shaping parameters to the logical interface set as well as to other levels.
On Juniper Networks MX Series 5G Universal Routing Platforms and systems with Enhanced IQ2 (IQ2E)
PICs, you can apply CoS shaping and scheduling at one of four different levels, including the VLAN set
level. You can only use this configuration on MX Series routers or IQ2E PICs. Beginning with Junos OS
Release 16.1, certain MPCs support up to five levels of scheduler hierarchies.
The supported scheduler hierarchy is as follows:
• The physical interface (level 1)
• The service VLAN (level 2 is unique to MX Series routers)
• The logical interface or customer VLAN (level 3)
• The queue (level 4)
Users can specify a traffic control profile (output-traffic-control-profile that can specify a shaping rate, a
guaranteed rate, and a scheduler map with transmit rate and buffer delay. The scheduler map contains the
mapping of queues (forwarding classes) to their respective schedulers (schedulers define the properties
for the queue). Queue properties can specify a transmit rate and buffer management parameters such as
buffer size and drop profile.
To configure CoS hierarchical scheduling, you must enable hierarchical scheduling by including the
hierarchical-scheduler statement at the physical interface.
14

CoS on Enhanced IQ2 PICs Overview
Hierarchical Schedulers and Traffic Control Profiles
When used, the interface set level of the hierarchy falls between the physical interface level (Level 1) and
the logical interface (Level 3). Queues are always Level 4 of the hierarchy.
NOTE: Beginning with Junos OS Release 16.1, certain MPCs on MX Series devices support up
to five levels of scheduler hierarchies. The concepts presented in this topic apply similarly to five
scheduler hierarchy levels.
Hierarchical schedulers add CoS parameters to the interface-set level of the configuration. They use traffic
control profiles to set values for parameters such as shaping rate (the peak information rate [PIR]),
guaranteed rate (the committed information rate [CIR] on these interfaces), scheduler maps (assigning
queues and resources to traffic), and so on.
The following CoS configuration places the following parameters in traffic control profiles at various levels:
• Traffic control profile at the port level (tcp-port-level1):
• A shaping rate (PIR) of 100 Mbps
• A delay buffer rate of 100 Mbps
• Traffic control profile at the interface set level (tcp-interface-level2):
• A guaranteed rate (CIR) of 40 Mbps
• Traffic control profile at the logical interface level (tcp-unit-level3):
• A guaranteed rate (CIR) of 30 Mbps
• A scheduler map called smap1 to hold various queue properties (level 4)
• A delay buffer rate of 40 Mbps

15
In this case, the traffic control profiles look like this:
[edit class-of-service traffic-control-profiles]

tcp-port-level1 { # This is the physical port level
shaping-rate 100m;
delay-buffer-rate 100m;
}
tcp-interface-level2 { # This is the interface set level
shaping-rate 60m;
guaranteed-rate 40m;
}
tcp-unit-level3 { # This is the logical interface level
shaping-rate 50m;
scheduler-map smap1;
}
Once configured, the traffic control profiles must be applied to the proper places in the CoS interfaces
hierarchy.
[edit class-of-service interfaces]

interface-set level-2 {
output-traffic-control-profile tcp-interface-level-2;
}
ge-0/1/0 {
output-traffic-control-profile tcp-port-level-1;
unit 0 {
output-traffic-control-profile tcp-unit-level-3;
}
}
In all cases, the properties for level 4 of the hierarchical schedulers are determined by the scheduler map.
Release Description
16.1 Beginning with Junos OS Release 16.1, certain MPCs on MX Series devices support up
to five levels of scheduler hierarchies.
16
Oversubscribing Interface Bandwidth

Providing a Guaranteed Minimum Rate
Configuring Scheduler Maps
Configuring Traffic Control Profiles for Shared Scheduling and Shaping
Example: Building a Four-Level Hierarchy of Schedulers
IN THIS SECTION
Configuring the Interface Sets | 17
Configuring the Interfaces | 17
Configuring the Traffic Control Profiles | 18
Configuring the Schedulers | 19
Configuring the Drop Profiles | 20
Configuring the Scheduler Maps | 20
Applying the Traffic Control Profiles | 21
This section provides a more complete example of building a 4-level hierarchy of schedulers. The
configuration parameters are shown in Figure 3 on page 16. The queues are shown at the top of the figure
with the other three levels of the hierarchy below.
Figure 3: Building a Scheduler Hierarchy
The figure’s PIR values are configured as the shaping rates and the CIRs are configured as the guaranteed
rate on the Ethernet interface ge-1/0/0. The PIR can be oversubscribed (that is, the sum of the children
17
PIRs can exceed the parent’s, as in svlan 1, where 200 + 200 + 100 exceeds the parent rate of 400)).
However, the sum of the children node level’s CIRs must never exceed the parent node’s CIR, as shown
in all the service VLANs (otherwise, the guaranteed rate could never be provided in all cases).
This configuration example presents all details of the CoS configuration for the interface in the figure
(ge-1/0/0), including:
Configuring the Interface Sets
[edit interfaces]
interface-set svlan-0 {
interface ge-1/0/0 {
unit 0;
unit 1;
}
}
interface-set svlan-1 {
unit 2;
unit 3;
unit 4;
}
}
Configuring the Interfaces
The keyword to configure hierarchical schedulers is at the physical interface level, as is VLAN tagging and
the VLAN IDs. In this example, the interface sets are defined by logical interfaces (units) and not outer
VLAN tags. All VLAN tags in this example are customer VLAN tags.
[edit interface ge-1/0/0]

hierarchical-scheduler;
vlan-tagging;
unit 0 {
vlan-id 100;
}
unit 1 {
vlan-id 101;
}
unit 2 {
vlan-id 102;
}
18
unit 3 {
vlan-id 103;
}
unit 4 {
vlan-id 104;
}
Configuring the Traffic Control Profiles
The traffic control profiles hold parameters for levels above the queue level of the scheduler hierarchy.
This section defines traffic control profiles for both the service VLAN level (logical interfaces) and the
customer VLAN (VLAN tag) level.

tcp-500m-shaping-rate {
shaping-rate 500m;
}
tcp-svlan0 {
shaping-rate 200m;
delay-buffer-rate 300m; # This parameter is not shown in the figure.
}
tcp-svlan1 {
shaping-rate 400m;
delay-buffer-rate 100m; # This parameter is not shown in the figure.
}
tcp-cvlan0 {
shaping-rate 100m;
scheduler-map tcp-map-cvlan0; # Applies scheduler maps to customer VLANs.
}
tcp-cvlan1 {
shaping-rate 100m;
scheduler-map tcp-map-cvlan1; # Applies scheduler maps to customer VLANs.
}
tcp-cvlan2 {
shaping-rate 200m;
scheduler-map tcp-map-cvlanx; # Applies scheduler maps to customer VLANs.
}
tcp-cvlan3 {
19
shaping-rate 200m;
scheduler-map tcp-map-cvlanx; # Applies scheduler maps to customer VLANs
}
tcp-cvlan4 {
shaping-rate 100m;
scheduler-map tcp-map-cvlanx; # Applies scheduler maps to customer VLANs
}
Configuring the Schedulers
The schedulers hold the information about the queues, the last level of the hierarchy. Note the consistent
naming schemes applied to repetitive elements in all parts of this example.
[edit class-of-service schedulers]

sched-cvlan0-qx {
priority low;
transmit-rate 20m;
buffer-size temporal 100ms;
drop-profile loss-priority low dp-low;
drop-profile loss-priority high dp-high;
}
sched-cvlan1-q0 {
priority high;
transmit-rate 20m;
buffer-size percent 40;
}
sched-cvlanx-qx {
transmit-rate percent 30;
}
sched-cvlan1-qx {
transmit-rate 10m;
buffer-size temporal 100ms;
}
20
Configuring the Drop Profiles
This section configures the drop profiles for the example. For more information about interpolated drop
profiles, see Managing Congestion Using RED Drop Profiles and Packet Loss Priorities.
[edit class-of-service drop-profiles]

dp-low {
interpolate fill-level 80 drop-probability 80;
}
dp-high {
}
Configuring the Scheduler Maps
This section configures the scheduler maps for the example. Each one references a scheduler configured
in “Configuring the Schedulers” on page 19.
[edit class-of-service scheduler-maps]

tcp-map-cvlan0 {
forwarding-class voice scheduler sched-cvlan0-qx;
forwarding-class video scheduler sched-cvlan0-qx;
forwarding-class data scheduler sched-cvlan0-qx;
}
tcp-map-cvlan1 {
forwarding-class voice scheduler sched-cvlan1-q0;
forwarding-class video scheduler sched-cvlan1-qx;
forwarding-class data scheduler sched-cvlan1-qx;
}
tcp-map-cvlanx {
forwarding-class voice scheduler sched-cvlanx-qx;
forwarding-class video scheduler sched-cvlanx-qx;
forwarding-class data scheduler sched-cvlanx-qx;
}
21
Applying the Traffic Control Profiles
This section applies the traffic control profiles to the proper levels of the hierarchy.
NOTE: Although a shaping rate can be applied directly to the physical interface, hierarchical
schedulers must use a traffic control profile to hold this parameter.

ge-1/0/0 {
output-traffic-control-profile tcp-500m-shaping-rate;
unit 0 {
output-traffic-control-profile tcp-cvlan0;
}
unit 1 {
}
unit 2 {
}
unit 3 {
}
unit 4 {
}
}
interface-set svlan0 {
output-traffic-control-profile tcp-svlan0;
}
interface-set svlan1 {
output-traffic-control-profile tcp-svlan1;
}
22
NOTE: You should be careful when using a show interfaces queue command that references
nonexistent class-of-service logical interfaces. When multiple logical interfaces (units) are not
configured under the same interface set or physical interface, but are referenced by a command
such as show interfaces queue ge-10/0/1.12 forwarding-class be or show interfaces queue
ge-10/0/1.13 forwarding-class be (where logical units 12 and 13 are not configured as a
class-of-service interfaces), these interfaces display the same traffic statistics for each logical
interface. In other words, even if there is no traffic passing through a particular unconfigured
logical interface, as long as one or more of the other unconfigured logical interfaces under the
same interface set or physical interface is passing traffic, this particular logical interface displays
statistics counters showing the total amount of traffic passed through all other unconfigured
logical interfaces together.
Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to

GRE Tunnels
IN THIS SECTION
Understanding Scheduling and Shaping of Traffic Routed to GRE Tunnels | 22
Configuration Overview | 23
Configuration Caveats | 23
Understanding Scheduling and Shaping of Traffic Routed to GRE Tunnels
On MX Series routers running Junos OS Release 12.3R4 or later revisions, 13.2R2 or later revision, or
13.3R1 or later, you can manage CoS scheduling and shaping of traffic routed to generic route encapsulation
(GRE) tunnel interfaces configured on MPC1 Q, MPC2 Q, or MPC2 EQ modules.
A single egress logical interface can be converted to multiple GRE tunnel interfaces. A GRE tunnel physical
interface can support many logical interfaces, but one or more of those logical interfaces might not have
an output traffic control profiles attached. If a GRE tunnel logical interface is not attached to an output
traffic control profile, the router does not assign the interface a dedicated scheduler. Instead, the interface
23
uses a reserved scheduler intended for all unshaped tunnel traffic (traffic entering a GRE tunnel logical
interface that does not have an explicit traffic control profile configuration).
Configuration Overview
At GRE tunnel interfaces, the output-traffic-control-profile configuration statement can apply an output
traffic scheduling and shaping profile at the physical or logical interface level, while the
output-traffic-control-profile-remaining configuration statement can apply an output traffic scheduling
and shaping profile for remaining traffic at the physical interface level only. Interface sets (sets of interfaces
used to configure hierarchical CoS schedulers on supported Ethernet interfaces) are not supported on
GRE tunnel interfaces.
By default—if you do not attach an output traffic control profile to the GRE tunnel physical interface—traffic
entering the interface is scheduled and shaped using the default 95/5 scheduler with parameters as
specified in the tunnel-services configuration.
If you use an output traffic control profile to configure the shaping rate at the GRE tunnel physical interface,
the shaping-rate specified by the attached traffic control profile overrides the bandwidth specified as the
tunnel services default value.
Configuration Caveats
When configuring hierarchical CoS scheduling and shaping of traffic routed to GRE tunnels, keep the
following guidelines in mind:
• You must first configure and commit a hierarchical scheduler on the GRE tunnel physical interface,
specifying a maximum of two hierarchical scheduling levels for node scaling. After you commit the
hierarchical-scheduler configuration, you can configure scheduling and queuing parameters at the GRE
tunnel physical or logical interfaces.
• GRE tunnel interfaces support eight egress queues only. For interfaces on MPC1 Q, MPC2 Q, and
MPC2 EQ modules, you can include the max-queues-per-interface 4 statement at the [edit fpc slot-number
pic pic-number] hierarchy level to configure four-queue mode for the interface. However, any GRE tunnel
interfaces configured on those ports have eight queues.
• Queuing and scheduling calculations include Layer 3 fields. For GRE interfaces, Layer 3 fields include
the delivery header (the outer IP header), the 4-byte GRE header, and the payload protocol header and
data.
Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed
to GRE Tunnels | 24
24
Example: Performing Output Scheduling and Shaping in Hierarchical CoS

Queues for Traffic Routed to GRE Tunnels
IN THIS SECTION
Requirements | 24
Overview | 25
Configuration | 25
Verification | 39
This example shows how to configure a generic routing encapsulation (GRE) tunnel device to perform CoS
output scheduling and shaping of IPv4 traffic routed to GRE tunnels. This feature is supported on MX
Series routers running Junos OS Release 12.3R4 or later revisions, 13.2R2 or later revision, or 13.3R1 or
later, with GRE tunnel interfaces configured on MPC1 Q, MPC2 Q, or MPC2 EQ modules.
Requirements
This example uses the following Juniper Networks hardware and Junos OS software:
• Transport network—An IPv4 network running Junos OS Release 13.3.
• GRE tunnel device—One MX80 router installed as an ingress provider edge (PE) router.
• Input and output logical interfaces configurable on two ports of the built-in 10-Gigabit Ethernet Modular
Interface Card (MIC):
• Input logical interface ge-1/1/0.0 for receiving traffic that is to be transported across the network.
• Output logical interfaces ge-1/1/1.0, ge-1/1/1.1, and ge-1/1/1.2 to convert to GRE tunnel source
interfaces gr-1/1/10.1, gr-1/1/10.2, and gr-1/1/10.3.
For information about interfaces hosted on modules in MX80 routers, see the following topics:
• MX5, MX10, MX40, and MX80 Modular Interface Card Description
• MX5, MX10, MX40, and MX80 Port and Interface Numbering

25
Overview
In this example, you configure the router with input and output logical interfaces for IPv4 traffic, and then
you convert the output logical interface to four GRE tunnel source interfaces. You also install static routes
in the routing table so that input traffic is routed to the four GRE tunnels.
NOTE: Before you apply a traffic control profile with a scheduler-map and shaping rate to a GRE
tunnel interface, you must configure and commit a hierarchical scheduler on the GRE tunnel
physical interface, specifying a maximum of two hierarchical scheduling levels for node scaling.
Configuration
IN THIS SECTION
Configuring Interfaces, Hierarchical Scheduling on the GRE Tunnel Physical Interface, and Static Routes | 29
Measuring GRE Tunnel Transmission Rates Without Shaping Applied | 32
Configuring Output Scheduling and Shaping at GRE Tunnel Physical and Logical Interfaces | 33
To configure scheduling and shaping in hierarchical CoS queues for traffic routed to GRE tunnel interfaces
configured on MPC1Q, MPC2Q, or MPC2 EQ modules on an MX Series router, perform these tasks:
CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any
line breaks, change any details necessary to match your network configuration, and then copy and paste
the commands into the CLI at the [edit] hierarchy level.
Configuring Interfaces, Hierarchical Scheduling on the GRE Tunnel Physical Interface, and Static Routes
set chassis fpc 1 pic 1 tunnel-services bandwidth 1g
set interfaces ge-1/1/0 unit 0 family inet address 10.6.6.1/24
set interfaces ge-1/1/1 unit 0 family inet address 10.70.1.1/24 arp 10.70.1.3
mac 00:00:03:00:04:00
mac 00:00:03:00:04:01
26
mac 00:00:03:00:04:02
mac 00:00:03:00:04:04
set interfaces gr-1/1/10 unit 1 family inet address 10.100.1.1/24
set interfaces gr-1/1/10 unit 1 tunnel source 10.70.1.1 destination 10.70.1.3
set interfaces gr-1/1/10 hierarchical-scheduler
set routing-options static route 10.2.2.0/24 next-hop gr-1/1/10.1
Configuring Output Scheduling and Shaping at GRE Tunnel Physical and Logical Interfaces
set class-of-service forwarding-classes queue 0 be
set class-of-service forwarding-classes queue 1 ef
set class-of-service forwarding-classes queue 2 af
set class-of-service forwarding-classes queue 3 nc
set class-of-service forwarding-classes queue 4 be1
set class-of-service forwarding-classes queue 5 ef1
set class-of-service forwarding-classes queue 6 af1
set class-of-service forwarding-classes queue 7 nc1
set class-of-service classifiers inet-precedence gr-inet forwarding-class be

loss-priority low code-points 000
27
set class-of-service classifiers inet-precedence gr-inet forwarding-class ef

set class-of-service classifiers inet-precedence gr-inet forwarding-class af

set class-of-service classifiers inet-precedence gr-inet forwarding-class nc

set class-of-service classifiers inet-precedence gr-inet forwarding-class be1

set class-of-service classifiers inet-precedence gr-inet forwarding-class ef1

set class-of-service classifiers inet-precedence gr-inet forwarding-class af1

set class-of-service classifiers inet-precedence gr-inet forwarding-class nc1

set class-of-service interfaces ge-1/1/0 unit 0 classifiers inet-precedence

gr-inet
set class-of-service schedulers be_sch transmit-rate percent 30
set class-of-service schedulers ef_sch transmit-rate percent 40
set class-of-service schedulers af_sch transmit-rate percent 25
set class-of-service schedulers nc_sch transmit-rate percent 5
set class-of-service schedulers be1_sch transmit-rate percent 60
set class-of-service schedulers be1_sch priority low
set class-of-service schedulers ef1_sch transmit-rate percent 40
set class-of-service schedulers ef1_sch priority medium-low
set class-of-service schedulers af1_sch transmit-rate percent 10
set class-of-service schedulers af1_sch priority strict-high
set class-of-service schedulers nc1_sch shaping-rate percent 10
set class-of-service schedulers nc1_sch priority high
set class-of-service scheduler-maps sch_map_1 forwarding-class be scheduler

be_sch
set class-of-service scheduler-maps sch_map_1 forwarding-class ef scheduler

ef_sch
28
set class-of-service scheduler-maps sch_map_1 forwarding-class af scheduler

af_sch
set class-of-service scheduler-maps sch_map_1 forwarding-class nc scheduler

nc_sch
set class-of-service scheduler-maps sch_map_2 forwarding-class be scheduler

be1_sch
set class-of-service scheduler-maps sch_map_2 forwarding-class ef scheduler

ef1_sch
set class-of-service scheduler-maps sch_map_3 forwarding-class af scheduler

af_sch
set class-of-service scheduler-maps sch_map_3 forwarding-class nc scheduler

nc_sch
set class-of-service traffic-control-profiles gr-ifl-tcp3 guaranteed-rate 5m
set class-of-service traffic-control-profiles gr-ifd-tcp shaping-rate 10m
set class-of-service traffic-control-profiles gr-ifd-tcp-remain shaping-rate

7m
set class-of-service traffic-control-profiles gr-ifd-tcp-remain guaranteed-rate

4m
set class-of-service traffic-control-profiles gr-ifl-tcp1 scheduler-map

sch_map_1
set class-of-service traffic-control-profiles gr-ifl-tcp1 shaping-rate 8m

sch_map_2

sch_map_3
set class-of-service interfaces gr-1/1/10 output-traffic-control-profile

gr-ifd-tcp
set class-of-service interfaces gr-1/1/10

output-traffic-control-profile-remaining gr-ifd-remain
set class-of-service interfaces gr-1/1/10 unit 1 output-traffic-control-profile

gr-ifl-tcp1
29

gr-ifl-tcp2

gr-ifl-tcp3
Configuring Interfaces, Hierarchical Scheduling on the GRE Tunnel Physical Interface, and Static Routes
Step-by-Step Procedure
To configure GRE tunnel interfaces (including enabling hierarchical scheduling) and static routes:
1. Configure the amount of bandwidth for tunnel services on the physical interface.
[edit]
user@host# set chassis fpc 1 pic 1 tunnel-services bandwidth 1g
2. Configure the GRE tunnel device output logical interface.
[edit]
user@host# set interfaces ge-1/1/0 unit 0 family inet address 10.6.6.1/24
3. Configure the GRE tunnel device output logical interface.
[edit]
user@host# set interfaces ge-1/1/1 unit 0 family inet address 10.70.1.1/24 arp 10.70.1.3 mac
00:00:03:00:04:00
00:00:03:00:04:01
00:00:03:00:04:02
00:00:03:00:04:04
4. Convert the output logical interface to four GRE tunnel interfaces.
[edit]
user@host# set interfaces gr-1/1/10 unit 1 family inet address 10.100.1.1/24
user@host# set interfaces gr-1/1/10 unit 1 tunnel source 10.70.1.1 destination 10.70.1.3
30
5. Enable the GRE tunnel interfaces to use hierarchical scheduling.
[edit]
user@host# set interfaces gr-1/1/10 hierarchical-scheduler
6. Install static routes in the routing table so that the device routes IPv4 traffic to the GRE tunnel source
interfaces.
Traffic destined to the subnets 10.2.2.0/24, 10.3.3.0/24, 10.4.4.0/24, and 10.5.5.0/24 is routed to the
tunnel interfaces at IP addresses 10.70.1.1, 10.80.1.1, 10.90.1.1, and 10.100.1.1, respectively.
[edit]
user@host# set routing-options static route 10.2.2.0/24 next-hop gr-1/1/10.1
7. If you are done configuring the device, commit the configuration.
[edit]
user@host# commit
Results
From configuration mode, confirm your configuration by entering the show chassis fpc 1 pic 1,
show interfaces ge-1/1/0, show interfaces ge-1/1/1, show interfaces gr-1/1/10, and show routing-options
commands. If the output does not display the intended configuration, repeat the instructions in this example
to correct the configuration.
Confirm the configuration of interfaces, hierarchical scheduling on the GRE tunnel physical interface, and
static routes.
user@host# show chassis fpc 1 pic 1

tunnel-services {
bandwidth 1g;
}
31
user@host# show interfaces ge-1/1/0

unit 0 {
family inet {
address 10.6.6.1/24;
]
}
user@host# show interfaces ge-1/1/1

unit 0 {
family inet {
address 10.70.1.1/24 (
arp 10.70.1.3 mac 00:00:03:00:04:00;
}
address 10.80.1.1/24 {
arp 10.80.1.3 mac 00:00:03:00:04:01;
}
address 10.90.1.1/24 {
arp 10.90.1.3 mac 00:00:03:00:04:02;
}
address 10.100.1.1/24 {
arp 10.100.1.3 mac 00:00:03:00:04:04;
}
]
}
user@host# show interfaces gr-1/1/10

unit 1 {
tunnel {
destination 10.70.1.3;
source 10.70.1.1;
}
family inet {
address 10.100.1.1/24;
}
}
unit 2 {
tunnel {
source 10.80.1.1;
}
family inet {
address 10.200.1.1/24;
32
}
}
unit 3 {
tunnel {
source 10.90.1.1;
}
family inet {
address 10.201.1.1/24;
}
}
unit 4 {
tunnel {
source 10.100.1.1;
}
family inet {
address 10.202.1.1/24;
}
}
user@host# show routing-options

static {
route 10.2.2.0/24 next-hop gr-1/1/10.1;
route 10.3.3.0/24 next-hop gr-1/1/10.2;
route 10.4.4.0/24 next-hop gr-1/1/10.3;
route 10.5.5.0/24 next-hop gr-1/1/10.4;
}
Measuring GRE Tunnel Transmission Rates Without Shaping Applied
To establish a baseline measurement, note the transmission rates at each GRE tunnel source.
1. Pass traffic through the GRE tunnel at logical interfaces gr-1/1/10.1, gr-1/1/10.2, and gr-1/1/10.3.
2. To display the traffic rates at each GRE tunnel source, use the show interfaces queue operational mode
command.
The following example command output shows detailed CoS queue statistics for logical interface
gr-1/1/10.1 (the GRE tunnel from source IP address 10.70.1.1 to destination IP address 10.70.1.3).
user@host> show interfaces queue gr-1/1/10.1

33
Logical interface gr-1/1/10.1 (Index 331) (SNMP ifIndex 4045)

Forwarding classes: 16 supported, 8 in use
Egress queues: 8 supported, 8 in use
Burst size: 0
Queue: 0, Forwarding classes: be
Queued:
Packets : 31818312 102494 pps
Bytes : 6522753960 168091936 bps
Transmitted:
Packets : 1515307 4879 pps
Bytes : 310637935 8001632 bps
Tail-dropped packets : 21013826 68228 pps
RED-dropped packets : 9289179 29387 pps
Low : 9289179 29387 pps
Medium-low : 0 0 pps
Medium-high : 0 0 pps
High : 0 0 pps
RED-dropped bytes : 1904281695 48194816 bps
Low : 1904281695 48194816 bps
Medium-low : 0 0 bps
Medium-high : 0 0 bps
High : 0 0 bps
...
NOTE: This step shows command output for queue 0 (forwarding class be) only.
The command output shows that the GRE tunnel device transmits traffic from queue 0 at a rate of
4879 pps. Allowing for 182 bytes per Layer 3 packet, preceded by 24 bytes of GRE overhead (a 20-byte
delivery header consisting of the IPv4 packet header followed by 4 bytes for GRE flags plus encapsulated
protocol type), the traffic rate received at the tunnel destination device is 8,040,592 bps:
4879 packets/second X 206 bytes/packet X 8 bits/byte = 8,040,592 bits/second
Configuring Output Scheduling and Shaping at GRE Tunnel Physical and Logical Interfaces
34
To configure the GRE tunnel device with scheduling and shaping at GRE tunnel physical and logical
interfaces:
1. Define eight transmission queues.
[edit]
user@host# set class-of-service forwarding-classes queue 0 be
user@host# set class-of-service forwarding-classes queue 1 ef
user@host# set class-of-service forwarding-classes queue 2 af
user@host# set class-of-service forwarding-classes queue 3 nc
user@host# set class-of-service forwarding-classes queue 4 be1
user@host# set class-of-service forwarding-classes queue 5 ef1
user@host# set class-of-service forwarding-classes queue 6 af1
user@host# set class-of-service forwarding-classes queue 7 nc1
NOTE: To configure up to eight forwarding classes with one-to-one mapping to output

queues for interfaces on M120 , M320, MX Series, and T Series routers and EX Series switches,
use the queue statement at the [edit class-of-service forwarding-classes] hierarchy level.
If you need to configure up to 16 forwarding classes with multiple forwarding classes mapped
to single queues for those interface types, use the class statement instead.
2. Configure BA classifier gr-inet that, based on IPv4 precedence bits set in an incoming packet, sets the
forwarding class, loss-priority value, and DSCP bits of the packet.
[edit]
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class be loss-priority low
code-points 000
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class ef loss-priority low
code-points 001
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class af loss-priority low
code-points 010
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class nc loss-priority low
code-points 011
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class be1 loss-priority low
code-points 100
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class ef1 loss-priority low
code-points 101
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class af1 loss-priority low
code-points 110
35
user@host# set class-of-service classifiers inet-precedence gr-inet forwarding-class nc1 loss-priority low
code-points 111
3. Apply BA classifier gr-inet to the GRE tunnel device input at logical interface ge-1/1/0.0.
[edit]
user@host# set class-of-service interfaces ge-1/1/0 unit 0 classifiers inet-precedence gr-inet
4. Define a scheduler for each forwarding class.
[edit]
user@host# set class-of-service schedulers be_sch transmit-rate percent 30
user@host# set class-of-service schedulers ef_sch transmit-rate percent 40
user@host# set class-of-service schedulers af_sch transmit-rate percent 25
user@host# set class-of-service schedulers nc_sch transmit-rate percent 5
user@host# set class-of-service schedulers be1_sch transmit-rate percent 60
user@host# set class-of-service schedulers be1_sch priority low
user@host# set class-of-service schedulers ef1_sch transmit-rate percent 40
user@host# set class-of-service schedulers ef1_sch priority medium-low
user@host# set class-of-service schedulers af1_sch transmit-rate percent 10
user@host# set class-of-service schedulers af1_sch priority strict-high
user@host# set class-of-service schedulers nc1_sch shaping-rate percent 10
user@host# set class-of-service schedulers nc1_sch priority high
5. Define a scheduler map for each of three GRE tunnels.
[edit]
user@host# set class-of-service scheduler-maps sch_map_1 forwarding-class be scheduler be_sch
user@host# set class-of-service scheduler-maps sch_map_1 forwarding-class ef scheduler ef_sch
user@host# set class-of-service scheduler-maps sch_map_1 forwarding-class af scheduler af_sch
user@host# set class-of-service scheduler-maps sch_map_1 forwarding-class nc scheduler nc_sch
user@host# set class-of-service scheduler-maps sch_map_2 forwarding-class be scheduler be1_sch
user@host# set class-of-service scheduler-maps sch_map_2 forwarding-class ef scheduler ef1_sch
user@host# set class-of-service scheduler-maps sch_map_3 forwarding-class af scheduler af_sch
user@host# set class-of-service scheduler-maps sch_map_3 forwarding-class nc scheduler nc_sch
6. Define traffic control profiles for three GRE tunnel interfaces.
[edit]
36
user@host# set class-of-service traffic-control-profiles gr-ifl-tcp1 scheduler-map sch_map_1

user@host# set class-of-service traffic-control-profiles gr-ifl-tcp1 shaping-rate 8m
user@host# set class-of-service traffic-control-profiles gr-ifl-tcp1 guaranteed-rate 3m
user@host# set class-of-service traffic-control-profiles gr-ifl-tcp shaping-rate 10m
user@host# set class-of-service traffic-control-profiles gr-ifl-tcp-remain shaping-rate 7m
user@host# set class-of-service traffic-control-profiles gr-ifl-tcp-remain guaranteed-rate 4m
7. Apply CoS scheduling and shaping to the output traffic at the physical interface and logical interfaces.
[edit]
user@host# set class-of-service interfaces gr-1/1/10 output-traffic-control-profile gr-ifd-tcp
user@host# set class-of-service interfaces gr-1/1/10 output-traffic-control-profile-remaining gr-ifd-remain
user@host# set class-of-service interfaces gr-1/1/10 unit 1 output-traffic-control-profile gr-ifl-tcp1
[edit]
user@host# commit
Results
From configuration mode, confirm your configuration by entering the show class-of-service
forwarding-classes, show class-of-service classifiers, show class-of-service interfaces ge-1/1/0,
show class-of-service schedulers, show class-of-service scheduler-maps, show class-of-service
traffic-control-profiles, and show class-of-service interfaces gr-1/1/10 commands. If the output does not
display the intended configuration, repeat the instructions in this example to correct the configuration.
Confirm the configuration of output scheduling and shaping at the GRE tunnel physical and logical interfaces.
user@host# show class-of-service forwarding-classes

queue 0 be;
queue 1 ef;
queue 2 af;
queue 3 nc;
queue 4 be1;
37
queue 5 ef1;
queue 6 af1;
queue 7 nc1;
user@host# show class-of-service classifiers

inet-precedence gr-inet {
forwarding-class be {
loss-priority low code-points 000;
}
forwarding-class ef {
}
forwarding-class af {
}
forwarding-class nc {
}
forwarding-class be1 {
}
forwarding-class ef1 {
}
forwarding-class af1 {
}
forwarding-class nc1 {
}
}
user@host# show class-of-service interfaces ge-1/1/0

unit 0 {
classifiers {
inet-precedence gr-inet;
}
}
user@host# show class-of-service schedulers

be_sch {
}
ef_sch {
38

}
af_sch {
}
nc_sch {
}
be1_sch {
priority low;
}
ef1_sch {
priority medium-low;
}
af1_sch {
priority strict-high;
}
nc1_sch {
shaping-rate percent 10;
priority high;
}
user@host# show class-of-service scheduler-maps

sch_map_1 {
forwarding-class be scheduler be_sch;
forwarding-class ef scheduler ef_sch;
forwarding-class af scheduler af_sch;
forwarding-class nc scheduler nc_sch;
}
sch_map_2 {
forwarding-class be scheduler be1_sch;
forwarding-class ef scheduler ef1_sch;
}
sch_map_3 {
}
user@host# show class-of-service traffic-control-profiles

gr-ifl-tcp1 {
scheduler-map sch_map_1;
39
shaping-rate 8m;
guaranteed-rate 3m;
}
gr-ifl-tcp2 {
guaranteed-rate 2m;
}
gr-ifl-tcp3 {
guaranteed-rate 5m;
}
gr-ifd-remain {
shaping-rate 7m;
guaranteed-rate 4m;
}
gr-ifd-tcp {
shaping-rate 10m;
}
user@host# show class-of-service interfaces gr-1/1/10

gr-1/1/10 {
output-traffic-control-profile gr-ifd-tcp;
output-traffic-control-profile-remaining gr-ifd-remain;
unit 1 {
output-traffic-control-profile gr-ifl-tcp1;
}
unit 2 {
}
unit 3 {
}
}
Verification
IN THIS SECTION
Verifying That Scheduling and Shaping Are Attached to the GRE Tunnel Interfaces | 40
Verifying That Scheduling and Shaping Are Functioning at the GRE Tunnel Interfaces | 41
40
Confirm that the configurations are working properly.
Verifying That Scheduling and Shaping Are Attached to the GRE Tunnel Interfaces
Purpose
Verify the association of traffic control profiles with GRE tunnel interfaces.
Action
Verify the traffic control profile attached to the GRE tunnel physical interface by using the show
class-of-service interface gr-1/1/10 detail operational mode command.
• user@host> show class-of-service interface gr-1/1/10 detail
Physical interface: gr-1/1/10, Enabled, Physical link is Up

Type: GRE, Link-level type: GRE, MTU: Unlimited, Speed: 1000mbps
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps
Physical interface: gr-1/1/10, Index: 220

Queues supported: 8, Queues in use: 8
Output traffic control profile: gr-ifd-tcp, Index: 17721
Output traffic control profile remaining: gr-ifd-remain, Index: 58414
Congestion-notification: Disabled
Logical interface gr-1/1/10.1

Flags: Point-To-Point SNMP-Traps 0x4000 IP-Header
10.70.1.3:10.70.1.1:47:df:64:0000000000000000 Encapsulation: GRE-NULL
Gre keepalives configured: Off, Gre keepalives adjacency state: down
inet 10.100.1.1/24
Logical interface: gr-1/1/10.1, Index: 331
Object Name Type Index
Traffic-control-profile gr-ifl-tcp1 Output 17849
Classifier ipprec-compatibility ip 13

inet 10.200.1.1/24

41

inet 10.201.1.1/24
Meaning
Ingress IPv4 traffic routed to GRE tunnels on the device is subject to CoS output scheduling and shaping.
Verifying That Scheduling and Shaping Are Functioning at the GRE Tunnel Interfaces
Purpose
Verify the traffic rate shaping at the GRE tunnel interfaces.
Action
1. Pass traffic through the GRE tunnel at logical interfaces gr-1/1/10.1, gr-1/1/10.2, and gr-1/1/10.3.
2. To verify the rate shaping at each GRE tunnel source, use the show interfaces queue operational mode
command.
The following example command output shows detailed CoS queue statistics for logical interface
gr-1/1/10.1 (the GRE tunnel from source IP address 10.70.1.1 to destination IP address 10.70.1.3):
user@host> show interfaces queue gr-1/1/10.1
Logical interface gr-1/1/10.1 (Index 331) (SNMP ifIndex 4045)

Burst size: 0
Queued:
Packets : 59613061 51294 pps
Bytes : 12220677505 84125792 bps
Transmitted:
Packets : 2230632 3039 pps
Bytes : 457279560 4985440 bps
Low : 49602496 46053 pps
42
High : 3308787 0 pps

Low : 10168511680 75528000 bps
High : 678301335 0 bps
Queue: 1, Forwarding classes: ef
Queued:
Packets : 15344874 51295 pps
Bytes : 3145699170 84125760 bps
Transmitted:
Packets : 366115 1218 pps
Bytes : 75053575 1997792 bps
Low : 14614270 48945 pps
High : 0 0 pps
Low : 2995925350 80270528 bps
High : 0 0 bps
...
NOTE: This step shows command output for queue 0 (forwarding class be) and queue 1
(forwarding class ef) only.
Meaning
Now that traffic shaping is attached to the GRE tunnel interfaces, the command output shows that traffic
shaping specified for the tunnel at logical interface gr-1/1/10.1 (shaping-rate 8m and guaranteed-rate 3m)
is honored.
• For queue 0, the GRE tunnel device transmits traffic at a rate of 3039 pps. The traffic rate received at
the tunnel destination device is 5,008,272 bps:

43
• For queue 0, the GRE tunnel device transmits traffic at a rate of 1218 pps. The traffic rate received at
the tunnel destination device is 2,007,264 bps:
Compare these statistics to the baseline measurements taken without traffic shaping, as described in
“Measuring GRE Tunnel Transmission Rates Without Shaping Applied” on page 32.
Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs
You can configure ingress CoS parameters, including hierarchical schedulers, on MX Series routers with
Enhanced Queuing DPCs (that is, line cards that have a queuing chip). In general, the supported configuration
statements apply to per-unit schedulers or to hierarchical schedulers.
NOTE: Ingress CoS is not supported on line cards that do not contain a queuing chip.
To configure ingress CoS for per-unit schedulers, include the following statements at the [edit
class-of-service interfaces interface-name] hierarchy level:
NOTE: The input-scheduler-map and input-traffic-control-profile statements are mutually

exclusive at the same hierarchy level.
[edit class-of-service interfaces interface-name]

input-excess-bandwidth-share (proportional value | equal);
input-scheduler-map map-name;
input-shaping-rate rate;
input-traffic-control-profile profile-name shared-instance instance-name;
unit logical-unit-number;
44
input-shaping-rate (percent percentage | rate);

}
To configure ingress CoS for hierarchical schedulers, include the interface-set interface-set-name statement
at the [edit class-of-service interfaces] hierarchy level:

interface-set interface-set-name {
input-traffic-control-profile-remaining profile-name;
interface interface-name {
}
}
}
By default, ingress CoS features are disabled on the Enhanced Queuing DPC.
For an Enhanced Queuing (EQ) DPC on an MX Series router, CoS queuing and scheduling are enabled on
the egress side but disabled on the ingress side by default. To enable ingress CoS on the EQ DPC, you
must configure the traffic-manager statement with ingress-and-egress mode:
[edit chassis fpc slot-number pic pic-number]

traffic-manager mode ingress-and-egress;
NOTE: If you enable ingress CoS settings and inline services on the same FPC, the FPC moves
to the offline state. This behavior is expected because traffic black hole detection is triggered
that causes the FPC to move to the offline state.
Configured CoS features on the ingress are independent of CoS features on the egress, with the following
exceptions:
• If you configure a per-unit or hierarchical scheduler at the [edit class-of-service interfaces] hierarchy
level, the schedulers apply in both the ingress and egress directions.
45
• You cannot configure the same logical interface on an ingress and an egress interface set. A logical
interface can only belong to one interface set.
• The DPC’s frame buffer of 512 MB is shared between ingress and egress configurations.
The following behavior aggregate (BA) classification tables are supported on the ingress side of the Enhanced
Queuing DPC:
• inet-precedence
• DSCP
• exp (MPLS)
• DSCP for IPv6
• IEEE 802.1p

46
CHAPTER 2
Configuring Hierarchical Class of Service on MICs,

MPCs, MLCs, and Aggregated Ethernet Interfaces
IN THIS CHAPTER
Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces Overview | 55
Example: Configuring Scheduling Modes on Aggregated Interfaces | 70
Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip | 76
Understanding Hierarchical Scheduling for MIC and MPC Interfaces
IN THIS SECTION
Scheduler Node Scaling for MIC and MPC Interfaces | 47
Hierarchical Scheduling Priority Levels for MIC and MPC Interfaces | 47
Guaranteed Bandwidth and Weight of an Interface Node on MIC and MPC Interfaces | 48
Hierarchical Scheduling for MIC and MPC Interfaces in Oversubscribed PIR Mode | 48

47
Scheduler Node Scaling for MIC and MPC Interfaces
In per-unit scheduling, the logical interfaces share a common level 2 node (one per port). In
hierarchical-scheduling, each logical interface has its own level 2 node. Thus, scaling is limited by the
number of level 2 nodes.
To better control system resources in hierarchical-scheduling mode, you can limit the number of scheduler
node levels to two. In this case, all logical interfaces and interface sets with CoS scheduling policy share
a single level 2 node. Consequently, the maximum number of logical interfaces with CoS scheduling policies
is increased (the interface sets must be at level 3).
To configure scheduler node scaling, include the hierarchical-scheduler statement and set the
maximum-hierarchy-levels option to 2 at the [edit interfaces xe-fpc/pic/port] hierarchy level.
[edit interfaces]
xe-2/0/0 {
hierarchical-scheduler {
maximum-hierarchy-levels 2;
}
}
NOTE: The maximum-hierarchy-levels option supports level 3 interface sets but not level 2
interface sets. If you configure level 2 interface sets with the maximum-hierarchy-levels option,
you generate Packet Forwarding Engine errors.
Hierarchical Scheduling Priority Levels for MIC and MPC Interfaces
The queuing model used by MIC and MPC interfaces supports three priority levels for guaranteed scheduling
priority and two lower priority levels for excess scheduling priority. You can configure a queue with one
guaranteed priority and one excess priority. For example, you can configure a queue for guaranteed low
(GL) as the guaranteed priority and configure excess high (EH) as the excess priority.
You can associate a guaranteed level with only one excess level. You can associate an excess level with
any number of guaranteed priority levels, including none.
Interface nodes maintain their guaranteed priority level (for example, guaranteed high, GH) as long as they
do not exceed their guaranteed bandwidth. If the queue bandwidth exceeds the guaranteed rate, then the
priority drops to the excess priority (for example, excess high, EH). Because excess level priorities are lower
than their guaranteed counterparts, the bandwidth guarantees for each of the other levels can be maintained.
48
Guaranteed Bandwidth and Weight of an Interface Node on MIC and MPC Interfaces
The queuing model used by MIC and MPC interfaces separates the concepts of guaranteed bandwidth and
weight of an interface node, although the two terms are often used interchangeably. The guaranteed
bandwidth for an interface node is the bandwidth the node can use, independent of what is happening at
the other nodes of the scheduling hierarchy. The weight of an interface node, on the other hand, is a value
that determines how excess bandwidth is used. The weight of a node comes into play when other nodes
at the same hierarchical scheduling level use less than the sum of their guaranteed bandwidths
For some application traffic types (such as constant bit rate voice, where there is little concern about
excess bandwidth), the guaranteed bandwidth dominates the node. For other types of application traffic
(such as bursty data, where a well-defined bandwidth is not always possible), the concept of weight
dominates the node.
Hierarchical Scheduling for MIC and MPC Interfaces in Oversubscribed PIR Mode
In contrast to the Intelligent Queuing Enhanced (IQE) and Intelligent Queuing 2 Enhanced (IQ2E) PICs, the
interfaces on MICs and MPCs set the guaranteed rate to zero in oversubscribed peak information rate
(PIR) mode for the per-unit scheduler. Also, the configured rate is scaled down to fit the oversubscribed
value. For example, if there are two logical interface units with a shaping rate of 1 Gbps each on a 1-Gbps
port (which is, therefore, oversubscribed 2 to 1), then the guaranteed rate on each unit is scaled down to
500 Mbps (scaled down by 2).
With hierarchical schedulers in oversubscribed PIR mode, the guaranteed rate for every logical interface
unit is set to zero. This means that the queue transmit rates are always oversubscribed.
Because in oversubscribed PIR mode the queue transmit rates are always oversubscribed, the following
are true:
• If the queue transmit rate is set as a percentage, then the guaranteed rate of the queue is set to zero;
but the excess rate (weight) of the queue is set correctly.
• If the queue transmit rate is set as an absolute value and if the queue has guaranteed high or medium
priority, then traffic up to the queue’s transmit rate is sent at that priority level. However, for guaranteed
low traffic, that traffic is demoted to the excess low region. This means that best-effort traffic well within
the queue’s transmit rate gets a lower priority than out-of-profile excess high traffic. This differs from
the IQE and IQ2E PICs.
CoS Features and Limitations on MIC and MPC Interfaces
49
Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces
You can configure ingress CoS parameters, including hierarchical schedulers, on MIC and MPC interfaces
on MX Series routers. In general, the supported configuration statements apply to per-unit schedulers or
to hierarchical schedulers.
NOTE: Ingress CoS is not supported on AE interfaces on MPCs.
To configure ingress CoS for per-unit schedulers, include the following statements at the [edit
class-of-service interfaces interface-name] hierarchy level:

input-traffic-control-profile profile-name;
To configure ingress CoS for hierarchical schedulers, include the interface-set interface-set-name statement
at the [edit class-of-service interfaces] hierarchy level:

}
}
50
By default, ingress CoS features are disabled on MIC and MPC interfaces. To enable ingress CoS on a MIC
or MPC interface, configure the traffic-manager statement with ingress-and-egress mode as shown in the
following example:
chassis {
fpc 7 {
pic 0 {
traffic-manager {
mode ingress-and-egress;
}
}
}
}
Configured CoS features on the ingress are independent of CoS features on the egress.
NOTE: Before Junos OS 16.1R1, for MIC-based MX80 and MX104 routers, only ten queues on
one MIC can be configured for ingress CoS. Starting with Junos OS 16.1R1, MX80 and MX104
routers support up to 12 ingress queues on any combination of both MIC and built-in ports.
Starting with Junos 17.4R2 on MX80 and MX104 routers, you can have precise control over
which ports have ingress CoS enabled by configuring traffic-manager at the port level ([edit
chassis fpc slot-number pic pic-number port port-number] hierarchy level). You cannot, however,
configure traffic-manager at both the port level and PIC level on the same device.
NOTE: HQoS MPC cards installed in MX240, MX480, MX960, MX2008, MX2010, and MX2020
routers have a hardware limitation with an ingress queuing CoS "ingress-and-egress" configuration.
Ingress queuing can be enabled for a maximum of 10 ports per MIC Slot, resulting in 20 ports
per MPC2E-3D-NG HQoS and MPC3E-3D-NG HQoS line card with 10 ports per MIC slot. In
the XM chip there are 16 loopback streams allocated per port group for PG0 and PG1, where
PG0 is mapped to MIC slot 0 and PG1 is mapped to MIC slot 1. On enabling ingress queuing on
a PIC slot, one loopback stream from the XM chip is allocated per interface from the respective
port group. Because there are only 16 loopback streams, out of which 2 are used by default and
4 are used for tunnel interfaces and inline services, 10 streams are left for ingress CoS.
51
The following behavior aggregate (BA) classification tables are supported on the ingress side of MIC and
MPC interfaces:
• DSCP
• DSCP for IPv6
• exp (MPLS)
• IEEE 802.1p
• inet-precedence
Release Description
17.4R2 Starting with Junos 17.4R2 on MX80 and MX104 routers, you can have precise control over
which ports have ingress CoS enabled by configuring traffic-manager at the port level
16.1R1 Starting with Junos OS 16.1R1, MX80 and MX104 routers support up to 12 ingress queues
on any combination of both MIC and built-in ports.
Per-Unit Queuing and Hierarchical Queuing for MIC and MPC Interfaces
IN THIS SECTION
Queuing Models Supported for MIC and MPC Interfaces | 52
Scheduler Node Levels for MIC and MPC Interfaces | 53

52
Queuing Models Supported for MIC and MPC Interfaces
IN THIS SECTION
Limited Scale Per-Unit Queuing MPCs | 52
Hierarchical Queuing MICs and MPCs | 52
Interfaces hosted on Modular Interface Card (MIC) and Modular Port Concentrator (MPC) line cards in
MX Series 5G Universal Routing Platforms support the following models of class-of-service (CoS) queuing,
depending on MIC or MPC type:
Limited Scale Per-Unit Queuing MPCs

Per-unit CoS queuing features on a limited scale are supported for interfaces hosted on some MPCs that
do not have a dedicated queuing chip, specifically the MPC3E, MPC4E, MPC5E, and MPC6E line cards
and on the fixed-configuration 16-port 10-Gigabit Ethernet MPC in MX240, MX480, MX960, MX2010,
and MX2020 routers.
NOTE: The nonqueuing MPC1 and MPC2 line cards do not support per-unit queuing.
On MPCs that support per-unit queuing, the following queuing capabilities are available:
• Four or eight egress queues per unit.
• Delay buffer capacities of 100 ms by default, and up to 200 ms maximum delay.
• Rate shaping of the ports and their queues.
• Guaranteed rate enforced at the queues.
The per-unit CoS queuing features also support pre-classification of incoming packets to protect high
priority packets in the event of congestion. Such features include ingress DSCP rewrite and per-VLAN
classification, ingress and egress policing, and rewrites.
Hierarchical Queuing MICs and MPCs

Hierarchical CoS queuing features are supported on interfaces hosted on MICs in MPC1 Q, MPC2 Q,
MPC2 EQ, MPC5EQ, MPC7E, MPC8E, and MPC9E line cards in MX204, MX240, MX480, MX960, MX2010,
MX2020, and MX10003 routers and for interfaces hosted on 1-Gigabit and 10-Gigabit Ethernet MICs in
MX5, MX10, MX40, MX80, or MX104 modular chassis routers. These MICs and MPCs provide a dedicated
queuing chip that supports hierarchical queuing.
53
Hierarchical queuing MICs and MPCs support all per-unit queuing functionality plus fine-grained queuing
abilities over four or five levels of hierarchical scheduling:
• Hierarchical scheduling with ports, interface sets, and logical interfaces.
• Shaping—Committed Information Rate (CIR) and a peak information rate (PIR)—at all scheduling levels,
including queues.
• Three normal- priority levels and two excess- priority levels configurable at all scheduling levels, including
queues.
• Per-priority shaping of traffic at Level 1 or Level 2.
• Shaping for unconfigured customer VLANs (C-VLANs) and for service VLANs (S-VLANs).
Scheduler Node Levels for MIC and MPC Interfaces
IN THIS SECTION
Scheduler Node Levels for Per-Unit Queuing MPCs | 53
Scheduler Node Levels for Hierarchical Queuing MICs and MPCs | 54
Interfaces hosted on MICs and MPCs support different scheduler node levels, depending on MIC or MPC
type:
Scheduler Node Levels for Per-Unit Queuing MPCs

For an interface hosted on a per-unit queuing MPC, each logical interface has its own dedicated level 3
node, and all logical interfaces share a common level 2 node (one per port).
Figure 4 on page 54 illustrates scheduler node levels for an interface hosted on a per-unit queuing MPC.
54
Figure 4: Scheduler Node Levels for Per-Unit Queuing MPCs
Logical interface (unit) Physical interface
Level 3
Level 3 Dummy Level 2 node Level 1 node
g017445
Level 3
For interfaces hosted on per-unit queuing MPCs, the level 2 node is always a dummy node.
Scheduler Node Levels for Hierarchical Queuing MICs and MPCs

With the exception of the 10-Gigabit Ethernet MPC with SFP+, the queuing model used by interfaces
hosted on hierarchical queuing MICs and MPCs supports up to five levels of scheduler nodes: the queue
itself (level 5), session logical interface (ppp or dhcp) (level 4), customer VLAN (C-VLAN) (level 3), the
interface set or service VLAN (S-VLAN) collection (level 2), and the physical interface or port (level 1).
Figure 5 on page 54 illustrates the scheduler node levels for an interface hosted on a hierarchical queuing
MIC or MPC.
Figure 5: Scheduler Node Levels for Interfaces on Hierarchical Queuing and Scheduling MICs and MPCs
Logical interface (unit) Interface set Physical interface
Level 3 Level 2 node
Level 3 Level 2 node Level 1 node

g017446
The figure depicts scheduler nodes for an interface that does not include interface sets and for which
traffic control profiles are applied to the logical interfaces only.
NOTE: If an interface set has a CoS scheduling policy but none of its child logical interfaces has
a CoS scheduling policy, then the interface set is considered to be a leaf node and has one level 2
and one level 3 node.
55

MX Series MPC Overview
MPCs Supported by MX Series Routers
MX Series MIC Overview
MICs Supported by MX Series Routers
MX5, MX10, MX40, and MX80 Modular Interface Card Description
Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces
Overview
Queuing Ethernet Modular Port Concentrators (MPCs) provide a set of dedicated queues for subscriber
interfaces configured with hierarchical scheduling or per-unit scheduling.
The dedicated queues offered on these MPCs enable service providers to reduce costs through different
scaling configurations. These queuing MPCs enable service providers to reduce the cost per subscriber
by allowing many subscriber interfaces to be created with four or eight queues.
This topic describes the overall queue, scheduler node, and logical interface scaling for subscriber interfaces
created on these MIC and MPC combinations.
Queue Scaling for MPCs
Beginning with Junos OS Release 15.1, MPC2E-3D-NG-Q, MPC3E-3D-NG-Q, MPC5EQ-40G10G, and

MPC5EQ-100G10G MPCs support up to five levels of hierarchical queuing. Beginning with Junos OS
Release 16.1R1, MPC7 line cards also support five levels of hierarchical queuing. Table 8 on page 55 lists
the number of dedicated queues and nodes supported per MPC.
Table 8: Dedicated Queues for MPCs
Dedicated Level 1 Nodes

MPC Queues Level 4 Nodes Level 3 Nodes Level 2 Nodes (Ports)
MPC2E-3D-NG-Q 512,000 64,000 16,000 4000 384
MPC3E-3D-NG-Q
MPC5EQ-40G10G 1 million 128,000 32,000 4000 384
MPC5EQ-100G10G
56
Table 8: Dedicated Queues for MPCs (continued)
Dedicated Level 1 Nodes

MPC Queues Level 4 Nodes Level 3 Nodes Level 2 Nodes (Ports)
MPC7 256,000 32,000 8000 4000 126
CAUTION: The maximum scaling targets provided in Table 8 on page 55 are based
on system level design specifications. Actual realized subscriber or session scale is
highly dependent upon the configuration and can be influenced by configuration
variables including: the number of routes, the number of enabled services, the number
of policy and firewall filters, policers, counters, statistics and access model type. Once
you define a configuration, your Juniper account team can help characterize the
expected system level scale or scale range for your live deployment.
MPCs vary in the number of Packet Forwarding Engines on board. MPC2E-3D-NG-Q and MPC3E-3D-NG-Q
MPCs each have one Packet Forwarding Engine, allowing all 64,000 level 4 (subscriber) nodes to be
allocated to a single MIC. MPC5EQ MPCs have two Packet Forwarding Engines, one for each possible
MIC, each supporting 64,000 level 4 (subscriber) nodes.
NOTE: The nonqueuing MPCs MPC2E-3D-NG, MPC3E-3D-NG, MPC5E-40G10G, and

MPC5E-100G10G provide up to eight queues per port in standard configuration. However, each
of these MPCs can be configured to provide limited-scale hierarchical class of service (HCoS)
and up to 32,000 queues.
Managing Remaining Queues
In Junos OS releases earlier than Release 15.1R4, SNMP traps generate system log messages to notify
you:
• When the number of available dedicated queues on the MPC drops below 10 percent. For example:
Mar 15 14:55:22.977 host cosd[1963]: COSD_OUT_OF_DEDICATED_QUEUES: Queue usage

count for interface xe-3/0/0 is at 90 percent
• When the maximum number of dedicated queues on the MPCs is reached. For example,
57
Mar 15 18:01:59.344 host cosd[3848]: COSD_OUT_OF_DEDICATED_QUEUES: Queue usage

count for interface xe-3/0/0 is at 100 percent.
When the maximum number of dedicated queues is allocated, the system does not provide subsequent
subscriber interfaces with a dedicated set of queues. For per-unit scheduling configurations, there are
no configurable queues remaining on the MPC.
For hierarchical scheduling configurations, remaining queues are available when the maximum number of
dedicated queues is reached on the MPC. Traffic from these logical interfaces is considered unclassified
and attached to a common set of queues that are shared by all subsequent logical interfaces. These common
queues are the default port queues that are created for every port. You can configure a traffic-control
profile and attach that to the interface to provide CoS parameters for the remaining queues. These subscriber
interfaces remain with this traffic-control profile, even if dedicated queues become available.
NOTE: Starting in Junos OS Release 15.1R4, the COSD_OUT_OF_DEDICATED_QUEUES

functionality is not available for QoS-enabled dynamic subscribers. Starting in Junos OS Release
17.4R1, CoS resource monitoring enables you to set a per-FPC queue threshold of up to 90
percent of resources bound to a scheduling hierarchy; subscriber logins are not allowed when
the threshold is reached. However, this threshold applies to all queues, not dedicated queues
alone. See Resource Monitoring for Subscriber Management and Services Overview for more
information.
Release Description
16.1R1 Beginning with Junos OS Release 16.1R1, MPC7 line cards also support five levels of
hierarchical queuing.
15.1R1 Beginning with Junos OS Release 15.1, MPC2E-3D-NG-Q, MPC3E-3D-NG-Q,

MPC5EQ-40G10G, and MPC5EQ-100G10G MPCs support up to five levels of hierarchical
queuing.
Hierarchical Class of Service User Guide

Managing Dedicated and Remaining Queues for Static CoS Configurations on MIC and MPC Interfaces
58
Managing Dedicated and Remaining Queues for Dynamic CoS Configurations on MIC and MPC Interfaces
Jitter Reduction in Hierarchical CoS Queues
IN THIS SECTION
Queue Jitter as a Function of the Maximum Number of Queues | 58
Default Maximum Queues for Hierarchical Queuing MICs and MPCs | 58
Shaping Rate Granularity as a Function of the Rate Wheel Update Period | 59
Queue Jitter as a Function of the Maximum Number of Queues
Each queuing chip on a Modular Interface Card (MIC) or Modular Port Concentrator (MPC) internally hosts
a rate wheel thread that updates the shaper credits into the shapers available at each level of scheduling
hierarchy. At each hierarchy level, the length of this update period determines two key characteristics of
scheduling:
• The minimum buffer needed for the queue to pass packets without dropping.
• The degree of jitter encountered in the queue.
At each hierarchy level, the length of the rate wheel update period is dependent upon the number of
entities enabled for that node level. Because traffic is queued at Level 5 (queues) and scheduled upwards
to Level 1 (the port), the number of entities (queues) enabled at Level 5 determines the number of entities
(logical interfaces, interface-sets, or ports) enabled at the other levels of the scheduling hierarchy. By
extension, the number of queues enabled for a given scheduler node hierarchy determines the length of
the update period at all hierarchy levels. Consequently, limiting the maximum number of queues supported
by a hierarchical queuing MIC or MPC can reduce jitter in the queues. To configure the maximum number
of queues allowed per hierarchical queuing MIC or MPC, include the max-queues statement at the [edit
chassis fpc slot-number] hierarchy level.
Default Maximum Queues for Hierarchical Queuing MICs and MPCs
The QX chip on a MIC or MPC consists of two symmetrical halves, and each half supports a maximum of
64 K queues (128 K queues per QX chip). The 2-port and 4-port 10-Gigabit Ethernet MICs with XFP and
the MPC1_Q line cards have one chipset and can support a maximum of 128 K queues, distributed across
59
the two partitions of the single QX chip. The MPC2 Q and MPC2 EQ line cards have two chipsets and can
support a maximum of 256 K queues, distributed across the four partitions of the two QX chips.
Table 9 on page 59 lists the maximum number of queues supported by default and the corresponding rate
wheel update period for each hierarchical queuing MIC or MPC.
Table 9: Default Maximum Queues and Corresponding Rate Wheel Update Periods
Maximum Rate Wheel

Router Model Hierarchical Queuing MIC or MPC Queues Update Period
MX5, 2-port 10-Gigabit Ethernet MIC with XFP 128 K 1.6 ms

MX10,
The chassis base board hosts one chipset-based Packet Forwarding
MX40, and
Engine process that operates in standalone mode. The single QX
MX80 modular
chip is composed of two partitions that each support 64 K queues
for egress ports.
MX240, MPC1 Q 128 K 1.6 ms

MX480,
The MPC1 Q line card hosts one chipset-based Packet Forwarding
MX960,
Engine process that operates in fabric mode. The single QX chip is
MX2010, and
composed of two partitions that each support 64 K queues for egress
MX2020
ports.
MPC2 Q 256 K 1.6 ms
The MPC2 Q line card hosts two chipset-based Packet Forwarding

Engine processes that operate in fabric mode. The two QX chips
are composed of four partitions that each support 64 K queues for
egress ports.
MPC2 EQ 256 K 2.6 ms
The MPC2 EQ line card hosts two chipset-based Packet Forwarding

Engine processes that operate in fabric mode. The two QX chips
are composed of four partitions that each support 64 K queues for
egress ports.
You can configure hierarchical queuing MICs and MPCs to support a reduced maximum number of queues.
Doing so reduces the rate wheel update period used by the QX chip, which in turn reduces jitter in the
queues for the egress interfaces hosted on the line card.
Shaping Rate Granularity as a Function of the Rate Wheel Update Period
Reducing the length of the QX chip rate wheel update period, in addition to reducing jitter in the hierarchical
scheduling queues, also indirectly increases the shaping granularity.
60
For a given port line rate and scheduling hierarchy level, the shaping granularity is a function of the minimum
shaper credit size and the rate wheel update period in effect as a result of the number of queues supported
by the line card.
shaping granularity = minimum shaper credit size / rate wheel update period
Table 10 on page 60 shows how shaping granularity is calculated for non-enhanced hierarchical queuing
MIC and MPC line cards with default values for minimum shaper credit size and for rate wheel update
period.
Table 10: Default Shaping Granularities on Non-Enhanced Queuing MICs and MPCs
Non-EnhancedQueuingMICorMPCDefaults
PortType Hierarchy Level Minimum Credit Update Period Calculation of Shaping Granularity
1 Gbps Level 1 (port), 4 bytes = 32 bits 13.33 ms = 32 bits / 0.01333 sec = 2.4 Kbps
Queuing Level 4 (queues) 0.01333 sec
Level 2, Level 3 16 bytes = 1.66 ms = 128 bits / 0.01333 sec = 9.6 Kbps
128 bits 0.00166 sec
10 Gbps Level 1 (port), 16 bytes = 13.33 ms = 128 bits / 0.01333 sec = 9.6 Kbps
Queuing Level 4 (queues) 128 bits 0.01333 sec
Level 2, Level 3 64 bytes = 1.66 ms = 512 bits / 0.01333 sec = 38.4 Kbps
512 bits 0.00166 sec

61
Example: Reducing Jitter in Hierarchical CoS Queues
IN THIS SECTION
Requirements | 61
Overview | 61
Configuration | 61
This example shows how to reduce jitter in the output queues for VLAN ports hosted on a hierarchical
queuing MPC.
Requirements
This example uses the following Juniper Networks hardware and Junos OS software:
• MX960 router in an IPv4 network and running Junos OS Release 13.2 or later.
• Available Gigabit Ethernet port hosted on FPC slot 2, PIC slot 0, port 0.
• Available Gigabit Ethernet port hosted on port 0 of a Gigabit Ethernet Modular Interface Card (MIC) in
PIC slot 0 of an MPC2 Q Modular Port Concentrator (MPC) in FPC slot 5.
Before you begin configuring this example, make sure that the maximum number of queues allowed for
the hierarchical queuing MPC in slot 5 has not yet been configured. When you enter the show chassis fpc
5 command from configuration mode, the max-queues statement should not display.
Overview
In this example you configure hierarchical scheduling on a VLAN port hosted on a hierarchical queuing
MPC. To reduce jitter in the queues for all egress ports hosted on the MPC, reduce the maximum number
of queues allowed for MPC.
Configuration

62
set interfaces xe-2/0/0 per-unit-scheduler

set interfaces xe-2/0/0 flexible-vlan-tagging
set interfaces xe-2/0/0 unit 0 vlan-id 1
set interfaces xe-2/0/0 unit 0 family inet address 10.1.1.1/24
set interfaces xe-2/0/0 unit * classifiers ieee-802.1 ieee_jitter
set interfaces xe-5/0/0 per-unit-scheduler
set interfaces xe-5/0/0 flexible-vlan-tagging
set interfaces xe-5/0/0 unit 0 vlan-id 1
set interfaces xe-5/0/0 unit 0 family inet address 10.2.1.1/24
set class-of-service-interfaces xe-5/0/0 unit * output-traffic-control-profile tcp
set class-of-service forwarding-classes queue 0 be
set class-of-service forwarding-classes queue 1 ef
set class-of-service forwarding-classes queue 2 af
set class-of-service forwarding-classes queue 3 nc
set class-of-service schedulers be_sch priority low
set class-of-service schedulers ef_sch priority low
set class-of-service schedulers af_sch priority strict-high
set class-of-service schedulers nc_sch priority low
set class-of-service classifiers ieee_jitter forwarding-class be loss-priority low code-points 000
set class-of-service classifiers ieee_jitter forwarding-class ef loss-priority low code-points 001
set class-of-service classifiers ieee_jitter forwarding-class af loss-priority low code-points 010
set class-of-service classifiers ieee_jitter forwarding-class nc loss-priority low code-points 011
set class-of-service scheduler-maps smap_jitter forwarding-class be scheduler be_sch
set class-of-service scheduler-maps smap_jitter forwarding-class ef scheduler ef_sch
set class-of-service scheduler-maps smap_jitter forwarding-class af scheduler af_sch
set class-of-service scheduler-maps smap_jitter forwarding-class nc scheduler nc_sch
set class-of-service traffic-control-profiles tcp scheduler-map smap_jitter
set class-of-service traffic-control-profiles tcp shaping-rate 6g
Baseline Configuration
Configure hierarchical scheduling at xe-5.0.0.
1. To configure the VLAN 1 input and output at xe-2/0/0.0 and xe-5/0/0.0:
[edit]
user@host# set interfaces xe-2/0/0 per-unit-scheduler
user@host# set interfaces xe-2/0/0 flexible-vlan-tagging
user@host# set interfaces xe-2/0/0 unit 0 vlan-id 1
user@host# set interfaces xe-2/0/0 unit 0 family inet address 10.1.1.1/24
user@host# set interfaces xe-5/0/0 per-unit-scheduler

user@host# set interfaces xe-5/0/0 flexible-vlan-tagging
63
user@host# set interfaces xe-5/0/0 unit 0 vlan-id 1

user@host# set interfaces xe-5/0/0 unit 0 family inet address 10.2.1.1/24
2. Map each of four queues to a forwarding class.
[edit]
user@host# set class-of-service forwarding-classes queue 0 be
user@host# set class-of-service forwarding-classes queue 1 ef
user@host# set class-of-service forwarding-classes queue 2 af
user@host# set class-of-service forwarding-classes queue 3 nc
3. Assign a packet-scheduling priority value to each forwarding class.
[edit]
user@host# set class-of-service schedulers be_sch priority low
user@host# set class-of-service schedulers ef_sch priority low
user@host# set class-of-service schedulers af_sch priority strict-high
user@host# set class-of-service schedulers ef_sch priority low
4. Customize the default IEEE 802.1p classifier (BA classifier based on Layer 2 header) by defining different
values for iEEE 802.1p code points.
[edit]
user@host# set class-of-service classifiers ieee_jitter forwarding-class be loss-priority low code-points 000
user@host# set class-of-service classifiers ieee_jitter forwarding-class ef loss-priority low code-points 001
user@host# set class-of-service classifiers ieee_jitter forwarding-class af loss-priority low code-points 010
user@host# set class-of-service classifiers ieee_jitter forwarding-class nc loss-priority low code-points 011
5. Apply the BA classifier to the input of the logical units on xe-2/0/0.
[edit]
user@host# set interfaces xe-2/0/0 unit * classifiers ieee-802.1 ieee_jitter
6. Configure the scheduler map smap_jitter to map the forwarding classes to the schedulers.
[edit]
user@host# set class-of-service scheduler-maps smap_jitter forwarding-class be scheduler be_sch
user@host# set class-of-service scheduler-maps smap_jitter forwarding-class ef scheduler ef_sch
64
user@host# set class-of-service scheduler-maps smap_jitter forwarding-class af scheduler af_sch

user@host# set class-of-service scheduler-maps smap_jitter forwarding-class nc scheduler nc_sch
7. Configure the traffic control profile tcp to combine the scheduler map smap_jitter (that maps the
forwarding classes to the schedulers for port-based scheduling) with a shaping rate (for hierarchical
scheduling).
[edit]
user@host# set class-of-service traffic-control-profiles tcp scheduler-map smap_jitter
user@host# set class-of-service traffic-control-profiles tcp shaping-rate 6g
8. Apply the traffic control profile to the router output at xe-5/0/0.
[edit]
user@host# set class-of-service-interfaces xe-5/0/0 unit * output-traffic-control-profile tcp
[edit]
user@host# commit
Results
Confirm your configuration by entering show interfaces and show cloass-of-service commands from
configuration mode. If the output does not display the intended configuration, repeat the instructions in
this example to correct the configuration.
[edit]
user@host# show interfaces
xe-2/0/0 {
per-unit-scheduler;
flexible-vlan-tagging;
unit 0 {
vlan-id 1;
family inet {
address 10.1.1.1/24;
}
}
}
65
xe-5/0/0 {
per-unit-scheduler;
unit 0 {
vlan-id 1;
family inet {
address 10.2.1.1/24;
}
}
}
[edit]
user@host# show class-of-service
classifiers {
ieee-802.1 ieee_jitter {
}
}
}
forwarding-class nc {
}
}
}
forwarding-classes {
queue 0 be;
queue 1 ef;
queue 2 af;
queue 3 nc;
}
traffic-control-profiles {
tcp {
scheduler-map smap_jitter;
shaping-rate 6g;
}
}
interfaces {
xe-2/0/0 {
unit * {
66
classifiers {
ieee-802.1 ieee_jitter;
}
}
}
xe-5/0/0 {
unit * {
output-traffic-control-profile tcp;
}
}
}
scheduler-maps {
smap_jitter {
}
}
schedulers {
be_sch {
priority low;
}
ef_sch {
priority low;
}
af_sch {
priority strict-high;
}
nc_sch {
priority low;
}
}
Verification
IN THIS SECTION
Measuring End-to-End Jitter to Establish the Baseline | 67
Configuring Jitter Reduction | 67
Measuring End-to-End Jitter to Verify Jitter Reduction | 67

67
Confirm that the configuration is working properly
Measuring End-to-End Jitter to Establish the Baseline
Purpose
Establish a baseline measurement by noting the amount of jitter that occurs when the hierarchical queuing
line card hosting the egress port is configured with the default maximum number of queues.
Action
To measure jitter:
1. Pass traffic through the VLAN.
2. Measure the variation in packet delay for selected packets in the data flow.
Configuring Jitter Reduction
Purpose
Reduce jitter in the VLAN port output queues.
Action
1. Configure a reduced maximum number of queues for egress ports on the hierarchical queuing MPC in
slot 5, thereby reducing the jitter in the port queues.
[edit]
user@host# set chassis fpc 5 max-queue 64k
[edit]
user@host# commit
Measuring End-to-End Jitter to Verify Jitter Reduction
Purpose
Measure the amount of jitter that occurs when the hierarchical queuing line card hosting the egress port
is configured with a reduced maximum number of queues.
Action
To measure jitter:
1. Pass traffic through the VLAN.

68
2. Measure the variation in packet delay for selected packets in the data flow.

max-queues | 430
Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview
On MX Series routers, you can apply hierarchical schedulers on aggregated ethernet bundles using interface
sets. This feature enables you to configure a group of virtual LANs (VLANs) and control their bandwidth.
This feature is supported at egress only.
You can configure interface sets for aggregated Ethernet (AE) interfaces created under static configurations.
You can configure class-of-service parameters on AE interfaces, in either link-protect or non-link-protect
mode. You can configure these parameters at the AE physical interface level. The CoS configuration is
fully replicated for all AE member links in link-protect mode. You can control the way these parameters
are applied to member links in non-link-protect mode by configuring the AE interface to operate in scaled
mode or replicate mode.
The link membership list and scheduler mode of the interface set is inherited from the underlying aggregated
Ethernet interface over which the interface set is configured. When an aggregated Ethernet interface
operates in link protection mode, or if scheduler mode is configured to replicate member links, the scheduling
parameters of the interface set are copied to each of the member links.
If the scheduler mode of the aggregated Ethernet interface is set to scale member links, the scheduling
parameters are scaled based on the number of active member links (scaling factor is 1/A where A is the
number of active links in the bundle) and applied to each of the AE interface member links.
To configure an interface set, include the interface-set statement at the [edit class-of-service interfaces]
hierarchy level.
To apply scheduling and queuing parameters to the interface set, include the output-traffic-control-profile
profile-name statement at the [edit class-of-service interfaces interface-name interface-set
interface-set-name] hierarchy level.
To apply an output traffic scheduling and shaping profile for the remaining traffic to the logical interface
or interface set, include the output-traffic-control-profile-remaining profile-name statement at the [edit
class-of-service interfaces interface-name] hierarchy level or the [edit class-of-service interfaces
interface-name interface-set interface-set-name] hierarchy level.
69

Controlling Remaining Traffic
Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces
The following example shows the creation of an interface set for aggregated Ethernet interfaces in a static
Ethernet configuration.
To configure interface sets for aggregated Ethernet (AE) interfaces created under static configurations:
1. Create the AE interfaces.
[edit]
user@host# show chassis | display set
set chassis aggregated-devices ethernet device-count 10
2. Configure the AE physical interfaces and member links.
user@host# show interfaces | display set
set interfaces ge-5/2/0 gigether-options 802.3ad ae0

set interfaces ge-5/2/1 gigether-options 802.3ad ae0
set interfaces ae0 hierarchical-scheduler maximum-hierarchy-levels 2
set interfaces ae0 flexible-vlan-tagging
set interfaces ae0 unit 0 vlan-id 100
3. Configure the interface set.
set interfaces interface-set ifset1-ae0 interface ae0 unit 0

set interfaces interface-set ifset1-ae0 interface ae0 unit 1
4. Configure class-of-service parameters for the interface sets.

70
set class-of-service interfaces interface-set ifset1-ae0 output-traffic-control-profile tcp
NOTE: You also need to configure the parameters of the traffic control profile. For more
information, see the Related Documentation section on this page.
5. Configure scheduler mode.
set class-of-service interfaces ae0 member-link-scheduler scale

Example: Configuring Shared Resources on Ethernet IQ2 Interfaces
Example: Configuring Scheduling Modes on Aggregated Interfaces
You can configure class-of-service parameters, such as queuing or shaping parameters on aggregated
interfaces, in either link-protect or non-link-protect mode. You can configure these parameters for per-unit
schedulers, hierarchical schedulers, or shaping at the physical and logical interface level. You can control
the way these parameters are applied by configuring the aggregated interface to operate in scale or
replicate mode.
You can apply these parameters on the following routers:
• MX Series router interfaces on EQ DPCs
• MX Series router interfaces on MICs or MPCs through Junos OS Release 10.2 (non-link-protect mode
only)
• M120 or M320 routers
• T Series router interfaces on IQ2 PICs
• PTX Series Packet Transport Routers

71
You can configure the applied parameters for aggregated interfaces operating in non-link-protected mode.
In link-protected mode, only one link in the bundle is active at a time (the other link is a backup link) so
schedulers cannot be scaled or replicated. In non-link-protected mode, all the links in the bundle are active
and send traffic; however, there is no backup link. If a link fails or is added to the bundle in
non-link-protected mode, the links’ traffic is redistributed among the active links.
To set the scheduling mode for aggregated interfaces, include the scale or replicate option of the
member-link-scheduler statement at the [edit class-of-service interfaces aen] hierarchy level, where n is
the configured number of the interface:
[edit class-of-service interfaces aen]

member-link-scheduler (replicate | scale);
By default, if you do not include the member-link-scheduler statement, scheduler parameters are applied
to the member links in the scale mode (also called “equal division mode”).
The aggregated Ethernet interfaces are otherwise configured as usual. For more information on configuring
aggregated Ethernet interfaces, see the Junos OS Network Interfaces Library for Routing Devices.
The following examples set scale mode on the ae0 interface and replicate mode on the ae1 interface.
[edit class-of-service]
interfaces ae0 {
member-link-scheduler scale;
}
interfaces ae1 {
member-link-scheduler replicate;
}
NOTE: The member-link-scheduler statement only appears for aggregated interfaces. You
configure this statement for aggregated interfaces in non-link-protected mode. For more
information about link protection modes, see the Network Interfaces Configuration Guide.
Aggregated interfaces support both hierarchical and per-unit schedulers.
NOTE: The traffic-control-profiles statement is not supported for PTX Series Packet Transport
Routers.
72
When interface parameters are using the scale option of the member-link-scheduler statement, the
following parameters under the [edit class-of-service traffic-control-profiles traffic-control-profile-name]
configuration are scaled on egress when hierarchical schedulers are configured:
• shaping-rate (PIR)
• guaranteed-rate (CIR)
• delay–buffer-rate
When interface parameters are using the scale option of the member-link-scheduler statement, the
following parameters under the [edit class-of-service schedulers scheduler-name] configuration are scaled
on egress when per-unit schedulers are configured:
• transmit-rate
• buffer-size
NOTE: You cannot apply a hierarchical scheduler at the interface set level for an ae interface.
(Interface sets cannot be configured under an ae interface.)
The following configuration parameters are not supported on ae interfaces in non-link-protection mode:
• Input scheduler maps
• Input traffic control profiles
• Input shaping rates
The following configuration conventions are also not supported:
• Scaling of the input-traffic-control-profile-remaining statement.
• The scheduler-map-chassis statement and the derived option for the ae interface. Chassis scheduler
maps should be applied under the physical interfaces.
• Dynamic and demux interfaces are not supported as part of the ae bundle.
Depending on the whether the scale or replicate option is configured, the member-link-scheduler statement
operates in either scaled mode (also called “equal division mode”) or replicated mode, respectively.
In scaled mode, a VLAN can have multiple flows that can be sent over multiple member links of the ae
interface. Likewise, a member link can receive traffic from any VLAN in the ae bundle. In scaled mode, the
physical interface bandwidth is divided equally among all member links of the ae bundle.
In scaled mode, the following scheduler parameter values are divided equally among the member links:
• When the parameters are configured using traffic control profiles, then the parameters scaled are the
shaping rate, guaranteed rate, and delay buffer rate.
73
• When the parameters are configured using scheduler maps, then the parameters scaled are the transmit
rate and buffer size. Shaping rate is also scaled if you configure it in bits per second (bps). Shaping rate
is not scaled if you configure it as a percentage of the available interface bandwidth.
For example, consider an ae bundle between routers R1 and R2 consisting of three links. These are ge-0/0/1,
ge-0/0/2 and ge-0/0/3 (ae0) on R1; and ge-1/0/0, ge-1/0/1, and ge-1/0/2 (ae2) on R2. Two logical
interfaces (units) are also configured on the ae0 bundle on R1: ae0.0 and ae0.1.
On ae0, traffic control profiles on R1 are configured as follows:
• ae0 (the physical interface level) has a PIR of 450 Mbps.
• ae0.0 (VLAN 100 at the logical interface level) has a PIR of 150 Mbps and a CIR of 90 Mbps.
• ae0.1 (VLAN 200 at the logical interface level) has a PIR of 90 Mbps and a CIR of 60 Mbps.
In scaled mode, the ae0 PIR is first divided among the member physical interfaces. Because there are three
members, each receives 450 / 3 = 150 Mbps as a derived value. So the scaled PIR for the members interfaces
is 150 Mbps each.
However, there are also two logical interfaces (ae0.0 and ae0.1) and VLANs (100 and 200) on ae0. Traffic
can leave on any of the three physical interfaces (ge-0/0/1, ge-0/0/2, or ge-0/0/3) in the bundle. Therefore,
two derived logical interfaces are added to the member links to represent the two VLANs.
There are now six logical interfaces on the physical interfaces of the links making up the ae bundle, one
set for VLAN 100 and the other for VLAN 200:
• ge-0/0/1.0 and ge-0/0/1.1
• ge-0/0/2.0 and ge-0/0/2.1
• ge-0/0/3.0 and ge-0/0/3.1
The traffic control profile parameters configured on ae0.0 are divided across all the underlying logical
interfaces (the unit 0s). In the same way, the traffic control profile parameters configured on ae0.1 are
divided across all the underlying logical interfaces (the unit 1s).
Therefore, the derived values of the scaled parameters on the interfaces are:
• For ge-0/0/1.0 and ge-0/0/2.0 and ge-0/0/3.0, each CIR = 90 / 3 = 30 Mbps, and each PIR = 150 / 3
= 50 Mbps.
• For ge-0/0/1.1 and ge-0/0/2.1 and ge-0/0/3.1, each CIR = 60 / 3 = 20 Mbps, and each PIR = 90 / 3 =
30 Mbps.
The scaled values are shown in Figure 6 on page 74.

74
Figure 6: Scaled Mode for Aggregated Ethernet Interfaces
PIR = 50m PIR = 30m PIR = 50m PIR = 30m PIR = 50m PIR = 30m
CIR = 30m CIR = 20m CIR = 30m CIR = 20m CIR = 30m CIR = 20m
ge-0/0/1.0 ge-0/0/1.1 ge-0/0/2.0 ge-0/0/2.1 ge-0/0/3.0 ge-0/0/3.1
ge-0/0/1 PIR = 150m ge-0/0/2 PIR = 150m ge-0/0/3 PIR = 150m
g017366
ae0 PIR = 450m
In scaled mode, when a new member link is added to the bundle, or an existing member link is either
removed or fails, then the scaling factor (based on the number of active links) is recomputed and the new
scheduler or traffic control profile parameters are reassigned. Only the PIR, CIR, and buffer parameters
are recomputed: all other parameters are simply copied at each level.
NOTE: In show class-of-service scheduler-map commands, values derived in scaled mode instead
of explicitly configured are flagged with &**sf**n suffix, where n indicates the value of the scaling
factor.
The following sample shows the output for the scheduler map named smap-all-abs with and without a
scaling factor:
user@host> show class-of-service scheduler-map
Scheduler map: smap-all-abs, Index: 65452
Scheduler: q0_sch_abs, Forwarding class: be, Index: 6775

Transmit rate: 40000000 bps, Rate Limit: none, Buffer size: remainder,
Priority: low
Excess Priority: unspecified
Drop profiles:
Loss priority Protocol Index Name
Low any 1 <default-drop-profile>
Medium low any 1 <default-drop-profile>
Medium high any 1 <default-drop-profile>
High any 1 <default-drop-profile>

75
Scheduler map: smap-all-abs, Index: 65452
Scheduler: q0_sch_abs&**sf**3, Forwarding class: be, Index: 2128

Transmit rate: 13333333 bps, Rate Limit: none, Buffer size: remainder,
Priority: low
Drop profiles:
Low any 1 <default-drop-profile>
Medium low any 1 <default-drop-profile>
Medium high any 1 <default-drop-profile>
High any 1 <default—drop—profile>
NOTE: There can be multiple scheduler maps created with different scaling factors, depending
on when the child interfaces come up. For example, if there are only two active children on a
parent interface, a new scheduler map with a scaling factor of 2 is created. The scheduler map
name is smap-all-abs&**sf**2.
In replicated mode, in contrast to scaled mode, the configured scheduler parameters are simply replicated,
not divided, among all member links of the ae bundle.
In replicated mode, the following scheduler parameter values are replicated among the member links and
logical interfaces:
• When the parameters are configured using traffic control profiles, then the parameters replicated are
the shaping rate, guaranteed rate, and delay buffer rate.
• When the parameters are configured using scheduler maps, then the parameters replicated are the
transmit rate and buffer size.
If the scheduler parameters in the example configuration between routers R1 and R2 are applied with the
member-link-scheduler replicate statement and option, the following parameters are applied:
• The ae0 PIR is copied among the member physical interfaces. Each receives 450 Mbps as a PIR.
• For each logical interface unit .0, the configured PIR and CIR for ae0.0 is replicated (copied). Each logical
interface unit .0 receives a PIR of 150 Mbps and a CIR of 90 Mbps.
• For each logical interface unit .1, the configured PIR and CIR for ae0.1 is replicated (copied). Each logical
interface unit .1 receives a PIR of 90 Mbps and a CIR of 60 Mbps.
The replicated values are shown in Figure 7 on page 76.

76
Figure 7: Replicated Mode for Aggregated Ethernet Interfaces
PIR = 150m PIR = 90m PIR = 150m PIR = 90m PIR = 150m PIR = 90m
CIR = 90m CIR = 60m CIR = 90m CIR = 60m CIR = 90m CIR = 60m
ge-0/0/1.0 ge-0/0/1.1 ge-0/0/2.0 ge-0/0/2.1 ge-0/0/3.0 ge-0/0/3.1
ge-0/0/1 PIR = 450m ge-0/0/2 PIR = 450m ge-0/0/3 PIR = 450m
g017367
ae0 PIR = 450m
In replicated mode, when a new member link is added to the bundle, or an existing member link is either
removed or fails, the values are either copied or deleted from the required levels.
How Schedulers Define Output Queue Properties

Default Schedulers Overview
Configuring Schedulers
Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the

Queuing Chip
Queuing MPCs contain a queuing chip that enables rich-queuing features such as hierarchical and per-vlan
queuing. By default, all traffic passing through an interface on one of these MPCs also passes through the
queuing chip, which decreases the available bandwidth of the interface. If you do not require hierarchical
or per-vlan queuing on a particular interface of a queuing MPC, you can bypass the queuing chip to increase
the available bandwidth.
Starting with Junos OS 18.2R1, you can enable this option on vMX routers to save a vCPU when scheduling
is not needed on an interface.
To bypass the queuing chip on a queuing MPC, you must be running Junos OS Release 14.2 or later. On
vMX routers, you must be running Junos OS Release 18.2 or later. You can bypass the queuing chip on
the following line cards:
• MPC1 Q
• MPC1E Q
• MPC2 Q
77
• MPC2 EQ
• MPC2E Q
• MPC2E EQ
• MPC5E Q (2x100GE + 4x10GE MPC5EQ or 6x40GE + 24x10GE MPC5EQ)
To bypass the queuing chip on an interface on a queuing MPC:
1. Ensure that neither per-unit-scheduler nor hierarchical-scheduler is configured on the interface.
NOTE: It is not possible to bypass the queuing chip on an interface if per-unit or hierarchical
scheduling is configured on that interface.
2. Enable bypass-queuing-chip on the interface.
For example:
[edit interfaces]
user@router# set interface- name bypass-queuing-chip
3. Commit your changes.
[edit interfaces]
user@router# show
interface-name {
bypass-queueing-chip;
}
4. Verify your changes.
user@router> show interfaces interface-name

Physical interface: interface-name, Enabled, Physical link is Up
Interface index: 147, SNMP ifIndex: 524
Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 1000mbps,
BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering:
Disabled,
Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online
Pad to minimum frame size: Disabled
78
Interface flags: SNMP-Traps Internal: 0x4000

Link flags : None
CoS queues : 8 supported, 4 maximum usable queues
Schedulers : 0, Queuing Chip Bypassed
Current address: 00:21:59:0f:35:31, Hardware address: 00:21:59:0f:35:31
Last flapped : 2014-04-29 14:10:18 PDT (02:27:46 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
Active alarms : None
Active defects : None
Interface transmit statistics: Disabled
Release Description
18.2R1 Starting with Junos OS 18.2R1, you can enable this option on vMX routers to save a vCPU
when scheduling is not needed on an interface.
14.2 To bypass the queuing chip on a queuing MPC, you must be running Junos OS Release 14.2
or later. On vMX routers, you must be running Junos OS Release 18.2 or later.
bypass-queuing-chip
2 PART
Hierarchical CoS for Subscriber

Management
Hierarchical Class of Service for Subscriber Management | 80
Applying CoS to Groups of Subscriber Interfaces | 110
Configuring Hierarchical Scheduling for MPLS Pseudowire Interfaces | 137
Configuring Hierarchical Scheduling for L2TP | 153
Preventing Bandwidth Contention on Subscriber Interfaces | 163
Configuring Targeted Distribution of Subscribers on Aggregated Ethernet

Interfaces | 188
Applying CoS Using Parameters Received from RADIUS | 212

80
CHAPTER 3
Hierarchical Class of Service for Subscriber

Management
IN THIS CHAPTER
Example: Maintaining a Constant Traffic Flow by Configuring a Static VLAN Interface with a Dynamic Profile
for Subscriber Access | 95
Hierarchical Class of Service for Subscriber Management Overview
The hierarchical class-of-service (HCoS) architecture as supported on fine-grained queuing MPCs is a

powerful feature designed to provide a flexible and scalable CoS solution in broadband network gateway
(BNG) subscriber access applications where triple-play or business class offerings are enabled through IP
CoS.
Hierarchical CoS enables you to apply traffic scheduling and queuing parameters (which can include a
delay-buffer bandwidth) and packet transmission scheduling parameters (which can include buffer
management parameters) to an individual subscriber interface rather than to all interfaces configured on
the port. HCoS enables you to dynamically modify queues when subscribers require services.
The logical interface set construct in a five-level scheduler hierarchy is the key feature that enables HCoS.
The interface set feature allows you to group subscribers into aggregate classes with specific guaranteed
and peak rates that map to service classes. Service classes ultimately map to how much you can charge
for the differentiated service levels.
HCoS can be applied dynamically through the use of dynamic traffic profiles and RADIUS vendor-specific
attributes (VSAs).
81
Dynamic traffic profiles are used to dynamically apply CoS to individual subscribers or groups of subscribers.
This enables you, as a service provider, to deploy a BRAS solution without having to manually provision
each customer. In a dynamic traffic profile, variables are used to represent the values for things like shaping
rate and drop priority.
Dynamic traffic profiles are used in conjunction with dynamic profiles. Dynamic profiles allow you to
dynamically provision IP service definitions by creating a template configuration and having the specific
variable values assigned in real time when the subscriber authenticates to the network.
NOTE: For a complete list of the Junos OS system variables, see: Junos OS Predefined Variables.
To learn more about how to use HCoS in conjunction with dynamic traffic control profiles for subscriber
management, read the Day One: Dynamic Subscriber Management book. Note that you will need to have
a login and password to access this document.
In addition, the following topics are very helpful:
• Hierarchical Class of Service Overview on page 2
• Subscriber Access Network Overview
• CoS for Subscriber Access Overview
• Subscriber Management Overview
• Class of Service and Subscriber Management Overview
Before applying dynamic HCoS on your network, you should learn about HCoS, define your needs, plan
how you want to implement HCoS, and test the operation in a simulated environment.

Understanding Hierarchical CoS for Subscriber Interfaces
Hierarchical CoS enables you to apply traffic scheduling and queuing parameters and packet transmission
scheduling parameters to an individual subscriber interface rather than to all interfaces configured on a
port. Hierarchical CoS enables you to dynamically modify queues when subscribers require services.
82
Hierarchical CoS is supported on MX Series routers with either Enhanced Queuing DPCs or queuing
MPCs/MICs installed. Beginning with Junos OS Release 16.1, five levels of hierarchy are supported on
MPC5E 3D Q line cards.
Interfaces support up to a five-level CoS scheduling hierarchy that, when fully configured, generally consists
of the physical interface (level 1), an interface set or underlying interface (level 2), one or more underlying
logical interfaces (level 3), one or more session or customer VLANs (level 4), and one or more queues (level
5). Although all CoS scheduling hierarchies are five-level, level 1 is always the physical interface and level
5 is always the queue. Hierarchical scheduling configurations consist of the type of interfaces you
configure—for example, a logical interface or an interface set—and where those interfaces reside in the
scheduling hierarchy—level 2, level 3, or level 4. Because many hierarchical scheduling configurations are
possible, we use the terms two-level hierarchical scheduling, three-level hierarchical scheduling, four-level
hierarchical scheduling in this topic.
NOTE: Starting with Junos OS 18.4R1, you can apply dynamic and static logical interfaces in
the same dynamic interface set on all MPCs that support 4 and 5-level hierarchical CoS. You can
also apply dynamic interface sets in dynamic interface sets.
Starting with Junos OS 19.3R1, you can apply an input traffic control profile (TCP) to a dynamic
logical interface set in 4-level hierarchical scheduling or to two dynamic logical interface sets in
5-level hierarchical scheduling. Thus, Junos CoS enables you to dynamically assign a static input
TCP with shaping-rate to a dynamic interface-set to enforce a customer’s SLA. If no such SLA
enforcement is needed, you can configure a static TCP that is designated as the default input
TCP assigned to any dynamic interface-set that does not already have an explicitly assigned
input TCP.
Two-Level Hierarchical Scheduling
Two-level hierarchical scheduling limits the number of hierarchical levels in the scheduling hierarchy to
two as shown in Figure 5 on page 54. In this configuration, interface sets are not configured and only the
logical interfaces have traffic control profiles (TCPs). Configuring two levels of hierarchy on MPCs that
support more levels preserves resources and allows the system to scale higher.
83
Figure 8: Two-Level Hierarchical Scheduling
Logical interface (unit) Interface set Physical interface
g017446
In a two-level scheduling hierarchy, all logical interfaces and interface sets share a single node; no hierarchical
relationship is formed.
You control two-level hierarchical scheduling by setting the maximum-hierarchy-levels option under the
[edit interfaces interface-name hierarchical-scheduler] hierarchy to 2:
• If the maximum-hierarchy-levels option is not set, then interface sets can be at either level 2 or level 3,
depending on whether the member logical interfaces within the interface set have a traffic control profile.
• If any member logical interface has a traffic-control profile, then the interface set is always a level 2 CoS
scheduler node.
• If no member logical interface has a traffic-control profile, the interface set is always a level 3 CoS
scheduler node.
• If the maximum-hierarchy-levels option is set, then the interface set can only be at level 3; it cannot be
at level 2. In this case, if you configure a level 2 interface set, you generate Packet Forwarding Engine
errors.
Table 11 on page 83 summarizes the interface hierarchy and the CoS scheduler node levels for two-level
hierarchical scheduling.
Table 11: Two-Level Hierarchical Scheduling—Interface Hierarchy Versus Scheduling Nodes
Level 1 Level 2 Level 3
Physical interface Logical interface One or more queues
Physical interface Interface set One or more queues
Physical interface Logical interface One or more queues
To configure two-level hierarchical scheduling, include the hierarchical-scheduler statement at the [edit
interfaces interface-name] hierarchy level and set the maximum-hierarchy-levels option to 2.
84
[edit interfaces]
interface-name {
}
}
CAUTION: MPC3E, 32x10GE MPC4E, and 2x100GE + 8x10GE MPC4E MPCs support
only two levels of scheduling hierarchy. When enabling hierarchical scheduling on
these cards, you must explicitly set maximum-hierarchy-levels to 2.
Three-Level Hierarchical Scheduling
Three-level hierarchical scheduling is supported only on MX Series routers running MPC/MIC interfaces.
Three-level hierarchical scheduling supports up to eight CoS queues. You can configure many different
three-level scheduling hierarchies, depending on the location of the interface set or the use of underlying
interfaces. In all variations, the physical interface is a level 1 CoS scheduler node and the queues reside at
the highest level. Configuring three levels of hierarchy on MPCs that support more levels preserves
resources and allows the system to scale higher.
NOTE: Three-level hierarchical scheduling is supported only on subscriber interfaces and interface
sets running over aggregated Ethernet interfaces on MPC/MIC interfaces in MX Series routers.
When you use three-level hierarchical scheduling, interface sets can reside at either level 3 or level 4. You
can also configure an underlying logical interface at level 3 and a logical interface at level 4.
Table 12 on page 84 summarizes the most common cases of the interface hierarchy and the CoS scheduler
node levels for three-level hierarchical scheduling.
Table 12: Three-Level Hierarchical Scheduling—Interface Hierarchy Versus CoS Scheduling Node Levels
Level 1 Level 2 Level 3 Level 4
Physical interface Interface set Logical interface One or more queues
Physical interface Logical interface Interface set One or more queues
Physical interface Underlying logical interface Logical interface One or more queues
85
In three-level hierarchical scheduling, the CoS scheduler nodes at level 1, level 2, and level 3 form a
hierarchical relationship.
With a three-level hierarchical scheduling, logical interfaces can reside at level 2, or they can reside at level
3 if the logical interface at level 2 is an underlying logical interface. This is shown in Figure 9 on page 85.
Figure 9: Three-Level Hierarchical Scheduling—Logical Interfaces at Level 3 with Underlying Logical

Interfaces at Level 2
Logical interface Underlying logical interface Physical interface

(unit) (unit)
g041450
Level 3
Another possible configuration for three-level hierarchical scheduling is shown in Figure 10 on page 85.
In this configuration, the logical interfaces are located at level 2 and the interface sets are located at level
3.
Figure 10: Three-Level Hierarchical Scheduling—Logical Interfaces at Level 2 with Interface Sets at Level
3
Interface set (unit) Logical interface (unit) Physical interface

g041449
Level 3
To configure three-level hierarchical scheduling, include the implicit-hierarchy option at the [edit interfaces
interface-name hierarchical-scheduler] hierarchy level and optionally set the maximum-hierarchy-levels
option to 3. (The default value for maximum-hierarchy-levels is 3.)
[edit interfaces]
86
interface-name {
implicit-hierarchy;
}
}
Interface Hierarchy Versus CoS Hierarchy

An interface hierarchy and a CoS scheduling hierarchy are distinctly different. Interface hierarchy refers
to the relationship between the various interfaces—for example, the relationship between logical interfaces
and an interface set, the relationship between a logical interface and an underlying logical interface, or the
relationship between the physical interface and the logical interface. CoS scheduling hierarchy refers to
the hierarchical relationship between the CoS scheduler nodes. In two-level hierarchical scheduling, no
hierarchy is formed between the CoS scheduler nodes—the logical interface and interface set share a single
level 2 scheduler node. However, when you use the implicit-hierarchy option for three-level hierarchical
scheduling, the CoS scheduler nodes form a scheduling hierarchy.
Figure 11 on page 86 and Figure 12 on page 87 provide two scenarios for this discussion.
Figure 11 on page 86 shows an interface hierarchy where a Gigabit Ethernet interface (ge-1/0/0) is the
physical interface. Two logical interfaces (ge-1/0/0.100 and ge-1/0/0.101) are configured on the physical
interface:
• Logical interface ge-1/0/0.100 is a member of a PPPoE interface set and a Demux interface set.
• Logical interface ge-1/0/0.101 is a member of a demux interface set.
Figure 11: Logical Interfaces at Level 2 and Interface Sets at Level 3
PPPoE PPPoE DHCP

subscriber queues subscriber queues subscriber queues
L4
TCP TCP
Pppoe- Demux- Ppp-Demux-
Logical Interface Logical Interface Logical Interface Set Logical Interface Set
L3
Sets Set (home) (demux-and pppoe)
L2 Logical Interfaces TCP GE-1/0/0.100 GE-1/0/0.101 TCP
Physical Interface
g041435
L1 GE-1/0/0
of Logical Tunnel
87
Each interface set has a dedicated queue. The CoS scheduler nodes at level 1 (physical interface), level 2
(underlying logical interfaces), and level 3 (interface sets) form a scheduling hierarchy.
To configure this scenario, you must include the implicit-hierarchy option under the hierarchical-scheduler
statement on physical interface ge-1/0/0 and configure and apply traffic-control profiles on each interface
set and underlying logical interface.
Figure 12 on page 87 shows an interface hierarchy where Gigabit Ethernet interface ge-1/0/0 is the
physical interface. Three logical interfaces are configured:
• Two logical interfaces (Pp0.100 and Demux0.100) reside on the underlying logical interface ge-1/0/0.100.
• A third logical interface (Pp0.101) resides on the underlying logical interface ge-1/0/0.101.
Figure 12: Logical Interfaces at Level 3 and Underlying Logical Interfaces at Level 2
PPPoE Demux DHCP

subscriber queues subscriber queues subscriber queues
L4
Demux0
L3 Logical Interfaces Pp0.100 TCP TCP Pp0.101
100
Underlying logical
L2 TCP GE-1/0/0.100 GE-1/0/0.101 TCP
interfaces
Physical Interface g041436

L1 GE-1/0/0
of Logical Tunnel
Each logical interface has a dedicated queue. The CoS scheduler nodes at level 1 (physical interface), level
2 (underlying logical interfaces), and level 3 (logical interfaces) form a scheduling hierarchy.
To configure this scenario, you must include the implicit-hierarchy option under the hierarchical-scheduler
statement on physical interface GE-1/0/0 and configure and apply traffic-control profiles on each logical
interface and underlying logical interface.
You can configure many different three-level scheduling hierarchies; Figure 11 on page 86 and
Figure 12 on page 87 present just two possible scenarios. Table 12 on page 84 summarizes the possible
interface locations and CoS scheduler nodes.
Four-Level Hierarchical Scheduling
Beginning with Junos OS Release 16.1, four-level hierarchical scheduling is supported on MX Series routers
running NG-MPC2E, NG-MPC3E, MPC5, and MPC7 line cards. Four-level hierarchical scheduling supports
88
up to eight class of service queues. In four-level scheduling hierarchies, the physical interface is a level 1
CoS scheduler node and the queues reside at level 5.
NOTE: Four-level hierarchical scheduling is not supported agent circuit identifier (ACI) or
aggregated Ethernet (AE) interfaces.
When you use four-level hierarchical scheduling, interface sets reside at levels 2 and 3 and logical interfaces
reside at levels 3 and 4. Table 13 on page 88 summarizes the most common case of the interface hierarchy
and the CoS scheduler node levels for four-level hierarchical scheduling. Starting with Junos OS 18.4R1,
you can apply dynamic and static logical interfaces in the same dynamic interface set on all MPCs that
support 4 and 5-level hierarchical CoS. You can also apply dynamic interface sets in dynamic interface
sets.
Table 13: Four-Level Hierarchical Scheduling—Interface Hierarchy Versus CoS Scheduling Node Levels
Level 1 Level 2 Level 3 Level 4 Level 5
Physical interface Interface set Customer VLAN Session Logical Interface One or more queues
(C-VLAN) (ppp or dhcp)
In four-level hierarchical scheduling, the CoS scheduler nodes at level 1, level 2, level 3, and level 4 form
a hierarchical relationship.
To configure four-level hierarchical scheduling, include the implicit-hierarchy option at the [edit interfaces
interface-name hierarchical-scheduler] hierarchy level and set the maximum-hierarchy-levels option to 4.
[edit interfaces]
interface-name {
implicit-hierarchy;
}
}
89
Release Description
19.3R1 Starting with Junos OS 19.3R1, you can apply an input traffic control profile (TCP) to a dynamic
logical interface set in 4-level hierarchical scheduling or to two dynamic logical interface sets in
5-level hierarchical scheduling. Thus, Junos CoS enables you to dynamically assign a static input TCP
with shaping-rate to a dynamic interface-set to enforce a customer’s SLA. If no such SLA enforcement
is needed, you can configure a static TCP that is designated as the default input TCP assigned to any
dynamic interface-set that does not already have an explicitly assigned input TCP.
18.4R1 Starting with Junos OS 18.4R1, you can apply dynamic and static logical interfaces in the same
dynamic interface set on all MPCs that support 4 and 5-level hierarchical CoS. You can also apply
dynamic interface sets in dynamic interface sets.
16.1 Beginning with Junos OS Release 16.1, four-level hierarchical scheduling is supported on MX Series
routers running NG-MPC2E, NG-MPC3E, MPC5, and MPC7 line cards.

Hardware Requirements for Dynamic Hierarchical CoS
Table 14 on page 90 lists the hardware requirements based on subscriber interface type for hierarchical
scheduling in dynamic CoS configurations.
90
Table 14: Hardware Required for Dynamic Hierarchical CoS Configurations
Dynamic CoS Subscriber Interface EQ DPCs on MX Series MPC Q/MIC Modules on

Configuration Type Routers MX Series Routers
Hierarchical CoS Static and dynamic VLANs Yes Yes
Static and dynamic VLANs Yes Yes

over aggregated Ethernet
Static or dynamic IP demux Yes Yes

interfaces
Static or dynamic IP demux Yes Yes

interfaces over aggregated
Ethernet
Static or dynamic VLAN No Yes

demux interfaces
Static or dynamic VLAN No Yes

demux interfaces over
aggregated Ethernet
Static PPPoE interfaces No Yes
Dynamic PPPoE interfaces No Yes
Static or dynamic PPPoE No Yes

interfaces over aggregated
Ethernet
L2TP LAC tunnel over PPP No Yes
L2TP LNS inline service No Yes

over PPP

Guidelines for Configuring Dynamic CoS for Subscriber Access
91
Configuring Static Hierarchical Scheduling in a Dynamic Profile
You configure static scheduling and queuing in a dynamic profile for subscriber access. To configure CoS
in a dynamic profile for subscriber access using static scheduling and queuing parameters:
1. Configure the static CoS parameters in the [edit class-of-service] hierarchy.
a. Enable the hierarchical scheduler for the interface.
See “Understanding Hierarchical CoS for Subscriber Interfaces” on page 81.
b. Configure the scheduler map and schedulers.
When you configure static scheduling and queuing in a dynamic profile, you reference the scheduler
map in the dynamic profile.
See Configuring Schedulers.
c. Configure the drop profiles.
See Defining Packet Drop Behavior by Configuring RED Drop Profiles.
d. Configure the forwarding classes.
See Configuring a Custom Forwarding Class for Each Queue.
e. Configure the rewrite-rules and classifier definitions.
See Configuring Rewrite Rules and Configuring Behavior Aggregate Classifiers.
See The Junos OS CoS Components Used to Manage Congestion and Control Service Levels for information
about configuring the remaining CoS parameters.
2. Configure a static or dynamic subscriber interface that can be referenced in the dynamic profile.
3. Configure CoS parameters in a dynamic profile.
a. Configure the dynamic profile.
See Configuring a Basic Dynamic Profile.
b. Configure traffic shaping and scheduling parameters in the dynamic profile using a traffic-control
profile. Reference the scheduler map you configured in the static [edit class-of-service] hierarchy.
See Configuring Static Traffic Shaping and Scheduling Parameters in a Dynamic Profile.
c. Apply CoS parameters to a subscriber interface by referencing an interface in the dynamic profile.
92
See Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile.
4. To configure default values for subscribers on login, and enable subscribers to replace other CoS
parameters when replacing services, configure variables in the dynamic profile.
See “Configuring Static Default Values for Traffic Scheduling and Shaping” on page 225.

CoS for Subscriber Access Overview
Example: Maintaining a Constant Traffic Flow by Configuring a Static VLAN Interface with a Dynamic
Profile for Subscriber Access | 95
Configuring Hierarchical CoS for a Subscriber Interface of Aggregated

Ethernet Links
You can enable hierarchical CoS on a subscriber interface with an underlying aggregated Ethernet interface.
Before you begin, configure the subscriber interface with aggregated Ethernet.
• To configure a VLAN interface over aggregated Ethernet with link protection, see Configuring a Static or
Dynamic VLAN Subscriber Interface over Aggregated Ethernet and Configuring Link Protection for Aggregated
Ethernet Interfaces.
• To configure a demux subscriber interface:
For static and dynamic IP demux interfaces, see Configuring a Static or Dynamic IP Demux Subscriber
Interface over Aggregated Ethernet.
For static and dynamic VLAN demux interfaces, see Configuring a Static or Dynamic VLAN Demux Subscriber
BEST PRACTICE: Link protection is not required for IP or demux subscriber interfaces. We
recommend that you enable targeted distribution on the demux interface to provide accurate
hierarchical scheduling for these links. See “Providing Accurate Scheduling for a Demux
Subscriber Interface of Aggregated Ethernet Links” on page 191.
93
BEST PRACTICE: While subscribers are active on aggregated Ethernet physical interfaces
with targeted distribution, we recommend that you do not change any attribute of the physical
interfaces, such as MTU. Instead, perform the following steps:
1. Log out all the subscribers.
2. Disable the interface.
3. Make the desired attribute changes.
4. Reenable the interface.
If you do not follow these steps, the commit check for your configuration fails, starting in Junos
OS Release 19.2. In earlier releases, changing the attribute values while subscribers are active
brings down the physical interface and all subscribers using that interface.
To avoid service interruptions, we recommend that you make the changes during a maintenance
window.
To configure hierarchical CoS on the link aggregation (LAG) bundle:
1. Specify that you want to access the LAG bundle.
user@host# edit interfaces aex
2. Configure the link aggregation (LAG) bundle with hierarchical scheduler mode.
[edit interfaces aex]

user@host# set hierarchical-scheduler
You can then attach static or dynamic traffic shaping and scheduling parameters at the aggregated Ethernet
logical interface or its underlying physical interface. See:
• Configuring Traffic Scheduling and Shaping for Subscriber Access
• Configuring Schedulers in a Dynamic Profile for Subscriber Access
• Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile

94
Verifying the Scheduling and Shaping Configuration for Subscriber Access

Configuring Hierarchical CoS on a Static PPPoE Subscriber Interface
You can configure hierarchical CoS on a static PPPoE subscriber interface.
Before you begin:
• Configure the static PPPoE subscriber interface.
See Configuring PPPoE.
To configure hierarchical CoS on a static PPPoE subscriber interface:
1. Specify the PPPoE interface that you want to configure.
user@host# edit interfaces pppoe-interface-name
2. Configure the hierarchical scheduler for the interface.
[edit interfaces interface-name]

3. (Optional) Group the PPPoE interfaces in an interface set.
[edit]
user@host# edit interfaces interface-set interface-set-name
You can now configure static traffic and scheduling parameters for each traffic-control profile, and attach
each traffic-control profile to the PPPoE interface or the PPPoE interface set. For more information, see
Using the CLI to Modify Traffic-Control Profiles That Are Currently Applied to Subscribers.
For hardware requirements and configuration guidelines, see Guidelines for Configuring Dynamic CoS
for Subscriber Access
CoS for PPPoE Subscriber Interfaces Overview
95

Example: Maintaining a Constant Traffic Flow by Configuring a Static VLAN

Interface with a Dynamic Profile for Subscriber Access
IN THIS SECTION
Requirements | 95
Overview | 95
Configuration | 96
Verification | 108
This example shows how to configure a static VLAN interface with a dynamic profile using static schedulers
and CoS parameters for subscriber access to maintain a constant traffic flow. The CoS parameters configure
a best-effort data service for subscribers.
Requirements
Before you begin, be sure that your environment meets the following requirements:
• The interface is hosted on an MX Series router.
• For hierarchical scheduling configurations, hierarchical scheduling is enabled in the static CLI for the
interface referenced in the dynamic profile. If not, the dynamic profile fails.
• Only one traffic-control-profile is configured under a dynamic profile.
• The output-traffic-control-profile that binds the traffic-control profile to the interface is defined within
the same dynamic profile as the interface.
Overview
In a dynamic profile, you can configure VLAN subscriber interfaces over the following statically created
logical interface types:
• GE—Gigabit Ethernet
• XE—10-Gigabit Ethernet
96
• AE—Aggregated Ethernet
Topology
We recommend that you configure each subscriber on a statically created VLAN.
Figure 13 on page 96 shows an example of subscriber interfaces on an individual VLAN.
Figure 13: VLAN Subscriber Interfaces
You can further separate VLANs on subscriber interfaces by configuring a VLAN interface as the underlying
interface for a set of IP demux interfaces.
Configuration
IN THIS SECTION
Configuring a Subscriber Interface with a Static VLAN | 98
Associating the Dynamic Profile with a Statically Created Interface | 99
Configuring the Firewall Filter | 101
Configuring Static Schedulers in a Dynamic Profile | 102
Associating the Scheduler with a Scheduler Map | 105
Configuring and Applying Static Traffic Shaping and Scheduling Parameters in a Dynamic Profile | 106
To configure a static VLAN interface with a dynamic profile for subscriber access, perform these tasks:
To quickly configure this example, copy the following configuration commands into a text file, remove any
line breaks, and then paste the commands into the CLI at the [edit] hierarchy level.
set interfaces ge-2/2/0

97
set interfaces ge-2/2/0 hierarchical-scheduler

set interfaces ge-2/2/0 vlan-tagging
set interfaces ge-2/2/0 vlan-tagging unit 100 vlan-id 100
set interfaces ge-2/2/0 vlan-tagging unit 100 vlan-id 100 family inet
set interfaces ge-2/2/0 vlan-tagging unit 100 vlan-id 100 family inet unnumbered-address lo0.0
preferred-source-address 10.0.0.1
set dynamic-profiles data-service
set dynamic-profiles data-service interfaces $junos-interface-ifd-name
set dynamic-profiles data-service interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit
set dynamic-profiles data-service interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit
family inet
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K term EF
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K term default
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K term EF from forwarding-class
EF
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K term EF then policer
POL_EF_G=768K
set dynamic-profiles data-service firewall family inet filter filter EF_limit_G=768K term default then accept
set dynamic-profiles data-service class-of-service schedulers be-scheduler
set dynamic-profiles data-service class-of-service schedulers be-scheduler buffer-size remainder
set dynamic-profiles data-service class-of-service schedulers be-scheduler drop-profile-map loss-priority any
protocol any
set dynamic-profiles data-service class-of-service schedulers be-scheduler drop-profile-map loss-priority any
protocol any drop-profile drop3
set dynamic-profiles data-service class-of-service schedulers be-scheduler priority low
user@host# set dynamic-profiles data-service class-of-service schedulers be-scheduler transmit-rate percent
40
set dynamic-profiles data-service class-of-service schedulers be-scheduler excess-rate percent 90
set dynamic-profiles data-service class-of-service schedulers be-scheduler excess-priority high
set dynamic-profiles data-service class-of-service scheduler-maps data-service-map
set dynamic-profiles data-service class-of-service scheduler-maps data-service-map forwarding-class best-effort
set dynamic-profiles data-service class-of-service scheduler-maps data-service-map forwarding-class best-effort
scheduler be-scheduler
set dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service
set dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service scheduler-map
data-service-map
set dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service shaping-rate 50k
set dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service guaranteed-rate 10k
set dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service delay-buffer-rate
10k
set dynamic-profiles data-service class-of-service interfaces $junos-interface-ifd-name unit
$junos-underlying-interface-unit output-traffic-control-profile tcp-data-service
98
Configuring a Subscriber Interface with a Static VLAN
After you configure a static VLAN interface, you can reference it in a dynamic profile.
1. Configure the static VLAN interface.
[edit]
user@host# set interfaces ge-2/2/0
2. Enable hierarchical scheduling for the interface.
[edit interfaces ge-2/2/0]

3. Enable VLAN tagging.

user@host# set vlan-tagging
4. Configure the unit and assign a VLAN ID.
[edit interfaces ge-2/2/0 vlan-tagging]

user@host# set unit 100 vlan-id 100
5. Define the family address type (inet for IPv4) for the VLAN interface.
[edit interfaces ge-2/2/0 vlan-tagging unit 100 vlan-id 100]

user@host# set family inet
6. Enable the physical interface to borrow an IP address from the loopback interface by setting an
unnumbered interface address. Configure a secondary IP address on the loopback interface, lo0.0, and
configure it as the preferred source address.
[edit interfaces ge-2/2/0 vlan-tagging unit 100 vlan-id 100 family inet]
user@host# set unnumbered-address lo0.0 preferred-source-address 10.0.0.1
Results
99
Confirm the configuration of the static VLAN interface by entering the show interfaces configuration
command. If the command output does not display the intended configuration, repeat the instructions in
this procedure to correct the configuration.
[edit]
user@host# show interfaces
interfaces {
ge-2/2/0 {
vlan-tagging;
unit 100 {
vlan-id 100;
family inet {
unnumbered-address lo0.0 preferred-source-address 10.0.0.1;
}
}
}
}
Associating the Dynamic Profile with a Statically Created Interface
A dynamic profile is a set of characteristics, defined in a type of template, that you can use to provide
dynamic subscriber access and services for broadband applications. When configuring the interface at the
[dynamic-profiles profile-name interfaces] hierarchy level for a dynamic profile, you use variables to specify
the interface name and the logical unit value. When a DHCP subscriber sends a DHCP request to the
interface, the dynamic profile replaces the interface name variable and logical unit name variable with the
actual interface name and logical unit number of the interface that received the DHCP request.
NOTE: Configuration of the interface name variable and logical interface name variable at the
[edit dynamic-profiles profile-name interfaces] hierarchy level is required for a dynamic profile
to function.
1. Create the new dynamic profile for data services for subscribers.
[edit]
user@host# set dynamic-profiles data-service
2. Define the interface-name variable statement with the internal $junos-interface-ifd-name variable used
by the router to match the interface name of the receiving interface.
100
[edit dynamic-profiles data-service]

user@host# set interfaces $junos-interface-ifd-name
3. Define the unit statement with the internal variable.
• When referencing an existing interface, specify the $junos-underlying-interface-unit variable used

by the router to match the unit value of the receiving interface.
• When creating dynamic interfaces, specify the $junos-interface-unit variable used by the router to
generate a unit value for the interface.
[edit dynamic-profiles data-service interfaces $junos-interface-ifd-name]

user@host# set unit $junos-underlying-interface-unit
or
[edit dynamic-profiles data-service interfaces $junos-interface-ifd-name]

user@host# set unit $junos-interface-unit
4. Define the family address type (inet for IPv4) for the $junos-interface-unit variable.
[edit dynamic-profiles data-service interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit]

user@host# set family inet
Results
Confirm the configuration of the dynamic profile by entering the show dynamic-profiles configuration
[edit]
user@host# show dynamic-profiles
dynamic-profiles {
data-service {
interfaces {
$junos-interface-ifd-name {
unit $junos-underlying-interface-unit {
family inet;
}
}
}
101
}
}
Configuring the Firewall Filter
To configure a static VLAN interface with a dynamic profile for subscriber access, you can configure a
firewall filter to provide enhanced security by blocking packets based on various match criteria, such as
subjecting traffic to a policer for rate limiting, assigning the traffic to a class-of-service (CoS) forwarding
class for later queuing and packet rewrite operations, or directing traffic to a specific routing instance.
1. Configure the family address type (inet for IPv4) for the firewall filter and specify the filter name.
We recommend that you name the filter something that indicates the filter’s purpose. In this example,
we use the bandwidth limit settings.
[edit dynamic-profiles data-service]

user@host# set firewall family inet filter EF_limit_G=768K
2. Specify the term names for the filter. Make each term name unique and represent what its function is.
The first term matches traffic that has been classified into the Expedited Forwarding (EF) class, and the
second term matches all non-EF traffic.
[edit dynamic-profiles data-service firewall family inet filter EF_limit_G=768K]

user@host# set term EF
user@host# set term default
3. In each firewall filter term, specify the conditions used to match components of a packet. Configure
the first term to match all traffic classified as EF class.
[edit dynamic-profiles data-service firewall family inet filter EF_limit_G=768K term EF]
user@host# set from forwarding-class EF
4. Specify the actions to take when the packet matches the condition in the first term. Send the EF traffic
to the policer named POL_EF_G=768K.
[edit dynamic-profiles data-service firewall family inet filter EF_limit_G=768K term EF]
user@host# set then policer POL_EF_G=768K
5. Specify the action to take when the packet matches the condition in the second term. All non-EF packet
traffic is accepted.
102
[edit dynamic-profiles data-service firewall family inet filter EF_limit_G=768K term default]
user@host# set then accept
Results
Confirm the configuration by entering the show dynamic-profiles data-service firewall configuration
[edit]
user@host# show dynamic-profiles data-service firewall
family inet {
filter EF_limit_G=768K {
term EF {
from {
forwarding-class EF;
}
then policer POL_EF_G=768K;
}
term default {
then accept;
}
}
}
Configuring Static Schedulers in a Dynamic Profile
You can configure static scheduling and queuing parameters in a dynamic profile for subscriber access.
Schedulers are part of the basic class-of-service (CoS) infrastructure. You must define at least one scheduler
per forwarding class. Schedulers indicate a forwarding class’s priority, transmit weight, and buffer size, as
well as various shaping and rate control mechanisms.
1. Specify the best-effort scheduler for which you want to configure parameters.
[edit dynamic-profiles data-service class-of-service]

user@host# set schedulers be-scheduler
103
NOTE: Set schedulers to the name of the scheduler to be configured or to the Junos OS
predefined variable ($junos-cos-scheduler) used for dynamic subscriber interfaces. The
predefined variable is replaced with the scheduler name obtained from the RADIUS server
when a subscriber authenticates over the interface to which the dynamic profile is attached.
2. (Optional) Configure the buffer size to use the remaining buffer available.
This parameter allows you to specify an explicit buffer size, either as a percent of interface speed or
as a function of time (specified in microseconds).
[edit dynamic-profiles data-service class-of-service schedulers be-scheduler]

user@host# set buffer-size remainder
3. (Optional) Configure the drop-profile map to associate one or more drop profiles with a queue.
The default random early detection (RED) drop profile is used when no explicit drop profile mapping
is specified. Specify a packet-loss priority (PLP) level of any, and for the specified scheduler to accept
any protocol type.

user@host# set drop-profile-map loss-priority any protocol any
4. (Optional) Configure the drop profile to map a fill level (fullness of a queue) to a drop probability
(probability that a packet is dropped).
[edit dynamic-profiles data-service class-of-service schedulers be-scheduler drop-profile-map loss-priority

any protocol any]
user@host# set drop-profile drop3
You enable RED by applying a drop profile to a scheduler.
5. (Optional) Configure the queue’s scheduler priority to a specific level (low) for guaranteed rate traffic.

user@host# set priority low
6. (Optional) Configure the queue’s transmit weight [in bits per second (bps)] or as a percentage of
transmission capacity.
104

user@host# set transmit-rate percent 40
The transmit rate guarantees the rate for the queue, assuming no priority-based starvation occurs.
When you do not specify a transmit weight, or when the transmit rate is reached, the queue can only
send excess-rate traffic because that queue’s priority is demoted to the excess region. A percentage
of zero (0) drops all packets in the queue.
7. (Optional) Configure the queue’s weight as either a percentage, or a proportion, for any unused
bandwidth traffic to share.

user@host# set excess-rate percent 90
Behavior varies based on interface mode, explicit configuration, and whether any other queues have
explicit weight configured. By default, excess bandwidth between the guaranteed and shaped rate is
shared equally among queues.
8. (Optional) Configure the priority of how excess bandwidth traffic is sent on a scheduler in a dynamic
profile.

user@host# set excess-priority high
To prevent the queue from sending any excess rate traffic, set to none.
Results
Confirm the configuration of the scheduler with static values in the dynamic profile by entering the show
dynamic-profiles data-service class-of-service configuration command. If the command output does not
display the intended configuration, repeat the instructions in this procedure to correct the configuration.
[edit]
user@host# show dynamic-profiles data-service class-of-service
class-of-service {
schedulers {
be-scheduler {
buffer-size remainder;
drop-profile-map loss-priority any protocol any drop-profile drop3;
priority low;
excess-rate percent 90;
105
excess-priority high;
}
}
}
Associating the Scheduler with a Scheduler Map
After you define your schedulers, you must link them to a set of queues on a logical interface using a
scheduler map. Applying a scheduler map to an interface places the related set of schedulers and drop
profiles into effect.
1. Configure the scheduler map name.

user@host# set scheduler-maps data-service-map
2. Configure a forwarding class to associate a scheduler with a scheduler map.
[edit dynamic-profiles data-service class-of-service scheduler-maps data-service-map]

user@host# set forwarding-class best-effort
3. Associate the scheduler you previously defined (be-scheduler) with the scheduler map.
[edit dynamic-profiles data-service class-of-service scheduler-maps data-service-map forwarding-class

best-effort]
user@host# set scheduler be-scheduler
Results
Confirm the configuration of the scheduler map by entering the show dynamic-profiles data-service
class-of-service scheduler-maps configuration command. If the command output does not display the
intended configuration, repeat the instructions in this procedure to correct the configuration.
[edit]
user@host# show dynamic-profiles data-service class-of-service scheduler-maps
scheduler-maps {
data-service-map {
forwarding-class best-effort scheduler be-scheduler;
}
}
106
Configuring and Applying Static Traffic Shaping and Scheduling Parameters in a Dynamic Profile
Configure static traffic shaping and scheduling parameters in a traffic-control profile. A traffic-control
profile is a generic class-of-service (CoS) container that you can apply at all points of a CoS hierarchy to
affect the committed information rate (CIR), peak information rate (PIR), and excess bandwidth handling.
You can specify the traffic-control profile at the port, logical interface, or logical interface-set level. The
traffic-control profile also references the scheduler map.
1. Create the traffic-control profile and assign it a name.

user@host# edit traffic-control-profiles tcp-data-service
2. Apply the static scheduler map, data-service-map, that you previously configured.
[edit dynamic-profiles data-service class-of-service traffic-control-profiles tcp-data-service]

user@host# set scheduler-map data-service-map
3. Configure the shaping rate [in bits per second (bps)] to use for the scheduler in the dynamic profile.

user@host# set shaping-rate 50k
The shaping rate places a maximum limit on a queue’s transmit capacity. By default, the shaping rate
is equal to the interface speed/shaping rate enabling the queue to send a the full rate of the interface.
4. Configure the guaranteed rate [in bits per second (bps)] to use for the scheduler in the dynamic profile.

user@host# set guaranteed-rate 10k
The guaranteed rate is the minimum bandwidth the queue can receive; if excess physical interface
bandwidth is available for use, the logical interface can receive more than the guaranteed rate provisioned
for the interface, depending on how you choose to manage excess bandwidth and the interface’s mode
of PIR compared to CIR/PIR.
5. Configure the delay-buffer rate [in bits per second (bps)] based on the delay-buffer calculation.

user@host# set delay-buffer-rate 10k
107
The delay buffer rate setting at one level of the hierarchy becomes the reference bandwidth used at
the next higher level, and the sum of the reference bandwidth cannot exceed the value used at a lower
level. If you do not include this statement, the delay-buffer rate is based on the guaranteed rate if one
is configured, or on the shaping rate if no guaranteed rate is configured.
6. After you configure the traffic shaping and scheduling CoS parameters in a dynamic profile, you apply
them to an interface. The output traffic-control profile enables you to provide traffic scheduling to the
interface.
Configure the interface name and logical interface using a variable, and apply the output traffic-control
profile to the interface. Specify the previously defined traffic-control profile, tcp-data-service.

user@host# set interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit
output-traffic-control-profile tcp-data-service
Results
Confirm the configuration and application of the static traffic shaping and scheduling parameters by
entering the show dynamic-profiles configuration command. If the command output does not display the
intended configuration, repeat the instructions in this procedure to correct the configuration.
[edit]
dynamic-profiles {
data-service {
class-of-service {
interfaces {
output-traffic-control-profile tcp-data-service;
}
}
}
tcp-data-service {
scheduler-map data-service-map;
shaping-rate 50k;
guaranteed-rate 10k;
delay-buffer-rate 10k;
}
}
}
}
108
Verification
IN THIS SECTION
Verifying Traffic Shaping and Scheduling Profiles for Subscriber Access | 108
Verifying the Mapping of Schedulers for Subscriber Access | 108
Confirm that the configuration is working properly.
Verifying Traffic Shaping and Scheduling Profiles for Subscriber Access
Purpose
View the class-of-service (CoS) configurations that are referenced in a dynamic profile for subscriber
access.
Action
user@host> show class-of-service traffic-control-profile
Traffic control profile: tcp-data-service, Index: 57625

Shaping rate: 50000
Scheduler map: data-service-map
Delay Buffer rate: 10000
Guaranteed rate: 10000
Meaning
The Shaping rate, Delay Buffer rate, and Guaranteed rate fields indicate rates of 50,000 bps, 10,000 bps,
and 10,000 bps, respectively, for the traffic-control profile.
Verifying the Mapping of Schedulers for Subscriber Access
Purpose
Display the mapping of schedulers to forwarding classes and a summary of scheduler parameters for each
entry.
109
Action
Scheduler map: data-service-map, Index: 84
Scheduler: be-scheduler, Index: 8721, Forwarding class: best-effort

Transmit rate: 40 percent, Rate Limit: none, Maximum buffer delay: 39 ms,
Priority: low
Drop profiles:
Any Any 8724 drop3
Meaning
The Scheduler map field indicates the parameters are for the best-effort scheduler. The Transmit rate field
shows 40 percent; the Rate Limit field indicates no limit; and the Drop profiles fields are for drop3.

110
CHAPTER 4
Applying CoS to Groups of Subscriber Interfaces
IN THIS CHAPTER
Example: Configuring a Dynamic Service VLAN Interface Set of Subscribers in a Dynamic Profile | 132
CoS for Interface Sets of Subscribers Overview
IN THIS SECTION
Guidelines for Configuring Dynamic Interface Sets in a Subscriber Access Network | 110
Interface sets enable service providers to group logical interfaces or other interface sets so they can apply
CoS parameters to all of the traffic in the group.
Interface sets are beneficial for various scenarios in a subscriber access network. For example, you can
use an interface set to configure a local loop with a small number of subscribers. Interface sets are also
useful for grouping a large number of subscribers into a particular service class or for defining traffic
engineering aggregates for DSLAMs.
Guidelines for Configuring Dynamic Interface Sets in a Subscriber Access Network
When configuring interface sets for subscriber access, keep the following guidelines in mind:
• You can configure interface sets of VLAN demux, PPPoE, or demux interfaces over aggregated Ethernet
interfaces.
• An interface can only belong to one interface set. If you try to add the same interface to different interface
sets, the commit operation fails.
111
• You configure the interface set and the traffic scheduling and shaping parameters in a dynamic profile.
However, you must apply the traffic-control profile to the interface set in the static [edit class-of-service]
hierarchy.
NOTE: This rule applies to all interface sets except ACI sets.
• The $junos-interface-set-name predefined variable is available only for RADIUS Accept messages;
change of authorization (CoA) requests are not supported.
• The $junos-aggregation-interface-set-name is the L2 interface-set representing a logical intermediate

node (DPU-C or PON tree) in the access network.
• The $junos-phy-ifd-underlying-intf-set-name represents a default, topology-based interface-set (based

on the physical interface name with a post-pend of “-underlying”) to conserve L2 CoS nodes.
• The $junos-svlan-interface-set-name predefined variable locally generates an interface set name for
use by dual-tagged VLAN interfaces based on the outer tag of the dual-tagged VLAN. The format of the
generated variable is physical_interface_name - outer_VLAN_tag. For example, an aggregated Ethernet
interface “ae0,” with a dual-tagged VLAN interface that has an outer tag of “111,” results in a
$junos-svlan-interface-set-name dynamic variable of “ae0-111”. Similarly, a non-aggregated Ethernet
interface of ge-1/1/0, with the same dual-tagged VLAN interface that has an outer tag of “111,” results
in a $junos-svlan-interface-set-name dynamic variable of “ge-1/1/0-111”.
• The $junos-phy-ifd-interface-set-name predefined variable locally generates an interface set name

associated with the underlying physical interface in a dynamic profile. This predefined variable enables
you to group all the subscribers on a specific physical interface so that you can apply services to the
entire group of subscribers.
Another use case for this predefined variable is to conserve CoS resources in a mixed business and
residential topology by collecting the residential subscribers into an interface set associated with the
physical interface, so that a level 2 node is used for the interface set rather than for each residential
interface. Otherwise, because the business and residential subscribers share the same interface and
business subscribers require three levels of CoS, then three levels are configured for each residential
subscriber. That results in an unnecessary level 2 node being consumed for each residential connection,
wasting CoS resources.
• The $junos-tagged-vlan-interface-set-name predefined variable locally generates an interface set name

used for grouping logical interfaces stacked over logical stacked VLAN demux interfaces for either a 1:1
(dual-tagged; individual client) VLAN or N:1 (single tagged; service) VLAN. The format of the generated
variable differs with VLAN type as follows:
• Dual-tagged (client) VLAN—physical_interface_name - outer_VLAN_tag - inner_VLAN_tag. For example,

an aggregated Ethernet interface “ae0,” with a dual-tagged VLAN interface that has an outer tag of
“111” and an inner tag of “200,” results in a $junos-tagged-vlan-interface-set-name dynamic variable
of “ae0-200-111”. Similarly, a non-aggregated Ethernet interface of ge-1/1/0, with the same dual-tagged
112
VLAN interface that has an outer tag of “111” and an inner tag of “200,” results in a
$junos-tagged-vlan-interface-set-name dynamic variable of “ge-1/1/0-200-111”.
• Single tagged (service) VLAN—physical_interface_name - VLAN_tag. For example, an aggregated Ethernet

interface “ae0,” with an N:1 VLAN using the single tag of “200,” results in a
$junos-tagged-vlan-interface-set-name dynamic variable of “ae0-200”. Similarly, a non-aggregated
Ethernet interface of ge-1/1/0, with the same N:1 VLAN using the single tag of “200,” results in a
$junos-tagged-vlan-interface-set-name dynamic variable of “ge-1/1/0-200”.
• All dynamic demux, dual-tagged VLAN logical interfaces with the same outer VLAN tag and physical
interface are assigned to the same interface set and all CoS values provisioned with the dynamic profile
are applied to the interfaces that are part of the set.
• The interface set name must be explicitly referenced in the CoS configuration as part of the static
configuration outside of the dynamic profile. The CoS configuration is static and the interface set name
must be statically referenced.
NOTE: This rule applies to all interface sets except ACI sets.
• RADIUS can return an access-accept message under certain conditions. A configured RADIUS VSA for
the interface set name takes precedence over the locally generated variable on the router. This means
that if the interface-set-name VSA is configured on RADIUS, the router continues to use this variable
instead of the locally generated value from the dynamic variable.
• Sets of aggregated Ethernet interfaces are supported on MPC/MIC interfaces on MX Series routers
only.
• The supported interface stacks for aggregated Ethernet in an interface set include VLAN demux interfaces,
IP demux interfaces, and PPPoE logical interfaces over VLAN demux interfaces.
• The link membership list and scheduler mode of the interface set are inherited from the underlying
aggregated Ethernet interface over which the interface set is configured.
• When an aggregated Ethernet interface operates in link protection mode, or if the scheduler mode is
configured to replicate member links, the scheduling parameters of the interface set are copied to each
of the member links.
• If the scheduler mode of the aggregated Ethernet interface is set to scale member links, the scheduling
parameters are scaled based on the number of active member links and applied to each of the aggregated
interface member links.

113
Example: Configuring a Dynamic Service VLAN Interface Set of Subscribers in a Dynamic Profile | 132
Configuring an Interface Set of Subscribers in a Dynamic Profile
Interface sets enable you to provide hierarchical scheduling to a group of subscriber interfaces.
Before you begin, configure the subscriber interfaces that you intend to include in the interface set.
To configure an interface set of subscriber interfaces:
1. Configure the interface set in the dynamic profile.
[edit dynamic-profiles profile-name interfaces]

user@host#edit interface-set interface-set-name
Replacing the interface-set-name variable with the $junos-interface-set-name,

$junos-svlan-interface-set-name, or $junos-tagged-vlan-interface-set-name predefined variable. The
interface set is created dynamically when the subscriber logs in.
2. Include the interfaces within the dynamic interface-set.
[edit dynamic-profiles profile-name interfaces interface-set $junos-interface-set-name]

user@host# set interface interface-name unit logical-unit-number
3. Apply traffic shaping and queuing parameters to the interface set.
TIP: You must configure the interface set in the static [edit class-of-service] hierarchy, not
in the [edit dynamic-profiles] hierarchy.

user@host# edit interface-set interface-set-name
[edit class-of-service interfaces interface-set interface-set-name]
user@host# set output-traffic-control-profile profile-name

114

CoS for Aggregated Ethernet Subscriber Interfaces Overview
Example: Configuring a Dynamic Interface Set of VLAN Subscribers
IN THIS SECTION
Requirements | 114
Overview | 114
Configuring the Dynamic VLANs | 114
Configuring Dynamic Traffic Scheduling and Shaping | 117
Configuring the Interface Set in the Dynamic Profile | 121
Configuring DHCP Access | 123
Configuring RADIUS Authentication | 125
Verification | 131
Requirements
This example uses the following software and hardware components:
• MX Series Router with MPCs
Overview
In this example, the network administrator groups dynamic VLAN interfaces in an interface set. The
interface set is configured in a dynamic profile, and enables hierarchical scheduling for the VLAN interfaces
for a multiplay service.
DHCP is used as the access method, and RADIUS is used as the authentication method for the interfaces
associated with the interface set.
Configuring the Dynamic VLANs

115
To quickly configure the dynamic VLANs, copy the following commands and paste them into the router
terminal window:
[edit]
edit dynamic-profiles vlan-prof
edit interfaces $junos-interface-ifd-name unit $junos-interface-unit
set vlan-id $junos-vlan-id
set demux-source inet
set family inet unnumbered-address lo0.0 preferred-source-address 203.0.113.32
top
edit interfaces ge-1/0/0
set hierarchical-scheduler
set vlan-tagging
edit auto-configure vlan-ranges dynamic-profile vlan-prof
set ranges any
set accept inet
top
set interfaces lo0 unit 0 family inet address 203.0.113.32/32
Configuring the Dynamic Profile for the Autoconfigured VLANs
In this section, you create a dynamic profile for the VLAN IDs to be automatically assigned when subscribers
log in.
To configure the dynamic profile for the VLANs:
1. Configure the dynamic profile.
[edit]
user@host#edit dynamic-profile vlan-prof
2. Configure the interfaces.
[edit dynamic-profiles vlan-prof]

user@host#edit interfaces $junos-interface-ifd-name unit $junos-interface-unit
3. Add the VLAN ID variable.
[edit dynamic-profiles vlan-prof interfaces $junos-interface-ifd-name unit $junos-interface-unit]

user@host#set vlan-id $junos-vlan-id
116
4. Configure the demux source as IPv4.

user@host#set demux-source inet
5. Configure the family.

user@host#set family inet unnumbered-address lo0.0 preferred-source-address 203.0.113.32
Configuring the VLAN Interfaces
To configure the VLAN interfaces:
1. Create the VLAN interface.
[edit]
user@host# edit interfaces ge-1/0/0
2. Enable hierarchical scheduling.

3. Configure VLAN tagging.

user@host# set vlan-tagging
4. Configure auto-configuration for the dynamic profile.

user@host# edit auto-configure vlan-ranges dynamic-profile vlan-prof
5. Configure any VLAN ID range.
[edit interfaces ge-1/0/0 auto-configure vlan-ranges dynamic-profile vlan-prof]

user@host# set ranges any
117
6. Specify IPv4 traffic for the VLAN.
[edit interfaces ge-1/0/0 auto-configure vlan-ranges dynamic-profile vlan-prof]

user@host# set accept inet
Configuring the Loopback Interface
To configure the loopback interface:
1. Create the loopback interface.
[edit]
user@host# edit interfaces lo0
2. Configure the unit and the family.
[edit intefaces lo0]

user@host# set unit 0 family inet address 203.0.113.32/32
Configuring Dynamic Traffic Scheduling and Shaping

To quickly configure the traffic scheduling and shaping parameters, copy the following commands and
paste them into the router terminal window:
[edit]
edit dynamic-profiles multiplay class-of-service schedulers be_sch
set transmit-rate percent 12
set buffer-size percent 12
set priority low
up
edit ef_sch
set priority low
up
edit af_sch
set priority low
118
up
edit nc_sch
set priority low
up
edit voice_sch
set priority low
up
edit video_sch
set priority low
up
edit game_sch
set priority low
up
edit data_sch
set priority low
up 2
edit scheduler-maps all_smap
set forwarding-class be scheduler be_sch
set forwarding-class ef scheduler ef_sch
set forwarding-class af scheduler af_sch
set forwarding-class nc scheduler nc_sch
set forwarding-class voice scheduler voice_sch
set forwarding-class video scheduler video_sch
set forwarding-class game scheduler game_sch
set forwarding-class data scheduler data_sch
up 2
edit traffic-control-profiles multiplay
set scheduler-map all_smap
set shaping-rate 100m
set guaranteed-rate 20m
Configuring the Schedulers in the Dynamic Profile
119
In this section, you create a dynamic profile for the multiplay service and configure scheduling and shaping.
To configure the schedulers:
1. Create the multiplay dynamic profile.
[edit]
user@host# edit dynamic-profiles multiplay class-of-service schedulers
2. Configure the best effort scheduler.
[edit dynamic-profiles multiplay class-of-service schedulers]

user@host# edit be_sch
user@host# set buffer-size percent 12
3. Configure the expedited forwarding scheduler.

user@host# edit ef_sch
4. Configure the assured forwarding scheduler.

user@host# edit af_sch
5. Configure the network control scheduler.

user@host# edit nc_sch
120
6. Configure the voice scheduler.

user@host# edit voice_sch
7. Configure the video scheduler.

user@host# edit video_sch
8. Configure the gaming scheduler.

user@host# edit game_sch
9. Configure the data scheduler.

user@host# edit data_sch
Configuring the Scheduler Map in the Dynamic Profile
To configure the scheduler map:
1. Configure the scheduler map for all of the services.
[edit dynamic-profiles multiplay class-of-service]

user@host# edit scheduler-maps all_smap
121
2. Configure the forwarding classes for each service in the scheduler map.
[edit dynamic-profiles multiplay class-of-service scheduler-maps all_smap]

user@host# set forwarding-class be scheduler be_sch
user@host# set forwarding-class ef scheduler ef_sch
user@host# set forwarding-class af scheduler af_sch
user@host# set forwarding-class nc scheduler nc_sch
user@host# set forwarding-class voice scheduler voice_sch
user@host# set forwarding-class video scheduler video_sch
user@host# set forwarding-class game scheduler game_sch
user@host# set forwarding-class data scheduler data_sch
Configuring the Traffic-Control Profile in the Dynamic Profile
To configure the traffic-control profile the interface set:
1. Configure the traffic-control profile.
[edit dynamic-profiles multiplay class-of-service]

user@host# edit traffic control-profiles multiplay
2. Configure the scheduler map.
[edit dynamic-profiles multiplay class-of-service traffic control-profiles multiplay]

user@host# set scheduler-map all_smap
3. Configure the shaping rate.

user@host# set shaping-rate 100m
4. Configure the guaranteed rate.

user@host# set guaranteed-rate 20m
Configuring the Interface Set in the Dynamic Profile

122
To quickly configure the interface set, copy the following commands and paste them into the router
terminal window:
[edit]
edit dynamic-profiles multiplay
edit interfaces interface-set $junos-interface-set-name
set interface $junos-interface-ifd-name unit $junos-underlying-interface-unit
top
edit class-of-service interfaces interface-set
set output-traffic-control-profile multiplay
Configuring the Interfaces for the Interface Set
To configure the interface variable for the interface set:
1. Configure the dynamic profile for the interface set.
[edit]
user@host#edit dynamic-profiles multiplay
2. Configure the interface using the Junos OS predefined variable.
[edit dynamic-profiles multiplay]

user@host#edit interfaces $junos-interface-ifd-name unit $junos-underlying-interface-unit
3. Configure the family.
[edit dynamic-profiles multiplay interfaces $junos-interface-set-name unit $junos-underlying-interface-unit]

user@host#set family inet unnumbered-address lo0.0 preferred-source-address 203.0.113.32
Configuring the Interface Set
To configure the interface set:
1. Configure the interface set using the Junos OS predefined variable.
[edit dynamic-profiles multiplay]

user@host#edit interfaces interface-set $junos-interface-set-name
123
2. Add the dynamic VLAN interfaces to the interface set.
[edit dynamic-profiles multiplay interfaces $junos-interface-set-name]

user@host#set interface $junos-interface-ifd-name unit $junos-underlying-interface-unit
Applying the Traffic-Control Profile to the Interface Set
You apply the traffic-control profile outside of the dynamic profile in the [edit class-of-service] hierarchy.
To apply the traffic-control profile:
1. Specify the interface set to which you want to apply the traffic-control profile.
user@host#edit interfaces interface-set dynamic-set
2. Attach the output traffic-control profile defined in the dynamic profile to the interface set.

user@host#set output-traffic-control-profile multiplay
Configuring DHCP Access

To quickly configure DHCP access, copy the following commands and paste them into the router terminal
window:
[edit]
edit system services dhcp-local-server authentication
set password $ABC123
set username-include user-prefix multiplay
up 1
set dynamic-profile dhcp-vlan-prof aggregate-clients replace
set group vlans interface ge-1/0/0
top
edit access address-assignment pool v4 family inet
set network 203.0.113.0/16
set range limited low 203.0.113.10
set range limited high 203.0.113.250
set dhcp-attributes maximum-lease-time 84600
124
Configuring the DHCP Local Server
To configure DHCP access:
1. Configure the DHCP local server.
[edit system]
user@host# edit services dhcp-local-server authentication
2. Set the password.
[edit system services dhcp-local-server authentication]

user@host# set password $ABC123
3. Specify that you want to include optional information in the username.
[edit system services dhcp-local-server authentication]

user@host# set username-include user-prefix multiplay
4. Attach the dynamic profile with the interface set.
[edit system services dhcp-local-server]

user@host# set dynamic-profile dhcp-vlan-prof aggregate-clients replace
5. Configure a group for the VLAN interface.
[edit system services dhcp-local-server]

user@host# set group vlans interface ge-1/0/0
Configuring Address Assignment Pools
To configure address assignment pools:
1. Configure the pool of IPv4 addresses.
[edit access]
user@host#edit address-assignment pool v4 family inet
125
2. Configure the family of interfaces in the pool.
[edit access address-assignment pool v4]

user@host#set network 203.0.113.0/16
3. Configure the upper and lower bounds of the address range.

user@host#set range limited low 203.0.113.10
user@host#set range limited high 203.0.113.250
4. Configure the maximum length of time in seconds for which a subscriber can request and hold a lease.

user@host#set dhcp-attributes maximum-lease-time 84600
Configuring RADIUS Authentication

To quickly configure RADIUS authentication, copy the following commands and paste them into the router
terminal window:
[edit]
edit access radius-server 192.51.100.108
set secret $ABC123ABC123ABC123
set timeout 5
set retry 5
up 2
edit profile acc-prof
set authentication-order radius
set radius authentication-server 192.51.100.108
Configuring RADIUS Access
To configure RADIUS access:
1. Configure the RADIUS server.
[edit access]
user@host#edit radius-server 192.51.100.108
126
2. Configure the required secret (password) that the local router or switch passes to the RADIUS client.
[edit access radius-server 192.51.100.108]

user@host# set secret $ABC123ABC123ABC123
3. Configure the length of time that the local router or switch waits to receive a response from a RADIUS
server.

user@host# set timeout 5
4. Configure the number of times that the router or switch attempts to contact a RADIUS accounting
server.

user@host# set retry 5
5. Configure the access profile.
[edit access]
user@host#edit profile acc-prof
6. Configure the authentication order.
[edit access profile acc-prof ]

user@host# set authentication-order radius
7. Configure the authentication server.
[edit access profile acc-prof]

user@host#set radius authentication-server 192.51.100.108
Results
dynamic-profiles {
vlan-prof {
interfaces {
127
“$junos-interface-ifd-name” {
unit "$junos-interface-unit" {
vlan-id "$junos-vlan-id";
demux-source inet;
family inet {
}
}
}
}
}
multiplay {
class-of-service {
multiplay {
scheduler-map all_smap;
shaping-rate 100m;
}
}
interfaces {
interface-set “$junos-interface-set-name” {
interface “$junos-interface-ifd-name” {
unit “$junos-underlying-interface-unit”;
}
}
“$junos-interface-ifd-name” {
output-traffic-control-profile multiplay;
}
}
}
scheduler-maps {
all_smap {
forwarding-class voice scheduler voice_sch;
forwarding-class video scheduler video_sch;
forwarding-class game scheduler game_sch;
forwarding-class data scheduler data_sch;
}
}
128
schedulers {
be_sch {
priority low;
}
ef_sch {
priority low;
}
af_sch {
priority low;
}
nc_sch {
priority low;
}
voice_sch {
priority low;
}
video_sch {
priority low;
}
game_sch {
priority low;
}
data_sch {
priority low;
}
}
}
}
129
access {
radius-server {
192.51.100.108 {
secret "$ABC123ABC123ABC123"; ## SECRET-DATA
timeout 5;
retry 5;
}
}
profile acc-prof {
authentication-order radius;
radius {
authentication-server 192.51.100.108;
}
}
address-assignment {
pool v4 {
family inet {
network 203.0.113.0/16;
range limited {
low 203.0.113.10;
high 203.0.113.250;
}
dhcp-attributes {
maximum-lease-time 84600;
}
}
}
}
}
class-of-service {
interfaces {
interface-set dynamic-set {
output-traffic-control-profile multiplay;
}
}
}
interfaces {
interface-set “$junos-interface-set-name” {
interface "$junos-interface-ifd-name" {
unit "$junos-underlying-interface-unit";
}
}
"$junos-interface-ifd-name" {
unit "$junos-underlying-interface-unit" {
130
family inet {
}
}
}
}
}
}
interfaces {
ge-1/0/0 {
vlan-tagging;
auto-configure {
vlan-ranges {
dynamic-profile vlan-prof {
accept inet;
ranges {
any;
}
}
}
}
}
lo0 {
unit 0 {
family inet {
address 203.0.113.32/32;
}
}
}
}
system {
services {
dhcp-local-server {
authentication {
password $ABC123;
username-include {
user-prefix multiplay;
}
}
dynamic-profile multiplay aggregate-clients replace;
group vlans {
interface ge-1/0/0.0;
}
131
}
}
}
Verification
IN THIS SECTION
Verifying the Interfaces that are Included in the Interface Set | 131
Verifying the Traffic Scheduling and Shaping Parameters for the Interface Set | 131
To confirm that the configuration is correct, perform these tasks:
Verifying the Interfaces that are Included in the Interface Set
Purpose
Verify the interfaces included in the interface set.
Action
user@host> show interfaces interface-set dynamic-set terse
Verifying the Traffic Scheduling and Shaping Parameters for the Interface Set
Purpose
Verify that the traffic scheduling and shaping parameters are applied properly to an interface included in
the interface set.
Action
user@host> show class-of-service interface

132
Example: Configuring a Dynamic Service VLAN Interface Set of Subscribers

in a Dynamic Profile
IN THIS SECTION
Requirements | 132
Overview | 132
Configuration | 133
Verification | 136
Interface sets enable you to provide hierarchical scheduling to a group of subscriber interfaces. In this
example, by using the $junos-svlan-interface-set-name internal dynamic variable when specifying the
interface set name, you can locally generate an interface set name for use by SVLAN interfaces based on
the outer tag of the dual-tagged VLAN. The format of the generated variable is physical_interface_name -
outer_VLAN_tag.
Requirements
Before you begin, configure the subscriber interfaces that you intend to include in the interface set. You
can find general configuration instructions for the supported dynamic interface configuration in DHCP
Subscriber Interface Overviewand in the following:
• For dynamic VLAN interfaces, see Configuring a Static or Dynamic VLAN Subscriber Interface over Aggregated
Ethernet.
• For dynamic IP demux interfaces, see Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces
in Dynamic Profiles and Configuring a Static or Dynamic IP Demux Subscriber Interface over Aggregated
Ethernet.
• For dynamic VLAN demux interfaces, see Configuring Dynamic Subscriber Interfaces Using VLAN Demux
Interfaces in Dynamic Profiles.
Overview
Interface sets enable you to provide hierarchical scheduling to a group of subscriber interfaces. By using
the $junos-svlan-interface-set-name internal dynamic variable when specifying the interface set name,
you can locally generate an interface set name for use by SVLAN interfaces based on the outer tag of the
dual-tagged VLAN. The format of the generated variable is physical_interface_name - outer_VLAN_tag.
133
This example includes the following statements:
• interface-set—Configures the name of the scheduler for dynamic CoS. In this example, you use the
$junos-svlan-interface-set-name variable to obtain the locally generated interface set name for use by
SVLAN interfaces based on the outer tag of the dual-tagged VLAN.
• output-traffic-control-profile—Applies an output traffic scheduling and shaping profile to the interface

set.
• output-traffic-control-profile-remaining—Applies an output traffic scheduling and shaping profile for

remaining traffic to the interface set.
Configuration

[edit]
set dynamic-profiles profile-dhcp-ipdemux interfaces interface-set $junos-svlan-interface-set-name interface
$junos-interface-ifd-name unit $junos-underlying-interface-unit
set dynamic-profiles profile-dhcp-ipdemux interfaces $junos-interface-ifd-name unit
$junos-underlying-interface-unit
set class-of-service traffic-control-profiles tcp1 scheduler-map schedMap
set class-of-service traffic-control-profiles tcp1 shaping-rate 50m
set class-of-service traffic-control-profiles tcp1 guaranteed-rate 200k
set class-of-service traffic-control-profiles tcp3 scheduler-map ss1q0q1
set class-of-service traffic-control-profiles tcp3 shaping-rate 20m
set class-of-service traffic-control-profiles tcp3 guaranteed-rate 5m
set class-of-service interfaces interface-set ae0-111 output-traffic-control-profile tcp1
set class-of-service interfaces interface-set ae0-111 output-traffic-control-profile-remaining tcp3
To configure an SVLAN interface set of subscriber interfaces:
1. Access the dynamic profile you want to modify for interface sets.
[edit]
user@host# edit dynamic-profiles profile-dhcp-ipdemux
2. Access the dynamic profile interface configuration.

134
[edit dynamic-profiles profile-dhcp-ipdemux]

user@host# edit interfaces
3. Configure the SVLAN interface set in the dynamic profile.
The interface set is created dynamically when the subscriber logs in.
[edit dynamic-profiles profile-dhcp-ipdemux interfaces]

user@host# edit interface-set $junos–svlan-interface-set-name
4. Include dynamic IP demux interface creation within the dynamic interface set.
[edit dynamic-profiles profile-dhcp-ipdemux interfaces interface-set $junos-svlan-interface-set-name]

user@host# set interface $junos-interface-ifd-name unit $junos-underlying-interface-unit
5. Access the SVLAN interface set name that you expect $junos-svlan-interface-set-name to generate.
For example, to specify the expected interface set name for aggregated Ethernet interface ae0 and
outer VLAN tag 111, include ae0-111 for the interface-set-name variable.

user@host# edit interface-set ae0-111
6. Apply traffic shaping and queuing parameters to the SVLAN interface set.
TIP: You must configure the interface set in the static [edit class-of-service] hierarchy, not
in the [edit dynamic-profiles] hierarchy.
[edit class-of-service interfaces interface-set ae0-111]

user@host# set output-traffic-control-profile tcp1
7. Apply traffic shaping and queuing parameters to any remaining traffic on the SVLAN interface set.
[edit class-of-service interfaces interface-set ae0-111]

user@host# set output-traffic-control-profile-remaining tcp3
135
Results
From configuration mode, confirm your configuration by entering the show dynamic-profiles command
and the show class-of-service command. If the output does not display the intended configuration, repeat
the instructions in this example to correct the configuration.

dynamic-profiles {
profile-dhcp-ipdemux {
interfaces {
interface-set "$junos-svlan-interface-set-name" {
interface "$junos-interface-ifd-name" {
}
}
}
}
}
}
user@host# show class-of-service

class-of-service {
tcp1 {
scheduler-map schedMap;
shaping-rate 50m;
guaranteed-rate 200k;
}
tcp3 {
inactive: scheduler-map ss1q0q1;
shaping-rate 20m;
guaranteed-rate 5m;
}
}
interfaces {
interface-set ae0-111 {
output-traffic-control-profile tcp1;
output-traffic-control-profile-remaining tcp3;
}
}
}
136
Verification
To confirm that the configuration is correct, perform these tasks:
Verifying the Interfaces that are Included in the Interface Set
Purpose
Verify the interfaces that are included in the interface set.
Action
user@host> show class-of-service interface-set
Displaying Information for Active Subscribers
Purpose
Display information for active subscribers.
Action
user@host> show subscribers detail
Dynamic Profiles Overview

Configuring a Basic Dynamic Profile
Configuring Remaining Common Queues on MIC and MPC Interfaces
137
CHAPTER 5
Configuring Hierarchical Scheduling for MPLS

Pseudowire Interfaces
IN THIS CHAPTER
Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical
Interfaces over a Transport Logical Interface) | 147
Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces (Logical
Interfaces over a Pseudowire Interface Set) | 149
Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview
Junos OS supports two aspects of CoS for MPLS pseudowire subscriber interfaces. You can apply CoS
rewrite rules and behavior aggregate (BA) classifiers to MPLS pseudowire subscriber interfaces. In addition,
CoS performs egress hierarchical shaping towards the subscriber on MPLS pseudowire subscriber interfaces.
Hierarchical CoS enables you to apply traffic scheduling and queuing parameters and packet transmission
scheduling parameters to an individual subscriber interface rather than to all interfaces configured on the
port. Hierarchical CoS is supported on MX Series routers with either EQ DPCs or MPC/MICs installed.
On Juniper Networks MX Series routers, MPC/MIC and EQ DPC interfaces support a four-level CoS
scheduling hierarchy that, when fully configured, consists of the physical interface (level 1), the interface
set or the underlying interface (level 2), one or more logical interfaces (level 3), and one or more queues
(level 4). Although all CoS scheduling hierarchies are four-level, level 1 is always the physical interface and
level 4 is always the queue. Hierarchical scheduling configurations consist of the type of interfaces you
configure; for example, a logical interface or an interface set and where those interfaces reside in the
scheduling hierarchy, either level 2 or level 3. Because many hierarchical scheduling configurations are
possible, we use the terms two-level hierarchical scheduling and three-level hierarchical scheduling in this
discussion.
138
Pseudowire Subscriber Logical Interfaces Overview

Configuring a Pseudowire Subscriber Logical Interface
CoS Configuration Overview for MPLS Pseudowire Subscriber Interfaces
CoS supports two-level and three-level hierarchies for MPLS pseudowire subscriber interfaces.
To configure two-level scheduling, include the maximum-hierarchy-levels 2 option under the [edit interfaces
interface-name hierarchical-scheduler] statement on the physical interface of the logical tunnel anchor
point.
To configure three-level hierarchical scheduling, include the implicit-hierarchy option under the [edit
interfaces interface-name hierarchical-scheduler] statement on the physical interface of the logical tunnel
anchor point. Use the following guidelines for configuring the implicit-hierarchy option:
• If an output traffic-control profile is configured on the pseudowire transport interface and on a pseudowire
service interface, the two interfaces form a scheduling hierarchy. The pseudowire transport interface
resides in a level 2 scheduler node and the pseudowire service interface resides in a level 3 scheduler
node.
• If an output traffic-control profile is configured on the pseudowire services interface but not on a
pseudowire transport interface, the pseudowire services interface resides in a level 3 scheduler node.
• If an output traffic-control profile is only configured on the pseudowire transport interface and not on
the pseudowire services interface, the pseudowire transport interface resides in a level 3 scheduler node
and all pseudowire traffic uses this node.
If the implicit-hierarchy option is not set on the logical tunnel anchor point, logical interfaces behave
normally with the hierarchical-scheduler mode configured with or without the hierarchical-scheduler
maximum-hierarchy-levels option under the [edit interfaces interface-name hierarchical-scheduler]
statement. In this case, when you apply a traffic-control profile to the pseudowire transport and service
logical interfaces, they both reside in level 3 scheduler nodes and do not form a scheduling hierarchy,
which might not be the desirable behavior. In business edge, where only the pseudowire logical interfaces
need to be shaped, applying the traffic-control profile at just the transport logical interface may be sufficient.
139
When configuring the logical tunnel physical interface for the maximum hierarchy level, all pseudowire
logical interfaces operating on the physical interface use the same hierarchy model. If you want to mix
two-level and three-level scheduling hierarchies, you can group the pseudowires together by hierarchy
levels and share the same logical tunnel anchor point or you can use three-level scheduling for all
pseudowires over the anchor point.
To specify rewrite rules and classifiers on pseudowire interfaces, reference the pseudowire device under
the [edit class-of-service interfaces] hierarchy level and specify the rewrite rules and classifiers for the
pseudowire interfaces.
To control all pseudowire traffic using the same logical tunnel interface, apply CoS policies at the physical
interface for the anchor logical tunnel.
NOTE: Starting with Junos OS Release 17.3R1, stateful anchor point redundancy support is
provided for pseudowire subscriber logical interface by the underlying redundant logical tunnel
interface (rlt) in active-backup mode. This redundancy protects the access and the core facing
link against anchor PFE (Packet Forwarding Engine) failure. Starting in Junos OS Release 18.1R2,
full hierarchical CoS support is provided for stateful anchor point redundancy of pseudowire
subscriber logical interfaces. Both transport and services logical interfaces created for the
pseudowire subscriber logical interface are stacked on the underlying redundant logical tunnel
control logical interface. This logical interface stacking model is used for both redundant and
non-redundant pseudowire subscriber logical interfaces. Hierarchical CoS is supported and
configured the same on both redundant and non-redundant pseudowire subscriber logical
interfaces.
Release Description
18.1R2 Starting in Junos OS Release 18.1R2, full hierarchical CoS support is provided for stateful
anchor point redundancy of pseudowire subscriber logical interfaces.

140
Anchor Redundancy Pseudowire Subscriber Logical Interfaces Overview
CoS Two-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber

Interfaces
Two-level hierarchical scheduling limits the number of hierarchical levels in the scheduling hierarchy to
two. In a two-level scheduling hierarchy, all logical interfaces and interface sets share a single level 2 node.
Table 15 on page 140 summarizes the interface hierarchy and the CoS scheduler node levels for two-level
hierarchical scheduling.
Table 15: Two-Level Hierarchical Scheduling–Interface Hierarchy Versus Scheduling Nodes
Physical interface – Pseudowire transport logical One or more queues

interface
Physical interface – Interface set One or more queues
Physical interface – Pseudowire service logical interface One or more queues
You use the two-level hierarchical scheduling when you have many pseudowires but you do not require
shaping specific to the subscriber logical interface. For example, when your configuration is one subscriber
per pseudowire interface.
Figure 14 on page 141 shows a two-level hierarchical scheduling configuration for the MPLS pseudowires.
In this configuration, level 1 is the physical interface used for the logical tunnel anchor node. All of the
pseudowire transport interfaces share a single level 2 node. The level 3 nodes are the pseudowire transport
logical interfaces (ps0.0, ps1.0, and ps2.0). In this configuration, interface sets are not configured and only
the logical interfaces have traffic control profiles.
141
Figure 14: MPLS Pseudowire Subscriber Interface Two-Level Scheduler Configuration
Queues Queues Queues
L4
Pseudowire ps0.0 ps1.0 ps2.0

L3
Logical Interfaces
TCP
L2 Dummy
L1 Logical Tunnel
g041325
Physical Interface
Two-level hierarchical scheduling has up to eight class of service queues. For this configuration, include
the maximum-hierarchy-levels 2 option under the [edit interfaces interface-name hierarchical-scheduler]
hierarchy level at the physical interface for the anchor logical tunnel.
NOTE: You cannot configure shaping policies on both the pseudowire logical interfaces and the
subscriber logical interfaces over the same pseudowire. If a traffic-control profile is configured
on a pseudowire logical interface, and CoS policies are configured on the subscriber logical
interface over another pseudowire, all of the logical interfaces are at level 3 and act as peers.

142
Configuring CoS Two-Level Hierarchical Scheduling for MPLS Pseudowire

Subscriber Interfaces
Before configuring CoS parameters for MPLS pseudowire subscriber interfaces, you must first complete
these tasks:
1. Configure the pseudowire logical interfaces. See Configuring a Pseudowire Subscriber Logical Interface.
2. Configure the pseudowire device count. See Configuring the Maximum Number of Pseudowire Logical
Interface Devices Supported on the Router.
3. Configure the pseudowire device including the logical tunnel anchor point. See Configuring a Pseudowire
Subscriber Logical Interface Device.
4. Configure the pseudowire transport logical interface. See Configuring the Transport Logical Interface for
a Pseudowire Subscriber Logical Interface.
5. Configure the pseudowire signaling (either Layer 2 circuit signaling or Layer 2 VPN signaling). See
Configuring Layer 2 Circuit Signaling for Pseudowire Subscriber Logical Interfaces or Configuring Layer 2
VPN Signaling for Pseudowire Subscriber Logical Interfaces.
6. Configure the pseudowire logical interfaces. See Configuring the Service Logical Interface for a Pseudowire
Subscriber Logical Interface.
To configure CoS policies on MPLS pseudowire subscriber interfaces using two-level scheduling:
1. Configure the hierarchical scheduler for the physical interface used for the logical tunnel (anchor point).
For two-level scheduling the hierarchical scheduler must be set to maximum-scheduler levels 2.
[edit]
user@host#edit interfaces ps-anchor-device-name
user@host#set hierarchical-scheduler maximum-hierarchy-levels 2
2. Specify the traffic-control profile to use on the pseudowire logical interface.
user@host#edit interfaces ps ps-device-name
user@host#edit unit logical-unit-number
user@host#set output-traffic-control-profile profile-name
3. Configure the rewrite rule.
The available rewrite rule types for pseudowire interfaces are dscp and inet-precedence.
143
user@host#edit rewrite-rules (dscp | inet-precedence) rewrite-name

user@host#edit forwarding-class class-name
user@host#set loss-priority class-name code-point (alias | bits)
4. Configure the classifier.
The available classifier types for pseudowire interfaces are dscp and inet-precedence.
user@host#edit classifiers (dscp | inet-precedence) classifier-name
user@host#set loss-priority class-name code-points [aliases] [bit-patterns]
5. Apply the rewrite rule and classifier to the pseudowire interface.
For the interface_name parameter, specify the pseudowire device name.
[edit class-of-service interfaces interface_name unit logical-unit-number]

user@host#set rewrite-rule (dscp | inet-precedence) (rewrite-name | default) protocol protocol-types
user@host#set classifiers (dscp | inet-precedence) (classifier-name | default)
CoS on Ethernet Pseudowires in Universal Edge Networks Overview

Mapping CoS Component Inputs to Outputs
144
CoS Three-Level Hierarchical Scheduling on MPLS Pseudowire Subscriber

Interfaces
In three-level hierarchical scheduling, the CoS scheduler nodes at level 1, level 2, and level 3 form a
scheduling hierarchy. You can configure many different three-level scheduling hierarchies, depending on
the location of the interface set and the use of underlying interfaces. In all variations, the physical interface
on which the logical tunnel resides is a level 1 CoS scheduler node and the queues reside at level 4.
Three-level scheduling hierarchies can have up to eight class of service queues.
Table 16 on page 144summarizes the most common three-level hierarchical scheduling configurations and
shows the interface hierarchy and CoS scheduler nodes.
Table 16: Three-Level Hierarchical Scheduling–Interface Hierarchy Versus CoS Scheduling Node Levels
Physical interface Pseudowire interface set Pseudowire service logical One or more queues
interfaces
Physical interface Pseudowire transport logical Pseudowire interface set One or more queues
interface
Physical interface Pseudowire transport logical Pseudowire service logical One or more queues
interface interfaces
Three-Level Scheduling Hierarchy: Pseudowire Logical Interfaces over a Transport Logical

Interface
Figure 15 on page 145 shows an MPLS pseudowire three-level scheduling hierarchy that includes two
pseudowire service logical interfaces over a pseudowire transport logical interface. This variation uses the
following scheduler nodes:
• Level 4—Forwarding class-based queues
• Level 3—Pseudowire service logical interfaces (ps0.1 and ps0.2) for subscriber sessions
• Level 2—Pseudowire transport logical interface (ps0.0)
• Level 1—Common/shared physical interface of the logical tunnel anchor point
You apply the traffic-control profiles at the pseudowire transport logical interfaces (level 2) and the
pseudowire service logical interfaces (level 3).
145
Figure 15: Three-Level Scheduling Hierarchy Case 1: Pseudowire Service Logical Interfaces over a
Transport Logical Interface
Queues Queues
L4
Pseudowire ps0.1 ps0.2

L3
Logical Interfaces
TCP
Pseudowire
L2 Transport ps0.0 TCP
Logical Interface
L1 Logical Tunnel
g041326
Physical Interface
Three-Level Scheduling Hierarchy : Pseudowire Service Logical Interfaces over a Pseudowire

Service Interface Set
Figure 16 on page 146 shows another variation of MPLS pseudowire three-level hierarchical scheduling
that includes two pseudowire service logical interfaces over a pseudowire service interface set. This
variation uses the following CoS scheduler nodes:
• Level 3—Pseudowire service logical interfaces (ps0.1 and ps0.2)
• Level 2—Pseudowire service interface set
You apply the traffic-control profile at the pseudowire service interfaces (level 3) and at the interface set
(level 2). This variation is most useful for subscriber edge deployments.
146
Figure 16: Three-Level Scheduling Hierarchy Case 2: Pseudowire Service Logical Interfaces over a
Pseudowire Service Interface Set
Queues Queues
L4
Pseudowire ps0.1 ps0.2

L3
Logical Interface
TCP
Interface Set of Pseudowire

L2 Pseudowire Logical Interface TCP
Logical Interfaces Set
Logical Tunnel
L1
g041327
Physical Interface
Three-Level Scheduling Hierarchy Combined Deployment Scenario
Figure 17 on page 146 shows a deployment scenario that combines the three-level hierarchical scheduling
scenarios in Figure 15 on page 145 and Figure 16 on page 146.
Figure 17: Three-Level Hierarchical Scheduling for MPLS Pseudowire Subscriber Interfaces—Deployment
Scenario
Queues Queues Queues Queues
L4
TCP TCP
ps0.1 ps0.2 ps1.1 ps1.2
L3
Pseudowire service Pseudowire service Pseudowire service Pseudowire service
interface interface interface interface
TCP
ps1.0
L2 Interface set Pseudowire transport
interface
L1 Physical interface
g041406
for logical tunnel
This variation uses the following CoS scheduler nodes:

147
• Level 3—Pseudowire service logical interfaces (ps0.1, ps0.2, ps1.1, and ps1.2)
• Level 2—Service interface set for pseudowire service interfaces (ps0.1 and ps0.2) and transport logical
interface (ps1.0) for the pseudowire service logical interfaces (ps1.1 and ps1.2)
You apply the traffic-control profiles to the interfaces at both level 2 and level 3, as well as the interface
set at level 2.

Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire

Subscriber Interfaces (Logical Interfaces over a Transport Logical Interface)
Before configuring CoS three-level scheduling on pseudowire logical interfaces over a transport logical
interface, you must first complete these tasks:
148
Three-level scheduling on pseudowire logical interfaces over a transport logical interface requires you to
apply the traffic-control profiles at both the pseudowire logical interface and the pseudowire transport
logical interface. To configure CoS policies on three-level scheduling on pseudowire logical interfaces over
a transport logical interface:
For three-level scheduling the hierarchical scheduler must be set to implicit-hierarchy.
[edit]
user@host#set hierarchical-scheduler implicit-hierarchy
2. Specify the traffic-control profile to use on the pseudowire logical interface.
3. Specify the traffic-control profile to use on the pseudowire transport logical interface.
149
6. Apply the rewrite rule and classifier to the pseudowire interfaces.
For the interface_name parameter, specify the pseudowire device name.


Configuring CoS Three-Level Hierarchical Scheduling for MPLS Pseudowire

Subscriber Interfaces (Logical Interfaces over a Pseudowire Interface Set)
Before configuring three-level scheduling on pseudowire logical interfaces over a pseudowire logical
interface set, you must first complete the following tasks:
150
Three-level scheduling on pseudowire logical interfaces over a pseudowire logical interface set requires
you to apply the traffic-control profiles at both the pseudowire logical interface and the pseudowire logical
interface-set. To configure CoS policies on MPLS pseudowire subscriber interfaces using three-level implicit
hierarchical scheduling:
For three-level scheduling the hierarchical scheduler must be set to implicit-hierarchy.
[edit]
user@host#set hierarchical-scheduler implicit-hierarchy
2. Specify the traffic-control profile to use on the pseudowire logical interfaces.
3. Define a pseudowire logical interface set and configure the traffic-control profile used for the interface
set.
user@host#edit interfaces
user@host#edit output-traffic-control-profile profile-name
151
4. Group the pseudowire logical interfaces in the pseudowire logical interface set.
[edit ]
user@host#edit interfaces
user@host#edit interface ps ps-device-name
7. Apply the rewrite rule and classifier to the pseudowire interfaces.
For the interface_name parameter, specify the ps device name.


152

153
CHAPTER 6
Configuring Hierarchical Scheduling for L2TP
IN THIS CHAPTER
Configuring an Inline Service Interface for L2TP LNS | 159
CoS for L2TP LAC Subscriber Interfaces Overview
IN THIS SECTION
Traffic from LAC to LNS | 154
LAC Tunnels: Traffic from LNS to LAC | 155

154
You can apply CoS to the Layer 2 Tunnel Protocol (L2TP) access concentrator (LAC) component.
In Layer 2 Tunnel Protocol (L2TP) configurations, IP and L2TP headers are added to packets arriving at a
PPP subscriber interface on the L2TP access concentrator (LAC) before being tunneled to the L2TP network
server (LNS). You can manage the IP header by configuring classifiers and rewrite-rules that transfer the
ToS (Type of Service) value or the 802.1p value from the inner IP header to the outer IP header of the L2TP
packet.
Figure 18 on page 154 shows the classifier and rewrite rules that you can configure from the LAC to the
LNS, and from the LNS to the LAC.
Figure 18: CoS Configuration for L2TP LAC Topology
RADIUS
server
CLEC network
ISP network
PPP connection LNS

LAC
PC
Classify (Layer 2 and Layer 3) and Rewrite (Layer 2)

g017488
Classify and Rewrite (Layer 2 and Layer 3)
Traffic from LAC to LNS
To set the ToS value or the 802.1p value on the inner IP header, you can configure both fixed and behavior
aggregate (BA) classifiers for subscribers at Layer 2 or Layer 3 of the network.
Table 17 on page 154 lists the configuration options for applying classifiers to a subscriber interface on an
ingress LAC tunnel.
Table 17: Ingress LAC Tunnel Classifier Options
Classifier Subscriber Interface
Fixed Either of the following:
• PPP interface
• Underlying VLAN interface
Layer 2 Either of the following:
• PPP interface
• Underlying VLAN interface
Layer 3 Family of PPP interfaces

155
You cannot configure a Layer 2 and fixed classifier together.
The behavior of the Layer 2 and Layer 3 classifiers depends on the configuration. For example, a Layer 3
classifier for a family of PPP interfaces overrides a Layer 2 classifier configured at the PPP interface, except
for the unknown packets and control packets.
If you do not configure a classifier for Layer 2, the system applies the default Layer 3 classifier so that
tunneled and terminated subscribers have the same behavior. To prevent unknown packets and control
packets from being discarded, the system assigns them to the best-effort forwarding class.
For egress tunnels, you configure rewrite rules at the PPP interface to set the ToS or 802.1p value of the
outer IP header. Rewrite rules are applied accordingly to the forwarding class, packet loss priority (PLP),
and code point.
LAC Tunnels: Traffic from LNS to LAC
On a LAC, mapping the inner IP header to the outer IP header of the L2TP packet depends on the classifier
and rewrite-rule configurations. For example, Table 18 on page 155 lists the values for the classifier and
rewrite rules for a VLAN interface. For assured forwarding, the inner 802.1p value (ob001) is classified
with the assured-forwarding class and low loss priority at the ingress interface. Based on the
assured-forwarding class and low loss priority in the rewrite rule, the ToS value in the outer IP header is
set to ob001.
Table 18: Sample Result for the Classifier and Rewrite Rules for a VLAN Interface
Inner .1p Value Forwarding Class Loss Priority Code Point Outer ToS Value
ob000 best-effort low 000 ob000
ob001 assured-forwarding low 001 ob001
ob101 expedited-forwarding low 101 ob101
ob111 network-control low 11 ob111

156
Configuring Dynamic CoS for an L2TP LAC Tunnel
In L2TP configurations, IP and L2TP headers are added to packets arriving at a PPP subscriber interface
on the LAC before being tunneled to the L2TP network server (LNS).
Classifiers and rewrite rules enable you to properly transfer the ToS (Type of Service) value or the 802.1p
value from the inner IP header to the outer IP header of the L2TP packet.
Before you begin, configure the L2TP LAC. See Configuring an L2TP LAC.
To manage the IP header values for a LAC tunnel:
1. Configure the classifier for the inner tunnel.
a. Define the fixed or behavior aggregate (BA) classifier.
• To configure a fixed classifier:
[edit class-of-service interfaces interface-name unit logical-unit-number]

user@host# set forwarding-class class-name
• To configure a BA classifier:
user@host#set classifiers (ieee-802.1 | inet-precedence) classifier-name forwarding-class class-name
loss-priority level code-points [ aliases ] [ bit-patterns]
b. Apply the classifier to the Layer 2 interface or Layer 3 interface. For Layer 2, you can apply the
classifier at the PPP interface or an underlying VLAN interface. For Layer 3, you can apply classifiers
to a family of PPP interfaces.
• To apply the classifier for the IEEE 802.1p value:
[edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-number

classifiers]
user@host# set ieee-802.1 (classifier-name | default) vlan-tag (inner | outer)
• To apply the classifier for the ToS value:

classifiers]
user@host# set inet-precedence (classifier-name | default)
2. Configure the rewrite rule for the egress tunnel.
a. Configure the rewrite rule with the forwarding class and the loss priority value.
157
user@host# set rewrite-rules (ieee-802.1 | inet-precedence) rewrite-name forwarding-class class-name
loss-priority level code-point (alias | bits)
b. Apply the rewrite rule to the PPP interface for which the L2TP tunnel is configured.
• To apply the rewrite-rule for the IEEE 802.1p value:

rewrite-rules]
user@host# set ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner)
• To apply the rewrite rule for the ToS value:

rewrite-rules]
user@host# set inet-precedence (rewrite-name | default)

CoS for L2TP LNS Inline Services Overview
IN THIS SECTION
Guidelines for Applying CoS to the LNS | 158
Hardware Requirements for Inline Services on the LNS | 158

158
You can apply hierarchical scheduling and per-session shaping to Layer 2 Tunnel Protocol (L2TP) network
server (LNS) inline services using a static or dynamic CoS configuration.
This feature is supported on MIC and MPC interfaces on MX240, MX480, and MX960 routers.
Guidelines for Applying CoS to the LNS
In L2TP configurations, IP, UDP, and L2TP headers are added to packets arriving at a PPP subscriber
interface on the L2TP access concentrator (LAC) before being tunneled to the LNS.
When a service interface is configured for an L2TP LNS session, it has an inner IP header and an outer IP
header. You can configure CoS for an LNS session that corresponds to the inner IP header only. The outer
IP header is used for L2TP tunnel processing only.
However, we recommend that you configure classifiers and rewrite-rules to transfer the ToS (type of
service) value from the inner IP header to the outer IP header of the L2TP packet.
Figure 19 on page 158 shows the classifier and rewrite rules that you can configure on an LNS inline service.
Figure 19: Processing of CoS Parameters in an L2TP LNS Inline Service
Egress tunnel (from LAC to Uplink)
Fixed or BA Multifield
IP/UDP/L2TP decapsulation
classification classification
LAC
peer Core / Internet
interface
Multifield
Shaping IP/UDP/L2TP capsulation Rewrite rule
classification
g017575
Ingress tunnel (from Uplink to LAC)
By default, the shaping calculation on the service interface includes the L2TP encapsulation. If necessary,
you can configure additional adjustments for downstream ATM traffic from the LAC or differences in Layer
2 protocols.
Hardware Requirements for Inline Services on the LNS
Hierarchical scheduling for L2TP LNS inline services is supported on MIC and MPC interfaces only. The
services that you can configure depend on the hardware combination. Table 19 on page 159 lists the
supported inline services and peer interfaces for each MIC and MPC combination.
159
Table 19: Hardware Requirements for L2TP LNS Inline Services
Inline Service Support–With Inline Service Support–Without

MPC Module Per-Session Shaping Per-Session Shaping
MPC2E-3D-NG No Yes
MPC2E-3D-NG-Q Yes Yes
MX80
MPC-3D-16XGE-SFPP No No
Configuring Static CoS for an L2TP LNS Inline Service

Configuring an Inline Service Interface for L2TP LNS
The inline service interface is a virtual physical service interface that resides on the Packet Forwarding
Engine. This si interface, referred to as an anchor interface, makes it possible to provide L2TP services
without a special services PIC. The inline service interface is supported only by MPCs on MX Series routers.
Four inline service interfaces are configurable per MPC-occupied chassis slot.
You can maximize the number of sessions that can be shaped in one service interface by setting the
maximum number of hierarchy levels to two. In this case, each LNS session consumes one L3 node in the
scheduler hierarchy for shaping.
If you do not specify the number of levels (two is the only option), then the number of LNS sessions that
can be shaped on the service interface is limited to the number of L2 nodes, or 4096 sessions. Additional
sessions still come up, but they are not shaped.
To configure an inline service interface:
1. Access the service interface.
[edit interfaces]
user@host# edit si-slot/pic/port
160
2. (Optional; for per-session shaping only) Enable the inline service interface for hierarchical schedulers
and limit the number of scheduler levels to two.
[edit interfaces si-slot/pic/port]

user@host# set hierarchical-scheduler maximum-hierarchy-levels 2
3. (Optional; for per-session shaping only) Configure services encapsulation for inline service interface.

user@host# set encapsulation generic-services
4. Configure the IPv4 family on the reserved unit 0 logical interface.

user@host# set unit 0 family inet
Configuring Dynamic CoS for an L2TP LNS Inline Service
You can configure hierarchical scheduling for an L2TP LNS inline service and manage the IP header values
using rewrite rules and classifiers.
Before you begin, configure the L2TP LNS inline service interface. See Configuring an L2TP LNS with Inline
Service Interfaces.
To configure CoS for an L2TP LNS inline service in a dynamic profile:
1. Configure the hierarchical scheduler for the service interface (si) interface.
[edit interfaces si-fpc/port/pic ]

user@host# set hierarchical-scheduler maximum-hierarchy-levels 2
BEST PRACTICE: To enable Level 3 nodes in the LNS scheduler hierarchy and to provide
better scaling, we recommend that you also specify a maximum of two hierarchy levels.
2. Configure the LNS to reflect the IP ToS value in the inner IP header to the outer IP header.
161
[edit services l2tp tunnel-group name]

user@host# set tos-reflect
3. Configure the classifier for egress traffic from the LAC.
a. Define the fixed or behavior aggregate (BA) classifier.
• To configure a fixed classifier:

user@host# set forwarding-class class-name
• To configure a BA classifier:
user@host# set classifiers (dscp | dscp-ipv6 | inet-precedence) classifier-name forwarding-class class-name
loss-priority level code-points [ aliases ] [ bit-patterns]
b. Apply the classifier to the service interface.
• To apply the classifier for the DSCP or DSCP IPv6 value:

classifiers]
user@host# set dscp (classifier-name | default)
user@host# set dscp-ipv6 (classifier-name | default)
• To apply the classifier for the ToS value:

classifiers]
user@host# set inet-precedence (classifier-name | default)
4. Configure and apply a rewrite-rule to ingress traffic to the LAC:
a. Configure the rewrite rule with the forwarding class and the loss priority value.
user@host# set rewrite-rules (dscp | dscp-ipv6 | inet-precedence) rewrite-name forwarding-class class-name
loss-priority level code-point (alias | bits)
b. Apply the rewrite rule to the service interface.
• To apply the rewrite rule for the DSCP or DSCP IPv6 value:
162

rewrite-rules]
user@host# setdscp (rewrite-name | default)
user@host# set dscp-ipv6 (rewrite-name | default)
• To apply the rewrite rule for the ToS value:

rewrite-rules]
user@host# set inet-precedence (rewrite-name | default)
5. (Optional) Configure additional adjustments for downstream ATM traffic.
By default, the shaping calculation on the service interface includes the L2TP encapsulation. If necessary,
you can configure additional adjustments for downstream ATM traffic from the LAC or differences in
Layer 2 protocols.
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name]

user@host# set overhead-accounting (frame-mode | cell-mode | $junos-cos-shaping-mode) <bytes (byte-value
| $junos-cos-byte-adjust)
6. Apply the traffic-control profile.
[edit dynamic-profiles profile-name class-of-service interfaces $junos-interface-ifd-name unit

$junos-interface-unit]
user@host# set output-traffic-control-profile profile-name

Example: Configuring an L2TP LNS
Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates
163
CHAPTER 7
Preventing Bandwidth Contention on Subscriber

Interfaces
IN THIS CHAPTER
Disabling Hierarchical Bandwidth Adjustment for Subscriber Interfaces with Reverse-OIF Mapping | 179
Hierarchical CoS Shaping-Rate Adjustments Overview
This overview describes how MX Series 5G Universal Routing Platforms installed in a subscriber access
network can adjust hierarchical class-of-service (CoS) parameters to prevent bandwidth contention at
subscriber interfaces.
Hierarchical CoS is supported only for subscriber interfaces on Enhanced Queueing (EQ) DPCs or MPC
interfaces operating in hierarchical scheduler mode.
The characteristics of voice, data, and video applications vary widely in their requirements for traffic
throughput, bandwidth management, delay and jitter tolerance, and buffer depth. To prevent bandwidth
contention at subscriber interfaces, you can configure applications such as ANCP and Multicast to perform
real-time adjustments to the shaping rate configured for subscriber interfaces for residential gateways.
Enabling shaping-rate adjustments on the router can prevent bandwidth contention at the interface from
causing degradation of the subscriber’s voice, data, or video services.
164
Types of Shaping-Rate Adjustments
The ANCP application supports absolute adjustments to a specific shaping-rate value. You can configure
ANCP to communicate the subscriber local loop speed to the MX Series router, which in turn throttles
traffic destined to the associated subscriber interface so that it matches the subscriber local loop speed.
ANCP acquires subscriber line rate information from DSLAMs and then communicates this data transmission
rate for use with CoS.
The OIF mapping and reverse OIF mapping multicast applications support delta adjustments that increase
or decrease the current shaping rate by a certain value. The system adjusts traffic destined to the subscriber
using reverse OIF mapping enabled on a specified multicast interface. Reverse OIF mapping is used to
determine the subscriber VLAN interface and the multicast traffic bandwidth on the interface.
Levels of Shaping-Rate Adjustments
Both absolute and delta adjustments are made to a subscriber’s aggregate shaping rate on a level 3 scheduler
node.
Adjustments that occur on the scheduler node can also impact the shaping rates for all queues. This
adjustment can be undesirable for service providers who want to provide a premium level of service on
specific queues.
For delta-based adjustments by multicast applications, you can control the distribution of shaping rates
among queues by assigning the percentage of adjustment allowed for each queue. In addition, you can set
a minimum adjusted shaping rate for each queue.
Figure 20 on page 164 shows a sample multicast network with shaping rates adjusted at the scheduler node
level. The shaping rate is reduced by 4 Mbps (from 41 Mbps to 37 Mbps) at the scheduler node for
subscriber interface 1, which reduces the rates of both the best effort and video on demand (VoD) service
queues.
Figure 20: Scheduler Node and Queues with Adjusted Shaping Rates
Queues Level 3 (Logical interface) Level 2 Level 1 (Gigabit Ethernet port)
BE: Shaping rate 5M Shaping rate: 37M

Subscriber interface 1
VoD: Shaping rate 38M
BE: Shaping rate 5M

Subscriber interface 2 Scheduler node GE port
g017580
IPTV Multicast VLAN

4 Mbps of multicast destined to subscriber interface 1
Figure 21 on page 165 shows the same network with queue-based adjustments enabled for the best-effort
queue on subscriber 1. The shaping rate of the best-effort queue is reduced by 4 Mbps (from 5 Mbps to
1 Mbps). The VoD service queue is not affected.
165
Figure 21: Queue with Adjusted Shaping Rate
Queues Level 3 (Logical interface) Level 2 Level 1 (Gigabit Ethernet port)
BE: Shaping rate 1M Shaping rate: 41M

Subscriber interface 1
BE: Shaping rate 5M

Subscriber interface 2 Scheduler node GE port
g017576
IPTV Multicast VLAN
4 Mbps of multicast destined to subscriber interface 1
Disabling Hierarchical Bandwidth Adjustment for Subscriber Interfaces with Reverse-OIF Mapping | 179
Shaping Rate Adjustments for Subscriber Local Loops Overview
This overview describes how an MX Series 5G Universal Routing Platform installed as an edge router can
adjust hierarchical CoS policy for subscriber interfaces for subscriber local loops. You can configure the
router to throttle the traffic sent to subscriber local loops so that the traffic does not exceed the current
data transmission rate of those lines. This feature ensures that changes to subscriber local loop speeds do
not cause bandwidth contention at the subscriber’s residential gateway.
In a typical subscriber access network, traffic destined to a subscriber is delivered from the access network,
through an edge router, to a DSLAM. The DSLAM multiplexes subscriber traffic through a DSL, also known
as a local loop, to the subscriber’s residential gateway. When line noise or cross talk in a subcarrier causes
the error rate on a DSL to exceed a certain threshold, the DSLAM can adapt itself by lowering the data
transmission rate to that carrier device. A lower data transmission rate is less susceptible to induced errors.
You can configure an MX Series router to adjust the configured shaping rates on scheduler nodes for
subscriber interfaces that represent subscriber local loops. Whenever a DSLAM resynchronizes a subscriber
local loop speed, the router adjusts the configured shaping rate for that line so that the aggregate egress
traffic to those subscribers is shaped to the local loop speed before the traffic reaches the DSLAM. Unless
the maximum amount of bandwidth allocated to the subscriber interface on the router is throttled to the
local loop speed, bandwidth contention can occur at the subscriber’s residential gateway, which can cause
166
the DSLAM to drop packets. This type of shaping-rate adjustment requires the topology discovery and
traffic-monitoring features of the Access Node Control Protocol (ANCP).
You can enable ANCP to communicate the subscriber local loop speed to CoS, which in turn throttles
traffic destined to the associated subscriber interface so that it matches the subscriber local loop speed.
The ANCP agent acquires unadjusted (net) subscriber line rate information from DSLAMs and then
communicates this data transmission rate for use with CoS. You can also configure percentage and byte
adjustments that the ANCP agent can make to the received net data rate for frame-mode DSL types before
communicating the adjusted rate and overhead to CoS.

For more information about the ANCP protocol, see the ANCP and the ANCP Agent Overview.
Guidelines for Configuring Shaping-Rate Adjustments for Subscriber Local

Loops
These guidelines apply to configuring an MX Series 5G Universal Routing Platform installed as an edge
router to adjust the configured shaping rates on scheduler nodes for subscriber interfaces that represent
subscriber local loops. This shaping-rate feature uses the topology discovery and traffic-monitoring features
of ANCP.
When you enhance hierarchical CoS policy by configuring ANCP-driven shaping-rate adjustments, consider
the following guidelines:
• Shaping-rate adjustments are supported only for subscriber local loops that terminate at DSLAMs that
you have configured as ANCP neighbors of the MX Series router.
• Shaping-rate adjustments are supported only for scheduler nodes for which you have configured an
initial shaping rate by including the shaping-rate statement in a traffic-control profile applied to the
scheduler node. Specify the initial shaping rate as a peak rate, in bits per second (bps), and not as a
percentage. Other methods of configuring a shaping rate are not supported with this feature.
• Shaping-rate adjustments are supported only for scheduler nodes that are static logical interface sets
that you have configured to operate at Level 3 of the scheduler hierarchy on the router. If an interface
167
set is configured with a logical interface (such as unit 0) and queue, then the interface set is an internal
scheduler node (as opposed to a root node or a leaf node) at Level 2 of the hierarchy. However, if there
are no traffic-control profiles are configured on logical interfaces in an interface set, then the interface
set is an internal scheduler node at Level 3 of the hierarchy.
• Shaping-rate adjustments are supported only for subscriber interfaces over physical interfaces that you
have configured to operate in hierarchical scheduler mode.
• After shaping-rate adjustments are enabled and the router has performed shaping-rate adjustments on
a scheduler node, you can configure a new shaping rate by including the shaping-rate statement in a
traffic-control profile and then applying that profile to that scheduler node. However, this new
shaping-rate value does not immediately result in shaping traffic at the new rate. The scheduler node
continues to be shaped at rate set by ANCP. Only when the ANCP shaping-rate adjustment feature is
disabled is the scheduler node shaped at the newly configured shaping-rate.
• The Layer 2 Tunneling Protocol (L2TP) is often used to carry traffic securely between an L2TP Network
Server (LNS) and an L2TP Access Concentrator (LAC). The QoS adjustment feature supports the shaping
overhead options that you can use to add a specified number of bytes to the actual packet length when
determining shaped session packet length. ANCP shaping-rate adjustments are not supported for ingress
traffic, only for egress traffic. To configure the number of bytes to add to the packet at the egress side
of the tunnel, include the egress-shaping-overhead and mode statements at the [edit chassis fpc
slot-number pic pic-number traffic-manager] hierarchy level. Use the shaping overhead options if you
need to account for encapsulation overhead.
For more information about the ANCP protocol, see the ANCP and the ANCP Agent Overview.

168
Configuring the Minimum Adjusted Shaping Rate on Scheduler Nodes for

Subscribers
IN THIS SECTION
Overview | 168
Configuring a Static Minimum Adjusted Shaping Rate on Scheduler Nodes | 168
Overview
Absolute adjustments and delta adjustments are performed at the scheduler node level. You can configure
a minimum adjusted shaping rate at the scheduler node level using static or dynamic CoS parameters.
This feature is supported for adjustments performed by the ANCP and multicast applications.
BEST PRACTICE: For multicast traffic, you can configure a minimum adjusted shaping rate at
the queue level. We recommend that you configure the minimum adjusted value at the scheduler
node or the queue, but not both.
When you configure a minimum adjusted value for a node and for a scheduler that is referenced
by a scheduler map in the same traffic-control-profile, the system uses the minimum value from
the scheduler.
Configuring a Static Minimum Adjusted Shaping Rate on Scheduler Nodes
To apply a minimum adjusted shaping rate for a scheduler node:
• Configure the adjust-minimum statement for the static traffic-control profile.
[edit class-of-service traffic-control-profiles profile-name]

user@host# set adjust-minimum rate
SEE ALSO
169

Configuring Traffic Scheduling and Shaping for Subscriber Access
Configuring a Dynamic Minimum Adjusted Shaping Rate on Scheduler Nodes
To apply a minimum adjusted shaping rate for a scheduler node:
• Configure the adjust-minimum statement for the dynamic traffic-control profile.

SEE ALSO


Configuring Shaping-Rate Adjustments on Queues
IN THIS SECTION
Overview | 170
Configuring a Static Shaping-Rate Adjustment for Queues | 170

170
Overview
By default, the multicast application adjusts the shaping rates at the scheduler node level. This adjustment
also impacts the shaping rates for all queues, which can be undesirable for service providers who want to
provide a premium level of service on specific queues.
For multicast applications, you can control the distribution of shaping rates among queues by assigning
the percentage of adjustment allowed for each queue. In addition, you can set a minimum adjusted shaping
rate for each queue.
This feature is supported for adjustments performed by the multicast application.
BEST PRACTICE: We recommend that you configure the minimum adjusted value at the scheduler
node or the queue, but not both.
When you configure a minimum adjusted value for a node and for a scheduler that is referenced
by a scheduler map in the same traffic-control-profile, the system uses the minimum value from
the scheduler.
Configuring a Static Shaping-Rate Adjustment for Queues
To configure adjustment parameters for a queue:
1. Configure the percentage of adjustment for the shaping rate.
[edit class-of-service schedulers scheduler-name]

user@host# set adjust-percent percentage
2. Configure the minimum adjusted value for the shaping rate.
Do one of the following:
• Configure the minimum adjusted value for the queue.

• Configure the minimum adjusted value for the node.
[edit class-of-service traffic-control-profile profile-name]

171
BEST PRACTICE: Ensure that the minimum adjusted value that you configure does not exceed
the shaping rate and is not lower than the configured transmit rate.
SEE ALSO

Configuring a Dynamic Shaping-Rate Adjustment for Queues
To configure adjustment parameters for a queue in a dynamic profile:
1. Configure the percentage of adjustment for the shaping rate.
[edit dynamic-profiles profile-name class-of-service schedulers scheduler-name]

user@host# set adjust-percent percentage
2. Configure the minimum adjusted value for the shaping rate.
Do one of the following:
• Configure the minimum adjusted value for the queue.
[edit dynamic-profiles profile-name class-of-service schedulers scheduler-name]

user@host# set adjust-minimum (rate | $junos-cos-adjust-minimum)
• Configure the minimum adjusted value for the node.
[edit dynamic-profiles profile-name class-of-service traffic-control-profile profile-name]

BEST PRACTICE: Ensure that the minimum adjusted value that you configure does not exceed
the shaping rate and is not lower than the configured transmit rate.
172
SEE ALSO


Enabling Shaping-Rate Adjustments for Subscriber Local Loops
IN THIS SECTION
Configuring Static Logical Interface Sets to Serve as CoS Hierarchical Scheduler Nodes for Subscriber
Loops | 173
Configuring the Logical Interfaces That Compose the Static Logical Interface Sets | 174
Configuring Hierarchical CoS on the Static Logical Interface Sets That Serve as Hierarchical Scheduler Nodes
for Subscriber Local Loops | 174
Configuring ANCP Functionality That Supports and Drives Shaping-Rate Adjustments for Subscriber Local
Loops | 177
You can enhance a CoS implementation by enabling an MX Series 5G Universal Routing Platform to adjust
the hierarchical CoS policy shaping rate configured for static interface sets that consist of two or more
VLANs and represent subscriber local loops. Whenever the digital subscriber line access multiplexer
(DSLAM) resynchronizes its data transmission rate to a digital subscriber line (DSL), the router adjusts the
shaping rate for the associated subscriber interface so that the maximum bandwidth allocation cannot
exceed the current data rate for the associated subscriber local loop. This feature ensures that data
transmission rate adjustments by the DSLAM do not cause bandwidth contention at the subscriber’s
residential gateway.
This topic includes the following tasks:

173
Configuring Static Logical Interface Sets to Serve as CoS Hierarchical Scheduler Nodes for
Subscriber Loops
To configure a logical interface set, begin by including the interface-set statement with the interface-set-name
option at the [edit interfaces] hierarchy level.
An interface set is composed of two or more logical interfaces on the same physical interface. Each logical
interface in an interface set corresponds to an individual subscriber service, such as voice, video, or data.
To specify either a list of logical unit numbers or the single outer VLAN tag used to identify the logical
interfaces that compose the interface set, include statements at the [edit interfaces interface-set
interface-set-name] hierarchy level:
• For an interface set composed of a list of logical interfaces identified by an inner VLAN tag on Ethernet
frames (called the customer VLAN, or C-VLAN, tag), you must specify each logical interface by including
the unit statement with the logical-unit-number option.
[edit]
interfaces {
interface ethernet-interface-name { # EQ DPC port
...
}
...
}
}
• For an interface set composed of a set of VLANs grouped at the DSLAM and identified by the same
service VLAN (S-VLAN) tag), you must specify the S-VLAN tag as the outer VLAN tag for each VLAN
by including the vlan-tags-outer statement with the vlan-tag option.
[edit]
interfaces {
interface ethernet-interface-name { # EQ DPC port
vlan-tags-outer vlan-tag; # Identify the DSLAM
}
...
}
}
For more information, see “Configuring Hierarchical Schedulers for CoS” on page 13.
174
Configuring the Logical Interfaces That Compose the Static Logical Interface Sets
Each underlying physical interface must be configured to operate in hierarchical scheduler mode and to
support stacked VLAN tagging on all logical interfaces. To configure, include the hierarchical-scheduler
statement and the stacked-vlan-tagging statement at the [edit interfaces ethernet-interface-name] hierarchy
level.
To associate the individual logical interfaces of an interface set with specific subscriber services provided
by the subscriber local loop, bind an S-VLAN tag and a C-VLAN tag to each logical interface that belongs
to a scheduler node that represents a subscriber local loop. Ethernet frames sent from the logical interfaces
contain an outer VLAN tag that identifies a DSLAM and an inner VLAN tag that identifies a subscriber port
on the DSLAM. To configure, include the vlan-tags statement at each logical interface:
[edit]
interfaces {
ethernet-interface-name { # EQ DPC port underlying an interface set
stacked-vlan-tagging; # Support 802.1Q VLAN dual-tagged frames
unit logical-unit-number { # Bind S-VLAN and C-VLAN tags to logical interface
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
}
...
}
}
For more information, see 802.1Q VLANs Overview.
Configuring Hierarchical CoS on the Static Logical Interface Sets That Serve as Hierarchical
Scheduler Nodes for Subscriber Local Loops
To configure hierarchical CoS on the static logical interface set that serves as the hierarchical scheduler
node for a subscriber local loop:
1. For each scheduler node that represents a subscriber local loop, configure an initial shaping rate.
NOTE: The CoS shaping-rate feature is supported only for scheduler nodes with a configured
shaping rate. The initial shaping rate must be configured by applying a traffic-control profile
that includes the shaping-rate statement. Specify the initial shaping rate as a peak rate, in
bits per second (bps), and not as a percentage. Other methods of configuring a shaping rate
are not supported with this feature.
175
• To enable traffic heading downstream (from the router to the DSLAM) to be gathered into an interface
set, include the interface-set statement and define the logical interface set name as the
interface-set-name option at the [edit class-of-service interfaces] hierarchy level.
• To apply output traffic scheduling and shaping parameters at the logical interface set level (rather
than at the logical unit level), include the output-traffic-control-profile statement and specify the
name of a traffic-control profile as the profile-name option at the [edit class-of-service interfaces
interface-set interface-set-name] hierarchy level.
To configure, include the following statements:
interfaces { # Configure interface-specific CoS for incoming packets

interface-set interface-set-name { # Configure a hierarchical scheduler
output-traffic-control-profile tc-profile-name; # Level 3 scheduler node
}
...
}
traffic-control-profiles { # Define traffic-control profiles
tc-profile-name { # Specify a scheduler map and traffic-shaping parameters
scheduler-map map-name;
shaping-rate rate; # This is the “configured shaping rate”
guaranteed-rate (percent percentage | rate);
delay-buffer-rate (percent percentage | rate);
}
...
}
You can include the statements at the following hierarchy levels:
• [edit class-of-service]
• [edit dynamic-profiles profile-name class-of-service]
2. Configure the scheduler maps referenced in the traffic-control profiles applied to the interface sets,
the schedulers referenced in those scheduler maps, and the drop profiles referenced in those schedulers.
• A scheduler map establishes the traffic output queues (forwarding classes) for a scheduler node and
associates each queue with a specific scheduler map.
• A scheduler defines queue properties (transmit rate, buffer size, priority, and drop profile) that specify
how traffic is treated in the output queue.
• A drop profile specifies how aggressively the MX Series router drops packets that are managed by
a particular scheduler by defining either a segmented or interpolated graph that maps output queue
fullness to packet drop probability.
176
To configure, include the statements at the static [edit class-of-service] hierarchy level:
[edit]
class-of-service {
scheduler-maps { # Assign queuing characteristics to output queues
map-name { # Map output queues to
forwarding-class class-name scheduler scheduler-name;
...
}
...
}
schedulers { # Define queuing characteristics
scheduler-name { # Specify queuing and buffer management
transmit-rate transmit-rate-option;
buffer-size buffer-size-option;
priority priority-level;
drop-profile-map loss-priority loss-priority-option protocol any drop-profile drop-profile-name;
...
}
}
drop-profiles { # Define random early detection (RED) for the delay buffer
drop-profile–name { # Specify how to drop packets from an output queue
drop-profile-name { # Map a queue fullness to a drop probability
fill-level percentage drop-probability percentage; # Option 1: segmented
fill-level percentage drop-probability percentage;
...
}
interpolate { # Option 2: interpolated
drop-probability [ values ];
fill-level [ values ];
}
}
...
}
}
For more information about configuring scheduler maps, schedulers, and drop profiles, see Mapping CoS
Component Inputs to Outputs.
177
Configuring ANCP Functionality That Supports and Drives Shaping-Rate Adjustments for
Subscriber Local Loops
To configure the Access Node Control Protocol (ANCP) functionality that supports and drives the
shaping-rate adjustments for subscriber local loops:
• Enable the ANCP agent to monitor subscriber local loop rates at the DSLAMs and communicate this
information to CoS.
• For frame-mode DSL types, optionally configure adjustments that are made to the net data rates, the
frame overhead, or both before the ANCP agent reports the values to CoS. Rates are adjusted by a
percentage. Bytes are added to or subtracted from the overhead per frame.
• Configure each DSLAM as an ANCP neighbor of the router so that TCP connections can be established
between the router and each DSLAM.
• Identify the subscriber interface sets whose traffic is monitored and shaped by the ANCP agent, and
associate those interface sets with the corresponding identifiers configured on the access node (DSLAM)
to uniquely identify the subscriber local loops within the access network.
The ANCP agent uses this information to build a mapping of subscribers to subscriber interfaces. When
the ANCP agent receives port management messages from a DSLAM or other access node, it uses the
access identifier contained in the message to determine which hierarchical scheduler node corresponds
to the subscriber.
To configure, include statements at the [edit protocols ancp] hierarchy level:
[edit]
protocols {
ancp {
qos-adjust; # Enable ANCP to monitor and adjust CoS shaping rates
other-bytes bytes; # Specify number of bytes to adjust OTHER access technology rate
other-overhead-adjust percentage; # Specify percentage by which to adjust OTHER access technology
rate
sdsl-bytes bytes; # Specify number of bytes to adjust SDSL rate
sdsl-overhead-adjust percentage; # Specify percentage by which to adjust SDSL rate
vdsl-bytes bytes; # Specify number of bytes to adjust VDSL rate
vdsl-overhead-adjust percentage; # Specify percentage by which to adjust VDSL rate
vdsl2-bytes bytes; # Specify number of bytes to adjust VDSL2 rate
vdsl2-overhead-adjust percentage; # Specify percentage by which to adjust VDSL2 rate
}
neighbor ip-address; # Configure each DSLAM as an ANCP neighbor
...
interfaces { # Identify subscribers for which ANCP can adjust shaping rates
interface-set {
interface-set-name {
178
access-identifier identifier-string; # DSLAM ID for the local loop

}
}
...
}
...
}
...
}
For hardware requirements and configuration guidelines, see Guidelines for Configuring Shaping-Rate
Adjustments for Subscriber Local Loops | 166
Traffic Rate Reporting and Adjustment by the ANCP Agent
Configuring the ANCP Agent to Report Traffic Rates to CoS
Disabling Shaping-Rate Adjustments for Subscriber Local Loops
To disable hierarchical CoS shaping-rate adjustments for subscriber local loops:
• Disable hierarchical CoS traffic-shaping adjustment by ANCP:
[edit protocols ancp]

user@host# delete qos-adjust
Traffic-shaping parameters for all subscriber local loops revert to their current configured values.
179
For hardware requirements and configuration guidelines, see Guidelines for Configuring Shaping-Rate
Adjustments for Subscriber Local Loops | 166
Disabling Hierarchical Bandwidth Adjustment for Subscriber Interfaces

with Reverse-OIF Mapping
You can disable hierarchical bandwidth adjustment for all subscriber interfaces with reverse OIF mapping
enabled on a specified multicast interface. Reverse OIF mapping is used to determine the subscriber VLAN
interface and the multicast traffic bandwidth on the interface.
To disable hierarchical bandwidth adjustment:
1. Specify that you want to access the subscriber interfaces with reverse-OIF mapping enabled.
[edit routing-instances routing-instance routing-options multicast interface interface-name]

user@host# edit reverse-oif-mapping
2. Disable hierarchical bandwidth adjustment for all subscriber interfaces on the interface.
user@host# set no-qos-adjust

Example: Configuring Multicast with Subscriber VLANs
180
Example: Configuring Hierarchical CoS Shaping-Rate Adjustments for

Subscriber Local Loops
This example shows how you can enable shaping-rate adjustments for static logical interface sets that
represent subscriber local loops:
1. Configure static logical interface sets to serve as CoS hierarchical scheduler nodes for subscriber local
loops.
This example uses a single scheduler node that represents two subscriber local loops. The scheduler
node is a static logical interface composed of two logical interfaces. The underlying physical interface
is port 0 on a Gigabit Ethernet EQ MPC in slot 4, PIC 0:
[edit]
interfaces {
interface-set ifset-of-logical-interfaces {
unit 1;
unit 2;
}
}
ge-4/0/0 {
description “access interface ge-4/0/0”;
stacked-vlan-tagging;
unit 1 {
description “DSL type ADSL1 = 0x01”;
proxy-arp;
vlan-tags outer 1 inner 1; # S-VLAN tag is ’1’ and C-VLAN tag is ’1’
family inet { # Specify a secondary loopback address
}
}
unit 2 {
description “DSL type ADSL1 = 0x01”;
proxy-arp;
vlan-tags outer 1 inner 2; # S-VLAN tag is ’1’ and C-VLAN tag is ’2’
family inet { # Specify a secondary loopback address
}
}
}
}
181
2. Begin configuring hierarchical CoS on the static logical interface set that serves as the hierarchical
scheduler node for the group of subscriber local loops.
[edit]
class-of-service {
interfaces {
interface-set ifset-of-logical-interfaces {
output-traffic-control-profile tcp-premium-with-4–queues;
}
}
}
3. Configure the traffic-control profiles that can be applied to the scheduler node:
[edit]
class-of-service {
tcp-basic-rate { # Specify a scheduler map and traffic controls
shaping-rate 10m;
}
tcp-premium-with-4-queues { # Specify a scheduler map and traffic controls
scheduler-map smap-premium-4q;
shaping-rate 20m;
}
}
}
In this example, the tcp-premium-with-4-queues traffic-control profile is applied to the interface set.
The other profile provides a lower shaping rate and no guaranteed rate.
4. Configure the scheduler map smap-premium-4q that is referenced in the traffic-control profile for the
scheduler node:
[edit]
class-of-service {
scheduler-maps { # Define the queues that comprise each scheduler node
smap-premium-4q { # Map each queue in the scheduler node to a scheduler
182

}
}
}
5. Configure the four schedulers (referenced in the scheduler map) that define the four output queues
for the scheduler node:
[edit]
class-of-service {
schedulers { # Define scheduling characteristics of each queue
be_sch { # Transmit rate and buffer management parameters
buffer-size remainder;
priority low;
}
ef_sch { # Transmit rate and buffer management parameters
...
}
af_sch { # Transmit rate and buffer management parameters
...
}
nc_sch { # Transmit rate and buffer management parameters
...
}
}
}
6. Enable ANCP to communicate with the DSLAM to adjust the CoS shaping rate for the scheduler node.
You must enable the ANCP feature for performing CoS traffic shaping adjustments, configure the
DSLAM as an ANCP neighbor, and specify the DSLAM-assigned identifier for the subscriber local loop
represented by the scheduler node Optionally specify byte or percentage adjustments for frame-mode
DSL types.
[edit]
protocols {
ancp {
qos-adjust; # Enable ANCP to adjust CoS shaping rates and specify rate adjustments
sdsl-bytes 30;
sdsl-overhead-adjust 87;
vdsl-bytes 20;
183
vdsl-overhead-adjust 95;
vdsl2-bytes 20;
vdsl2-overhead-adjust 87;
}
neighbor 10.2.3.4; # Configure the DSLAM as an ANCP neighbor
interfaces { # Identify subscribers for which ANCP can adjust shaping rates
interface-set {
ifset-of-logical-interfaces {
access-identifier “dslam port 2/3”; # DSLAM ID for the local loop
}
}
}
}
}
NOTE: If ANCP is not yet enabled, the process starts when you commit a configuration that
contains the protocols ancp stanza.
7. You can display the configured shaping rate and the adjusted shaping rate for each logical interface
set configured for hierarchical CoS, issue the show class-of-service interface-set operational command.

Verifying the Configuration of Shaping-Rate Adjustments for Subscriber

Local Loops
Purpose
Display the configured shaping rate and the adjusted shaping rate for each logical interface set configured
for hierarchical CoS.
184
NOTE: After shaping-rate adjustments are enabled and the router has performed shaping-rate
adjustments on a scheduler node, you can configure a new shaping rate by including the
shaping-rate statement in a traffic-control profile and then applying that profile to that scheduler
node. However, this new shaping-rate value does not immediately result in shaping traffic at the
new rate. The scheduler node continues to be shaped at rate set by ANCP. Only when the ANCP
shaping-rate adjustment feature is disabled is the scheduler node shaped at the newly configured
shaping-rate.
Action
Issue the show class-of-service interface-set operational command.
Verifying the Configuration of ANCP for Shaping-Rate Adjustments

Purpose
Use to display or clear information about the ANCP configuration for shaping-rate adjustments.
Action
• To display ANCP neighbor information, issue the show ancp neighbor operational command.
• To clear ANCP neighbors, issue the clear ancp neighbor operational command.
• To display ANCP subscriber information, issue the show ancp subscriber operational command.
• To display ANCP class-of-service information, issue the show ancp cos operational command.
If ANCP is not yet enabled, the process starts when you commit a configuration that contains the protocols
ancp stanza.
ANCP and the ANCP Agent Overview

Configuring the ANCP Agent
185
Using Hierarchical CoS to Adjust Shaping Rates Based on Multicast Traffic
For service providers that are using interface sets to deliver services such as voice and data and multicast
VLANs (M-VLANs) to deliver broadcast television, you can set up CoS so that when a subscriber begins
receiving multicast traffic, the shaping rate of the subscriber interface is adjusted to account for the
multicast traffic. You can also set up the class of service (CoS) multicast adjustment to be propagated from
the subscriber interface to the interface set, which is the parent in the scheduler hierarchy. This feature
prevents oversubscription of the multicast replicator, such as a PON, which can result in dropped traffic
and service disruption.
For broadcast television, instead of transporting separate video streams from the source to each subscriber
receiving the same stream, the broadband network gateway (BNG) uses M-VLANs to send one stream to
the access node. The access node, such as an Optical Line Terminal (OLT) or a DSLAM, replicates the video
stream for each subscriber that is currently watching a particular television channel. In this scenario,
M-VLANs are used to stream television and interface sets are used to manage traffic to the access node.
An interface set contains an interface for each subscriber that is attached to the access node. See
Figure 22 on page 185 for a typical broadcast television network topology.
Figure 22: Typical Broadcast Television Network Topology.
Voice
Video RG1 PON1
Data
Sub 1 VLAN
Sub 2 VLAN
Sub 3 VLAN Access

Voice Network
Video RG2 PON2 OLT BNG
Data
M-VLAN
Voice
Video RG3 PON3
Data
BNG Broadband Network GW

OLT Optical Line Terminal
g043724
PON Passive Optical Network

RG Residential Gateway
When a subscriber begins watching a television channel, the BNG detects that the subscriber has joined
a multicast group and has begun receiving traffic from an M-VLAN. The BNG adjusts traffic shaping on
the subscriber interface to account for the bandwidth that the multicast traffic is using. For example, if a
subscriber begins watching a television channel, the BNG reduces the bandwidth on the subscriber interface
to account for the bandwidth being used by the multicast traffic. If you set up CoS to propagate the reduced
bandwidth of the subscriber interface to the interface set, the interface set’s shaping rate is also reduced.
186
The BNG uses CoS adjustments based on three-level hierarchical CoS scheduling to implement this feature.
Level 2 in the scheduler hierarchy is the interface set, and level 3 is the logical interface. To use this feature,
you configure traffic-control profiles for logical interfaces (level 3) to adjust the parent interface set (level
2).
You can set up CoS adjustments to the parent interface set to happen once for each broadcast television
channel being streamed over the M-VLAN by including the qos-adjust-hierarchical interface-set at the
[edit dynamic-profiles dynamic-profile-name access-cac interface $junos-interface-name] hierarchy. For
example:
user@host# set dynamic-profiles dynamic-profile-name access-cac interface $junos-interface-name

qos-adjust-hierarchical interface-set
To illustrate the benefit of this feature, consider two scenarios from Figure 23 on page 186, which shows
a possible subscriber scheduler hierarchy with M-VLANs.
Figure 23: Typical Subscriber Scheduler Hierarchy with M-VLANs
Queues Level 3 node Level 2 node Level 1 node

(RG) PON port (OLT port)
RG1 Q0
RG1 Q1
RG1
RG1 Q2
RG1 Q3
Shaping rate Shaping rate
1 Gbps 2.4 Gbps
RG2 Q0
RG2 Q1
RG2 PON2
RG2 Q2
RG2 Q3
Shaping rate
1 Gbps
RG3 Q0
RG3 Q1
RG3 OLT
RG3 Q2
RG3 Q3
MC Q0
MC Q1
M-VLAN
MC Q2
MC Q3
M-VLAN Multicast VLAN

OLT Optical Line Terminal
g043723
PON Passive Optical Network

RG Residential Gateway
187
Scenario 1
Each of 32 subscribers on PON2 are consuming as much data as they can. Each subscriber receives (2.4
Gbps / 32 subscribers) = 75Mbps. Subscriber 1 on PON2 starts watching a 120Mbps multicast video
stream. Each subscriber receives (2.4Gbps – 120Mbps) / 32 subscribers = 71.25Mbps of data. Subscriber
1 receives 120Mbps of video, and 71.25Mbps of data. Then Subscriber 2 on PON2 starts watching a
different 120Mbps multicast video stream. Each subscriber then receives (2.4Gbps – 240Mbps) / 32
subscribers = 67.5 Mbps of data. Subscribers 1 and 2 receive 120Mbps of video and 67.5Mbps of data.
Final QoS adjustments:
• Subscriber 1’s shaping-rate is reduced by 120Mbps to 880Mbps.
• PON2’s shaping-rate is reduced by 240Mbps to 2.160Gbps, leaving all 32 subscribers to equally share
2.160Gbps – which is 67.5Mbps each.
Scenario 2
Each of 32 subscribers are consuming as much data as they can. Each subscriber receives (2.4 Gbps / 32
subscribers) = 75Mbps. Subscriber 1 on PON2 starts watching a 120Mbps multicast video stream. Each
subscriber then receives (2.4Gbps – 120Mbps) / 32 subscribers = 71.25Mbps of data. Subscriber 1 gets
120Mbps of video, and 71.25Mbps of data. Subscriber 2 on PON2 then starts watching the same 120Mbps
multicast video stream. This is completely serviced. Since this is the same video stream as Subscriber 1 is
watching, and the stream is being replicated at the PON, only one subscriber adjustment is needed. No
additional PON adjustment is needed due to subscriber 2 watching the same 120Mbps multicast video
steam.
Final QoS adjustments:
• PON2’s shaping-rate is reduced by 240Mbps to 2.280Gbps, leaving all 32 subscribers to equally share
2.280Gbps – which is 71.25Mbps each.
When any one of the two subscribers receiving the 120Mbps video stream unsubscribes, the adjustment
for that subscriber is reverted. The other subscriber’s adjustment remains, as does the PON’s adjustment.
When the remaining subscriber unsubscribes the adjustment for that subscriber is reverted, as is the PON’s
adjustment.
188
CHAPTER 8
Configuring Targeted Distribution of Subscribers on

Aggregated Ethernet Interfaces
IN THIS CHAPTER
Providing Accurate Scheduling for a Demux Subscriber Interface of Aggregated Ethernet Links | 191
Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet Interface | 193
Example: Separating Targeted Multicast Traffic for Demux Subscribers on Aggregated Ethernet
Interfaces | 196
Distribution of Demux Subscribers in an Aggregated Ethernet Interface
This topic describes the distribution options available for demux subscriber interfaces over aggregated
Ethernet.
Distribution Models
By default, the system supports hash-based distribution for all subscriber interface types in an aggregated
Ethernet bundle configured without link protection. In this model, traffic for a logical interface can be
distributed over multiple links in the bundle. This model is desirable when there are many flows through
the logical interface and you need to load balance those flows.
Note that if the distribution flows are not even, egress CoS scheduling can be inaccurate. In addition,
scheduler resources are required on every link of the aggregated Ethernet interface. For example, if
subscriber traffic is allocated 10 MB for a triple-play service over four links in a bundle, each of the links
could receive 2.5 MB of traffic. High-density services such as video could be limited by the bandwidth on
one of the links.
189
Targeted distribution enables you to target the egress traffic for an IP or VLAN demux subscriber on a
single member link, using a single scheduler resource. To achieve load balancing over the member links,
the system distributes the subscriber interfaces equally among the links. This enables the subscriber that
is allocated 10 MB to be accurately scheduled as the traffic flows through.
Sample Targeted Distribution Topology
Figure 24 on page 189 displays a sample targeted distribution of subscriber traffic across links in an
aggregated Ethernet interface. A primary and backup link is allocated for each subscriber.
Figure 24: Targeted Subscriber Links
Layer 3 CoS schedulers GE-x.1 GE-y.1 GE-x.2 GE-z.2 GE-y.3 GE-z.3
demux0.1 demux0.2 demux0.3
Remaining Remaining Remaining

Layer 1 CoS schedulers GE-x GE-y GE-z
scheduler scheduler scheduler
AE bundle
The blue Layer 3 scheduler
g017525
represents the primary. Access Node
For example, if link GE-x went down, subscriber 1 can begin forwarding over the backup, which is link
Ge-y. When link GE-y comes back up, subscriber 1 switches back to its primary link, GE-x.
In the event that both GE-x and GE-y go down, subscriber 3 starts forwarding through its backup, GE-z.
Subscriber 1 will have lost its primary and backup links, and will also begin forwarding out the GE-z link.
A new level 3 scheduler is assigned for this subscriber on link GE-z. If there is a momentary lapse between
the time that a new scheduler is allocated and forwarding switches to GE-z, the traffic will be forwarding
through to the remaining scheduler. Subscriber 2 continues to forward through its primarily link, GE-z.
Redundancy and Redistribution Mechanisms
Two types of redundancy are available in the targeted distribution model: link redundancy and module
redundancy.
By default, an aggregated Ethernet interface is enabled with link redundancy. Backup links for a subscriber
are chosen based on the link with the least number of subscribers, which provides redundancy if a link
fails.
The module redundancy option enables you to provide redundancy if a module or a link fails. Backup links
for a subscriber are chosen on a different DPC or MPC from the primary link, based on the link with the
190
least number of subscribers among the links on different modules. You can enable this for the aggregated
Ethernet interface.
When links are removed, affected subscribers are redistributed among the active remaining backup links.
When links are added to the system, no automatic redistribution occurs. New subscribers are assigned to
the links with the fewest subscribers (which are typically the new links).
Considerations and Best Practices
Keep the following guidelines in mind when configuring targeted distribution for demux subscribers:
• You can manage subscribers with both hash-based and targeted distribution models in the same network.
For example, you can allocate subscribers with interface types such as PPPoE with hash-based distribution,
and enable demux subscribers with targeted distribution.
• We recommend that you configure module redundancy to protect against module failures. When module
redundancy is enabled, you can ensure an even distribution of subscribers if you allocate no more than
50 percent of the links on a single DPC or MPC.
• During normal network operations, the system maintains an even balance of subscribers among the links
in a bundle, even as subscribers log in and out. However, if the distribution of a bundle becomes uneven
(for example, when a link goes down and new subscribers are logging in), you can perform a manual
rebalance of the bundle. In addition, you can configure periodic rebalancing of the bundle with a specific
time interval.
• When you anticipate that a link will be down for an extended time, and you want to ensure that backup
links are provisioned for all subscribers, we recommend that you remove the failed link from the bundle.
This forces the affected subscribers to redistribute to other links.
• We recommend that you apply a remaining traffic-control profile to the logical interface to ensure that
minimal scheduling parameters are applied to the remaining subscriber traffic. This provides scheduling
for subscribers that do not have schedulers allocated because they have not been configured or they
have been over-provisioned, or because of scheduler transitions on multiple link failures.
• If you perform a cold restart on the router when it is forwarding active subscribers, the subscriber
interfaces with targeted distribution are assigned to the first links that become available when the system
is initializing so forwarding can begin. To rebalance the system following a cold restart, perform a manual
rebalance of the bundle. In addition, we recommend that you configure Graceful Routing Engine
switchover (GRES) on the router to enable nonstop forwarding during switchover, and avoid performing
cold restarts.
• To ensure appropriate and predictable targeted distribution, you must configure chassis network services
to use enhanced-ip mode.
• Unless specifically separated, multicast traffic egresses in parallel with unicast traffic, sharing the CoS
hierarchy and aggregated Ethernet flow distribution.
191
Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet
Interface | 193
Static or Dynamic Demux Subscriber Interfaces over Aggregated Ethernet Overview
Providing Accurate Scheduling for a Demux Subscriber Interface of

Aggregated Ethernet Links
Unlike VLAN subscriber interfaces, enabling link protection is not required for configuring hierarchical CoS
on demux interfaces. Instead, we recommend that you enable targeted distribution on the demux interface
to provide accurate scheduling for the aggregated Ethernet links.
Before you begin, configure the subscriber interface with aggregated Ethernet:
• For static and dynamic IP demux interfaces, see Configuring a Static or Dynamic IP Demux Subscriber
• For static and dynamic VLAN demux interfaces, see Configuring a Static or Dynamic VLAN Demux Subscriber
To provide accurate scheduling for a demux subscriber interface of aggregated Ethernet links:
1. Enable targeted distribution for the demux interface.
See “Configuring the Distribution Type for Demux Subscribers on Aggregated Ethernet Interfaces” on
page 192.
2. Enable hierarchical scheduling on the link aggregation bundle.
See “Configuring Hierarchical CoS for a Subscriber Interface of Aggregated Ethernet Links” on page 92.
3. (Optional) Enable module redundancy to ensure that CoS resources are provisioned for the aggregated
Ethernet links if a module or a link fails. By default, link redundancy is supported.
See “Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet
Interface” on page 193.
192
4. (Optional) Configure rebalancing periodically or manually for the subscribers. See “Configuring
Rebalancing of Demux Subscribers in an Aggregated Ethernet Interface” on page 194.
5. Attach static or dynamic traffic shaping and scheduling parameters at the aggregated Ethernet logical
interface or its underlying physical interface. See:
• Configuring Traffic Scheduling and Shaping for Subscriber Access
• Configuring Schedulers in a Dynamic Profile for Subscriber Access
• Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile
• Applying Minimal Shaping and Scheduling to Remaining Subscriber Traffic

Configuring the Distribution Type for Demux Subscribers on Aggregated

Ethernet Interfaces
By default, the system supports hash-based distribution of subscriber traffic in aggregated Ethernet bundles.
You can configure the system to target the egress traffic for a subscriber on a single member link, using a
single scheduler resource. The system distributes the subscriber interfaces equally among the member
links.
To configure targeted distribution:
1. Edit the chassis hierarchy level.
[edit]
user@host#edit chassis
2. Enable chassis network services for enhanced-ip mode.
[edit chassis]
user@host#set network-services enhanced-ip
3. Access the logical interface.

193
[edit]
user@host#edit interfaces demux0 unit logical-unit-number
4. Enable targeted distribution for the interface.
[edit interfaces demux0 unit logical-unit-number]

user@host#set targeted-distribution

Configuring Link and Module Redundancy for Demux Subscribers in an

Aggregated Ethernet Interface
By default, an aggregated Ethernet bundle with targeted distribution is enabled with link redundancy.
Backup links for a subscriber are chosen based on the link with the fewest subscribers, which provides
redundancy if a link fails.
We recommend that you configure the module redundancy option to provide redundancy if a module or
a link fails. Backup links for a subscriber are chosen on a different DPC or MPC from the primary link,
based on the link with the fewest subscribers among the links on different modules.
To configure module redundancy for an aggregated Ethernet bundle:
1. Access the aggregated Ethernet bundle for which you want to configure module redundancy.
edit
user@host# edit interfaces aex aggregated-ether-options
2. Enable module redundancy for the bundle.
[edit interfaces aex aggregated-ether-options]

user@host# logical-interface-fpc-redundancy
194
Configuring Rebalancing of Demux Subscribers in an Aggregated Ethernet

Interface
IN THIS SECTION
Configuring Periodic Rebalancing of Subscribers in an Aggregated Ethernet Interface | 194
Configuring Manual Rebalancing of Subscribers on an Aggregated Ethernet Interface | 195
In a targeted distribution model, the system allocates demux subscriber interfaces equally among the
member links in the aggregated Ethernet interface. When links are removed, affected subscribers are
redistributed among the active remaining backup links. When links are added to the system, no automatic
redistribution occurs. New subscribers are assigned to the links with the fewest subscribers (which are
typically the new links).
During normal network operations, the system maintains an even balance of traffic among the links in a
bundle, even as subscribers log in and out. However, if the distribution of a bundle becomes uneven (for
example, when a link goes down for a period of time and new subscribers are logging in), you can perform
a manual rebalance of the bundle. In addition, you can configure periodic rebalancing of the bundle with
a specific interval.
Configuring Periodic Rebalancing of Subscribers in an Aggregated Ethernet Interface
If subscribers are frequently logging in and logging out of your network, you can configure the system to
periodically rebalance the links based on a specific time and interval.
To configure periodic rebalancing:
1. Access the aggregated Ethernet interface for which you want to configure periodic rebalancing.
edit
user@host# edit interfaces aenumber aggregated-ether-options
195
2. Configure the rebalancing parameters for the interface, including the time and the interval between
rebalancing actions.
[edit interfaces aenumber aggregated-ether-options]

user@host# rebalance-periodic time hour:minute <interval hours>
SEE ALSO

Configuring Manual Rebalancing of Subscribers on an Aggregated Ethernet Interface
To manually rebalance the subscribers among the links in an aggregated Ethernet bundle with targeted
distribution:
• Issue the request interface rebalance command:
user@host# request interface rebalance interface <interface-name>
SEE ALSO


196
Example: Separating Targeted Multicast Traffic for Demux Subscribers on

Aggregated Ethernet Interfaces
IN THIS SECTION
Requirements | 196
Overview | 196
Configuration | 197
Verification | 204
This example shows how to separate targeted multicast traffic from targeted unicast traffic and send that
multicast traffic to a different interface through the use of OIF maps.
Requirements
Before configuring this example, make sure to configure the distribution type for the interface. See
“Configuring the Distribution Type for Demux Subscribers on Aggregated Ethernet Interfaces” on page 192
for instructions.
Overview
In this example, targeted traffic distribution is already configured on the router. Dynamically created
interfaces each carry their unicast traffic but all multicast traffic is sent to the GE-5/3/9.0 interface.
Figure 25 on page 197 shows the sample network.

197
Figure 25: Multicast Traffic Separation Using OIF Mapping
Unicast Traffic Multicast Traffic
Targeted Data
Policy / OIF Map
Dynamic
Demux GE-5/3/9.0
Interface
AE bundle
g017850
Access Node Access Node
Configuration
IN THIS SECTION
Configure an OIF Map Policy | 198
Configure a DHCP VLAN Dynamic Profile | 199
Configure a VLAN Demux Dynamic Profile | 200

set policy-options policy-statement OIF-v4-all term oif539 from route-filter 192.168.20.0/4 orlonger
set policy-options policy-statement OIF-v4-all term oif539 then map-to-interface ge-5/3/9.0
set policy-options policy-statement OIF-v4-all term oif539 then accept
set dynamic-profiles dhcp-vlan-prof interfaces "$junos-interface-ifd-name" unit "$junos-underlying-interface-unit"
family inet unnumbered-address lo0.0
set dynamic-profiles dhcp-vlan-prof interfaces "$junos-interface-ifd-name" unit "$junos-underlying-interface-unit"
family inet unnumbered-address preferred-sour ce-address 10.20.0.2
set dynamic-profiles demux-vlan-prof interfaces demux0 unit "$junos-interface-un it" vlan-id "$junos-vlan-id"
set dynamic-profiles demux-vlan-prof interfaces demux0 unit "$junos-interface-un it" demux-options
underlying-interface "$junos-interface-ifd-name"
198
set dynamic-profiles demux-vlan-prof interfaces demux0 unit "$junos-interface-un it" targeted-distribution

set dynamic-profiles demux-vlan-prof interfaces demux0 unit "$junos-interface-un it" family inet
unnumbered-address lo0.0
set dynamic-profiles demux-vlan-prof interfaces demux0 unit "$junos-interface-un it" family inet
unnumbered-address preferred-source-address 10.20.0.2
set dynamic-profiles demux-vlan-prof protocols igmp interface "$junos-interface- name" version 2
set dynamic-profiles demux-vlan-prof protocols igmp interface "$junos-interface- name" promiscuous-mode
set dynamic-profiles demux-vlan-prof protocols igmp interface "$junos-interface- name" passive allow-receive
set dynamic-profiles demux-vlan-prof protocols igmp interface "$junos-interface- name" passive send-group-query
set dynamic-profiles demux-vlan-prof protocols igmp interface "$junos-interface- name" oif-map OIF-v4-all
Configure an OIF Map Policy
The following example requires you to navigate various levels in the configuration hierarchy.
To configure the OIF map:
1. Access the router policy options:
[edit]
user@host#edit policy-options
2. Edit a policy statement.
[edit policy-options]
user@host edit policy-statement OIF-v4-all
3. Create a term for mapping incoming multicast traffic to a specific interface.
[edit policy-options OIF-v4-all]

user@host edit term oif539
4. Define the match condition for the term. In this case, the term matches any route prefix of
192.168.20.0/4 or longer (all multicast traffic).
[edit policy-options OIF-v4-all term oif539]

user@host set from route-filter 192.168.20.0/4 orlonger
5. Define the action for the term. In this case, when a match occurs, the term accepts the traffic and maps
it to interface GE-5/3/9.0.
199
[edit policy-options OIF-v4-all term oif539]

user@host set then map-to-interface ge-5/3/9.0
user@host set then accept
Results
Confirm your configuration by issuing the show policy-options commands. If the output does not display
the intended configuration, repeat the instructions in this example to correct the configuration.
[edit]
user@host# show policy-options
policy-statement OIF-v4-all {
term oif539 {
from {
route-filter 192.168.20.0/4 orlonger;
}
then {
map-to-interface ge-5/3/9.0;
accept;
}
}
}
Configure a DHCP VLAN Dynamic Profile
To configure a DHCP VLAN dynamic profile for client access:
1. Create a dynamic VLAN demux profile.
[edit]
user@host#edit dynamic-profiles dhcp-vlan-prof
2. Edit the dynamic profile interface.
[edit dynamic-profiles dhcp-vlan-prof]

user@host edit interfaces $junos-ifd-name
200
3. Edit the interface unit dynamic variable.
[edit dynamic-profiles demux-vlan-prof interfaces $junos-ifd-name]

user@host edit unit $junos-underlying-interface-unit
4. Edit the interface family.
[edit dynamic-profiles demux-vlan-prof interfaces $junos-ifd-name unit $junos-underlying-interface-unit]

user@host edit family inet
5. Define the loopback address.
[edit dynamic-profiles demux-vlan-prof interfaces $junos-ifd-name unit $junos-underlying-interface-unit ]

user@host set unnumbered-address lo0.0 preferred-source-address 10.20.0.2
Results
Confirm your configuration by issuing the show dynamic-profiles command. If the output for the
dhcp-vlan-prof dynamic profile does not display the intended configuration, repeat the instructions in this
example to correct the configuration.
[edit]
dhcp-vlan-prof {
interfaces {
family inet {
}
}
}
}
}
Configure a VLAN Demux Dynamic Profile
201
To configure the OIF map:
1. Create a dynamic VLAN demux profile.
[edit]
user@host#edit dynamic-profiles demux-vlan-prof
2. Edit the dynamic profile demux0 interface.
[edit dynamic-profiles demux-vlan-prof]

user@host edit interfaces demux0
3. Edit the interface unit dynamic variable.
[edit dynamic-profiles demux-vlan-prof interfaces demux0]

user@host edit unit $junos-interface-unit
4. Specify the VLAN ID dynamic variable.
[edit dynamic-profiles demux-vlan-prof interfaces demux0 unit “$junos-interface-unit”]

user@host set vlan-id $junos-vlan-id
5. Access the demux options.

user@host edit demux-options
6. Define the demux underlying interface.
[edit dynamic-profiles demux-vlan-prof interfaces demux0 unit “$junos-interface-unit” demux-options]

user@host set underlying-interface $junos-interface-ifd-name
7. Specify that dynamically created VLANs are using targeted distribution.

202
user@host set targeted-distribution
8. Edit the interface family.

user@host edit family inet
9. Define the loopback address.
[edit dynamic-profiles demux-vlan-prof interfaces demux0 unit “$junos-interface-unit” family inet]

user@host set unnumbered-address lo0.0 preferred-source-address 10.20.0.2
10. Edit the dynamic profile IGMP protocol.
[edit dynamic-profiles demux-vlan-prof]

user@host edit protocols igmp
11. Enable IGMP on dynamically created interfaces.
[edit dynamic-profiles demux-vlan-prof protocols igmp]

user@host edit interface $junos-interface-name
12. Specify the IGMP version that you want dynamically created interfaces to use.
[edit dynamic-profiles demux-vlan-prof protocols igmp interface $junos-interface-name]

user@host set version 2
13. Specify the OIF map that you want dynamically created IGMP interfaces to use.

user@host set oif-map OIF-v4-all
203
14. Specify that IGMP selectively sends and receives control traffic such as IGMP reports, queries, and
leaves.

user@host set passive allow-receive send-group-query
15. Specify that the interface accepts IGMP reports from hosts on any subnetwork.

user@host set promiscuous-mode
Results
Confirm your configuration by issuing the show dynamic-profiles commands. If the output for the
dhcp-vlan-prof dynamic profile does not display the intended configuration, repeat the instructions in this
example to correct the configuration.
[edit]
demux-vlan-prof {
interfaces {
demux0 {
vlan-id "$junos-vlan-id";
demux-options {
underlying-interface "$junos-interface-ifd-name";
}
targeted-distribution;
family inet {
}
}
}
}
protocols {
igmp {
interface "$junos-interface-name" {
version 2;
promiscuous-mode;
passive allow-receive send-group-query;
oif-map OIF-v4-all;
}
}
204
}
}
...
Verification
IN THIS SECTION
Locate the Multicast Group Member | 204
Ensure the Targeting Aggregated Ethernet Interface for the Subscriber is Functional | 205
View the Packets for the Targeted Interface | 206
Confirm that the configuration is working properly.
Locate the Multicast Group Member
Purpose
Locate the dynamic interface and ensure that it is associated with the appropriate IGMP group.
Action
user@host>show igmp group
Interface: demux0.1073741824, Groups: 1

Group: 192.0.2.1
Source: 0.0.0.0
Last reported by: 10.20.0.10
Timeout: 52 Type: Dynamic
Interface: local, Groups: 2
Group: 192.0.2.2
Source: 0.0.0.0
Last reported by: Local
Group: 192.0.2.22
Source: 0.0.0.0
Last reported by: Local
205
Meaning
The first Interface field shows the dynamically created demux interface, demux0.1073741824, and the
Group field immediately below the first Interface field shows the group, 192.0.2.1, to which the subscriber
belongs.
Ensure the Targeting Aggregated Ethernet Interface for the Subscriber is Functional
Purpose
Use the dynamic subscriber interface value to ensure that the targeting aggregated interface is functional.
Action
user@host>show interfaces demux0.1073741824 extensive
Logical interface demux0.1073741824 (Index 810) (SNMP ifIndex 1613)

(Generation 170)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1 ] Encapsulation: ENET2
Demux:
Underlying interface: ae0 (Index 708)
Link:
ge-1/0/0
ge-5/3/7
Targeting summary:
ge-1/0/0, backup, Physical link is Up
ge-5/3/7, primary, Physical link is Up
Traffic statistics:
Input bytes : 862
Output bytes : 3160
Input packets: 3
Output packets: 30
Local statistics:
Input bytes : 862
Output bytes : 3160
Input packets: 3
Output packets: 30
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol inet, MTU: 1500, Generation: 212, Route table: 0
Flags: Sendbcast-pkt-to-re, Unnumbered
Donor interface: lo0.0 (Index 802)
Preferred source address: 10.20.0.2
206
Meaning
The Targeting summary field shows that the primary interface, ge-5/3/7, is up.
View the Packets for the Targeted Interface
Purpose
Verify that packet traffic sent to targeted interface GE-5/3/9 consists only of multicast packets.
Action
user@host>show interfaces ge-5/3/9 extensive
Physical interface: ge-5/3/9, Enabled, Physical link is Up

Interface index: 704, SNMP ifIndex: 1605, Generation: 197
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Online
Link flags : None
Schedulers : 0
Hold-times : Up 0 ms, Down 0 ms
Current address: 00:21:59:ab:85:2a, Hardware address: 00:21:59:ab:85:2a
Last flapped : 2012-09-26 17:32:24 EDT (6d 20:44 ago)
Statistics last cleared: Never
Traffic statistics:
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Dropped traffic statistics due to STP State:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
FIFO errors: 0, Resource errors: 0
207
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Queue number: Mapped forwarding classes
0 best-effort
1 expedited-forwarding
2 assured-forwarding
3 network-control
MAC statistics: Receive Transmit
Total octets 0 113871616
Total packets 0 889620
Unicast packets 0 0
Broadcast packets 0 0
Multicast packets 0 889620
CRC/Align errors 0 0
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
VLAN tagged frames 0
Code violations 0
Total errors 0 0
Filter statistics:
Input packet count 0
Input packet rejects 0
Input DA rejects 0
Input SA rejects 0
Output packet count 889620
Output packet pad count 0
Output packet error count 0
CAM destination filters: 0, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
208
Link mode: Full-duplex, Flow control: Symmetric, Remote fault: OK

Local resolution:
Flow control: None, Remote fault: Link OK
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 950000000 95 0 low none
3 network-control 5 50000000 5 0 low none
Logical interface ge-5/3/9.0 (Index 818) (SNMP ifIndex 1597) (Generation 149)
Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Traffic statistics:
Input bytes : 0
Output bytes : 97857650
Input packets: 0
Output packets: 889620
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Protocol aenet, AE bundle: ae4.0, Generation: 180, Route table: 0
Meaning
The MAC statistics Unicast packet field shows that the interface is not transmitting any unicast packet
traffic and the Multicast packet field shows that the total number of packets being transmitted from the
interface are multicast packets.
209
Verifying the Distribution of Demux Subscribers in an Aggregated Ethernet

Interface
Purpose
View the distribution status of subscribers that are targeted to links in an aggregated Ethernet interface.
Action
• To display a summary of the distribution of links on the demux interface:
user@host> show interfaces demux0 extensive
• To display the targeted distribution on a specific aggregated Ethernet interface:
user@host> show interfaces targeting aex
Configuring the Distribution Type for PPPoE Subscribers on Aggregated

Ethernet Interfaces
By default, the system supports hash-based distribution of subscriber traffic in aggregated Ethernet bundles.
You can configure the system to target the egress traffic for a subscriber on a single member link, using a
single scheduler resource. The system distributes the subscriber interfaces equally among the member
links.
To configure targeted distribution:
1. Edit the chassis hierarchy level.
[edit]
user@host#edit chassis
210
2. Enable chassis network services for enhanced-ip mode.
[edit chassis]
user@host#set network-services enhanced-ip
3. Access the logical interface.
[edit]
user@host#edit interfaces pp0 unit logical-unit-number
4. Enable targeted distribution for the interface.
[edit interfaces pp0 unit logical-unit-number]

user@host#set targeted-distribution

Verifying the Distribution of PPPoE Subscribers in an Aggregated Ethernet

Interface
Purpose
View the distribution status of subscribers that are targeted to links in an aggregated Ethernet interface.
Action
• To display a summary of the distribution of links on the demux interface:
user@host> show interfaces pp0 extensive
• To display the targeted distribution on a specific aggregated Ethernet interface:
user@host> show interfaces targeting aex

211

212
CHAPTER 9
Applying CoS Using Parameters Received from

RADIUS
IN THIS CHAPTER
CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber Sessions Overview | 221
Guidelines for Configuring CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member Subscriber
Sessions | 223
Configuring Static Default Values for Traffic Scheduling and Shaping | 225
Applying CoS Traffic-Shaping Attributes to Dynamic Interface Sets and Member Subscriber Sessions | 227
Example: Configuring Dynamic Hierarchical Scheduling for Subscribers | 235
Subscriber Interfaces That Provide Initial CoS Parameters Dynamically

Obtained from RADIUS
IN THIS SECTION
Dynamic Configuration of Initial CoS in Access Profiles | 213
Predefined Variables for Dynamic Configuration of Initial Traffic Shaping | 213
Predefined Variables for Dynamic Configuration of Initial Scheduling and Queuing | 214
213
You can configure interface-specific CoS parameters that the router obtains when subscribers log in at
appropriately configured static or dynamic subscriber interfaces. This feature is supported only for interfaces
on Enhanced Queuing Dense Port Concentrators (EQ DPCs) in MX Series 5G Universal Routing Platforms.
To configure a dynamic profile to provide initial CoS Services, make sure you understand the following
concepts:
Dynamic Configuration of Initial CoS in Access Profiles
When a router interface receives a join message from a DHCP subscriber, the Junos OS applies the values
configured in the dynamic profile associated with that router interface. A dynamic profile that is activated
through its association with a subscriber interface is known as an access dynamic profile. You can associate
a dynamic profile with a subscriber interface on the router by including statements at the [edit
dynamic-profiles profile-name class-of-service interfaces] hierarchy level.
The Junos OS supports predefined variables for obtaining CoS parameters from the RADIUS authentication
server. When a client authenticates over a router interface associated with the access dynamic profile,
the router replaces the predefined variables with interface-specific values obtained from the RADIUS
server.
NOTE: To associate dynamically configured initial CoS features with a subscriber interface,
reference Junos OS predefined variables—and not user-defined variables—in an access dynamic
profile for that interface.
Predefined Variables for Dynamic Configuration of Initial Traffic Shaping
You can configure an access dynamic profile that provides initial traffic-shaping parameters when a
subscriber logs in. The Junos OS obtains this information from the RADIUS server when a subscriber
authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached.
If you define the Juniper Networks authentication and authorization VSA for CoS traffic-shaping parameter
values (attribute number 26–108) on the RADIUS authentication server, the RADIUS server includes the
values in RADIUS Access-Accept messages it sends to the router when a subscriber successfully
authenticates over the interface.
To provide an initial scheduler map name and traffic shaping parameters obtained from the RADIUS
authentication server when a subscriber logs in, reference the Junos OS predefined variables for CoS listed
in Table 20 on page 214 in an access dynamic profile associated with the subscriber interface.
214
Table 20: CoS Predefined Variables for Scheduler Map and Traffic Shaping
Variable Description
$junos-cos-scheduler-map Scheduler-map name to be dynamically configured in a traffic-control profile in the

access dynamic profile when a subscriber logs in.
NOTE: The scheduler map referenced by the scheduler-map statement can be defined
dynamically (at the [edit dynamic-profiles profile-name class-of-service scheduler-maps]
hierarchy level) or statically (at the [edit class-of-service scheduler-maps] hierarchy
level).
$junos-cos-shaping-rate Shaping rate to be dynamically configured in a traffic-control profile in the access

dynamic profile when a subscriber logs in. You can configure a RADIUS authentication
server to include this information in the Accept-Accept message when a subscriber
successfully authenticates over the static or dynamic subscriber interface to which
the access dynamic profile is attached.
$junos-cos-guaranteed-rate Guaranteed rate to be dynamically configured in a traffic-control profile in the access

$junos-cos-delay-buffer-rate Delay-buffer rate to be dynamically configured in a traffic-control profile in the access

Predefined Variables for Dynamic Configuration of Initial Scheduling and Queuing
You can configure an access dynamic profile that provides initial traffic-shaping parameters when a
subscriber logs in. The Junos OS obtains this information from the RADIUS server when a subscriber
authenticates over the static or dynamic subscriber interface to which the access dynamic profile is attached.
If you define the Juniper Networks authentication and authorization VSA for CoS scheduling and queuing
parameter values (attribute number 26–146) on the RADIUS authentication server, the RADIUS server
includes the values in RADIUS Access-Accept messages it sends to the router when a subscriber successfully
authenticates over the interface.
To provide an initial scheduler name and scheduler and queuing parameters obtained from the RADIUS
authentication server when a subscriber logs in, reference the Junos OS predefined variables listed in
Table 21 on page 215 in an access dynamic profile associated with the subscriber interface.
215
Table 21: CoS Predefined Variables for Scheduling and Queuing
$junos-cos-scheduler Name of a scheduler to be dynamically configured in the access

dynamic profile. You can configure a RADIUS authentication server to
include this information in the Accept-Accept message when a
subscriber successfully authenticates over the static or dynamic
subscriber interface to which the access dynamic profile is attached.
$junos-cos-scheduler-transmit-rate Transmit rate to be dynamically configured for the scheduler in the

access dynamic profile. You can configure a RADIUS authentication
server to include this information in the Accept-Accept message when
a subscriber successfully authenticates over the static or dynamic
subscriber interface to which the access dynamic profile is attached.
$junos-cos-scheduler-bs Buffer size, as a percentage of total buffer, to be dynamically configured

for the scheduler in the access dynamic profile. You can configure a
RADIUS authentication server to include this information in the
Accept-Accept message when a subscriber successfully authenticates
over the static or dynamic subscriber interface to which the access
dynamic profile is attached.
$junos-cos-scheduler-pri Packet-scheduling priority value to be dynamically configured for the

scheduler in the access dynamic profile. You can configure a RADIUS
authentication server to include this information in the Accept-Accept
message when a subscriber successfully authenticates over the static
or dynamic subscriber interface to which the access dynamic profile
is attached.
$junos-cos-scheduler-dropfile-low Name of the drop profile for RED for loss-priority level low to be
dynamically configured for the scheduler in the access dynamic profile.
You can configure a RADIUS authentication server to include this
information in the Accept-Accept message when a subscriber
successfully authenticates over the static or dynamic subscriber
interface to which the access dynamic profile is attached.
NOTE: The drop profile must be configured statically (at the [edit
class-of-service schedulers scheduler-name drop-profiles] hierarchy
level) for loss-priority low.
216
Table 21: CoS Predefined Variables for Scheduling and Queuing (continued)
$junos-cos-scheduler-dropfile-medium-low Name of the drop profile for RED for loss-priority level medium-low
to be dynamically configured for the scheduler in the access dynamic
profile. The Junos OS obtains this information from the RADIUS server
when a subscriber authenticates over the static or dynamic subscriber
level).
$junos-cos-scheduler-dropfile-medium-high Name of the drop profile for RED for loss-priority level medium-high
to be dynamically configured for the scheduler in the access dynamic
profile. You can configure a RADIUS authentication server to include
this information in the Accept-Accept message when a subscriber
level).
$junos-cos-scheduler-dropfile-high Name of the drop profile for RED for loss-priority level high to be
level).
$junos-cos-scheduler-dropfile-any Name of the drop profile for RED for loss-priority level any to be
level).
217
Subscriber Activation and Service Management in an Access Network

Dynamic Variables Overview
Junos OS Predefined Variables
Example: Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
Changing CoS Services Overview
This topic describes how to provide CoS when subscribers dynamically upgrade or downgrade services in
an access environment.
You can configure your network with a dynamic client profile that provides all subscribers with default CoS
parameters when they log in. For example, all subscribers can receive a basic data service. By configuring
the client profile with Junos OS predefined variables for RADIUS-provided CoS parameters, you also enable
the service to be activated for those subscribers at login.
NOTE: The dynamic client profile is also referred to as a dynamic client access profile, or
sometimes just access profile for brevity. Do not confuse this profile, configured at the [edit
dynamic-profiles profile-name] hierarchy level, with the access profile configured at the [edit
access profile profile-name] hierarchy level. These static access profiles are used to configure
authentication, accounting, and authorization parameters for subscriber access, some session
attributes, and client-specific properties for L2TP and PPP sessions. Access profiles are applied
at various configuration levels with the access-profile statement.
To enable subscribers to activate a service or upgrade to different services through RADIUS

change-of-authorization (CoA) messages after login, configure a dynamic service profile that includes
user-defined variables.
Types of CoS Variables Used in a Service Profile
You can configure variables for the following CoS parameters in a service profile:
• Shaping rate
• Delay buffer rate

218
• Guaranteed rate
• Scheduler map
For each CoS parameter, you must associate a RADIUS vendor ID. For each vendor ID, you must assign
an attribute number and a tag. The tag is used to differentiate between values for different CoS variables
when you specify the same attribute number for those variables. These values are matched with the values
supplied by RADIUS during subscriber authentication. All of the values in the dynamic profile must be
defined in RADIUS or none of the values are passed.
Optionally, you can configure default values for each parameter. Configuring default values is beneficial
if you do not configure RADIUS to enable service changes. During service changes, RADIUS takes
precedence over the default value that is configured.
Static and Dynamic CoS Configurations
Depending on how you configure CoS parameters in the access and service profiles, certain CoS parameters
are replaced or merged when subscribers change or activate new services.
Static configuration is when you configure the scheduler map and schedulers in the static [edit
class-of-service] hierarchy and reference the scheduler map in the dynamic profile. Dynamic configuration
is when you configure the scheduler map and schedulers within the dynamic profile.
The CoS configuration also depends on whether you have enabled multiple subscribers on the same logical
interface using the aggregate-clients statements in the dynamic profile referenced by DHCP. When you
specify the aggregate-clients replace statement, the scheduler map names are replaced. In both cases, if
the length of the scheduler map name exceeds 128 characters, subscribers cannot log in. When you specify
the aggregate-clients merge statement, the scheduler map names specified in the dynamic profile are
appended.
BEST PRACTICE: To improve CoS performance in IPv4, IPv6, and dual-stack networks, we
recommend that you use the aggregate-clients replace statement rather than the
aggregate-clients merge statement.
Scenarios for Static and Dynamic Configuration of CoS Parameters
Table 22 on page 219 lists the scenarios for static and dynamic configuration of CoS parameters in access
profiles and service profiles at subscriber login. The table also lists the behavior for each configuration for
service activation and service modification using RADIUS CoA messages.
219
Table 22: CoS Services and Variables
Dynamic CoS Dynamic CoS

Configuration Configuration
(Multiple (Multiple
Subscribers Subscribers
Enabled on a Enabled on a
Logical Interface Logical Interface
Static CoS Dynamic CoS with the with the
Configuration Configuration aggregate-clients aggregate-clients
Scenario (Single Subscriber) (Single Subscriber) merge Statement) replace Statement)
Subscriber login • Configure RADIUS • Configure RADIUS • Configure RADIUS • Configure RADIUS
values or default values or default values or default values or default
values for all values for all values for all values for all
parameters in parameters in parameters in parameters in
access profile access profile access profile access profile
• Configure • Configure • Configure • Configure
scheduler map in scheduler map and scheduler map and scheduler map and
edit schedulers in schedulers in schedulers in
class-of-service access profile access profile access profile
hierarchy and
reference in access
profile
RADIUS CoA for Replaces the Replaces the Combines the values Replaces the
service or variable following parameters: following parameters: of the following following parameters:
change parameters to their
• Delay buffer rate • Delay buffer rate maximum scalar • Delay buffer rate
• Guaranteed rate • Guaranteed rate value: • Guaranteed rate
• Scheduler map • Shaping rate • Shaping rate
• Delay buffer rate
• Shaping rate • Scheduler map • Scheduler map
• Guaranteed rate
• Shaping rate
Appends the
scheduler map
parameter
220
Table 22: CoS Services and Variables (continued)
Dynamic CoS Dynamic CoS

Configuration Configuration
(Multiple (Multiple
Subscribers Subscribers
Enabled on a Enabled on a
Logical Interface Logical Interface
Static CoS Dynamic CoS with the with the
Configuration Configuration aggregate-clients aggregate-clients
Scenario (Single Subscriber) (Single Subscriber) merge Statement) replace Statement)
RADIUS CoA for Does not merge Merge queues if the Merge queues if the Merge queues if the
service activation queues queue specified in queue specified in queue specified in
the service profile is the service profile is the service profile is
NOTE:In this case,
not already in use for not already in use for not already in use for
use a similar
the subscriber the subscriber the subscriber
configuration to the
access profile, NOTE: Do not NOTE: Do not NOTE: Do not
including the same instantiate a CoA instantiate a CoA instantiate a CoA
name for the request using a request using a request using a
traffic-control-profile. service dynamic service dynamic service dynamic
During service profile that is already profile that is already profile that is already
activation, this in use on the same in use on the same in use on the same
configuration logical interface. logical interface. logical interface.
replaces the original
configuration in the
access profile.

Dynamic Profile Attachment to DHCP Subscriber Interfaces Overview
RADIUS Attributes and Juniper Networks VSAs Supported by the AAA Service Framework
221
CoS Traffic Shaping Attributes for Dynamic Interface Sets and Member
Subscriber Sessions Overview
IN THIS SECTION
Supported Network Configurations | 221
Traffic-Control Profiles in Subscriber Interface Dynamic Profiles | 221
CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets and Member Subscriber Sessions | 222
To control bandwidth at a household level in a subscriber access network, you can apply RADIUS dynamic
class of service (CoS) traffic-shaping attributes to a dynamic interface set and its member subscriber
sessions when the subscriber sessions are authenticated. (The dynamic interface set itself does not go
through the authentication process.)
A household is represented by either a dynamic interface set or a dynamic agent-circuit-identifier (ACI)

interface set from which the subscriber sessions originate. For this feature, dynamic interface sets and
dynamic ACI interface sets are mapped to Level 2 of the Junos OS CoS scheduler hierarchy, which enables
you to use CoS traffic-shaping to shape the bandwidth at the household (interface set) level.
The subscriber sessions, also referred to as subscriber interfaces or client sessions, can be dynamic VLAN,
PPPoE, or IP demultiplexing (IP demux) subscriber interfaces. The subscriber interfaces are mapped to
Level 3 of the Junos OS CoS scheduler hierarchy.
Supported Network Configurations
Applying RADIUS dynamic CoS traffic-shaping attributes to a dynamic interface set and its member
subscriber sessions is supported for the following network configurations:
• Dynamic IP demux subscriber interfaces (for DHCP subscribers) over either a dynamic interface set or
a dynamic ACI interface set
• Dynamic PPPoE subscriber interfaces over either a dynamic interface set or a dynamic ACI interface set
Traffic-Control Profiles in Subscriber Interface Dynamic Profiles
To apply dynamic CoS traffic-shaping attributes to a dynamic interface set and its member subscriber
sessions, you must define and attach the traffic-control profiles for both the dynamic interface set and the
dynamic subscriber sessions within the dynamic profile for the subscriber interface.
222
At the [edit dynamic-profiles profile-name class-of-service traffic-control-profiles] hierarchy level in the

dynamic profile, configure both of the following:
• Traffic-control profile for the dynamic VLAN, PPPoE, or IP demux subscriber interfaces
• Traffic-control profile for the dynamic interface set or dynamic ACI interface set to which the subscriber
interfaces belong
RADIUS tag values for the Junos OS CoS traffic shaping predefined variables used in both traffic-control
profiles must be in the 100s range, as described in “CoS Traffic Shaping Predefined Variables for Dynamic
Interface Sets” on page 229.
At the [edit dynamic-profiles profile-name interfaces] hierarchy level in the dynamic profile, use the
output-traffic-control-profile statement to apply the traffic-control profiles to the dynamic subscriber
interface and the dynamic interface set or dynamic ACI interface set.
CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets and Member Subscriber
Sessions
The set of $junos-cos-parameter predefined dynamic variables has been duplicated and assigned a RADIUS
tag value in the 100s range for use with this feature. The RADIUS tag value is the only difference between
the existing CoS traffic-shaping predefined dynamic variables and the predefined dynamic variables that
you must use with this feature.
Both RADIUS instances of the $junos-cos-parameter predefined dynamic variables are available, but you
must use the dynamic variables with tag values in the 100s range to apply CoS traffic-shaping attributes
to both the dynamic interface set and member subscriber sessions in a subscriber interface dynamic profile.
For example, the existing $junos-cos-shaping-rate predefined variable is assigned RADIUS vendor ID
4874, attribute number 108, and tag value 2. To apply CoS traffic-shaping attributes to the dynamic
interface set and its member subscriber sessions, you must instead use the $junos-cos-shaping-rate
predefined variable that is assigned RADIUS vendor ID 4874, attribute number 108, and tag value 102.
NOTE: Do not configure a combination of $junos-cos-parameter predefined dynamic variables

with RADIUS tag values in the 100s range and $junos-cos-parameter predefined dynamic variables
with tag values not in the 100s range in the same traffic-control profile. If you do so, the subscriber
authentication process fails.
223
Guidelines for Configuring CoS Traffic Shaping Attributes for Dynamic

Interface Sets and Member Subscriber Sessions
Observe the following guidelines when you apply dynamic CoS traffic-shaping attributes to a dynamic
interface set or a dynamic ACI interface set and its member subscriber sessions. For complete information
about the Junos OS CoS traffic-shaping predefined dynamic variables and RADIUS tag values used with
this feature, see “CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets” on page 229.
• This feature is supported only for dynamically configured and instantiated subscriber interfaces.
• Do not configure a combination of $junos-cos-parameter predefined dynamic variables with RADIUS

tag values in the 100s range and $junos-cos-parameter predefined dynamic variables with tag values
not in the 100s range in the same traffic-control profile. If you do so, the subscriber authentication
process fails.
• Use the $junos-cos-adjust-minimum predefined variable (tag 109) only in traffic-control profiles for
dynamic subscriber interfaces. Using this variable in a traffic-control profile for a dynamic interface set
or dynamic ACI interface set has no effect.
• Do not configure the $junos-cos-excess-rate-high predefined variable (tag 110) when the
$junos-cos-excess-rate predefined variable (tag 105) is configured, and vice-versa.
• Do not configure the $junos-cos-excess-rate-low predefined variable (tag 111) when the
$junos-cos-excess-rate predefined variable (tag 105) is configured, and vice-versa.
• Do not configure the $junos-cos-byte-adjust-frame predefined variable (tag 114) when the
$junos-cos-byte-adjust predefined variable (tag 108) is configured, and vice-versa.
• Do not configure the $junos-cos-byte-adjust-cell predefined variable (tag 115) when the
$junos-cos-byte-adjust predefined variable (tag 108) is configured, and vice-versa.
• Use the per-priority $junos-cos-shaping-rate-parameter predefined variables (tags 116 through 125)
only in traffic-control profiles for dynamic interface sets or dynamic ACI interface sets. Using these
variables in traffic-control profiles for a dynamic logical subscriber interface causes the subscriber session
to fail.
224
Overview | 221
Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
You can configure a subscriber interface so that subscribers receive initial CoS parameters that the router
obtains from the RADIUS authentication server when subscribers log in using that logical interface on the
router.
1. Configure external RADIUS server VSAs with values that you expect subscribers to log in with.
• To configure a RADIUS authentication server to include CoS traffic-shaping parameters in

authentication grants on certain subscriber interfaces, configure Juniper Networks VSA 26–108.
• To configure a RADIUS authentication server to include CoS scheduling and queuing parameters in
authentication grants a certain subscriber interfaces, configure Juniper Networks VSA 28–146.
See Configuring Router or Switch Interaction with RADIUS Servers and RADIUS Servers and Parameters for
Subscriber Access.
2. Configure a subscriber interface that supports hierarchical CoS.
3. Associate a traffic-control profile with the interface.
See Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile.
4. Configuring initial traffic-shaping parameters to be obtained from RADIUS.
See Configuring Dynamic Traffic Shaping and Scheduling Parameters in a Dynamic Profile.
5. Configure forwarding classes and scheduler maps statically.
See Configuring a Custom Forwarding Class for Each Queue and Configuring Scheduler Maps.
6. Configure a scheduler to specify initial scheduling and queuing parameters to be dynamically obtained
from RADIUS when a subscriber logs in.
See Configuring Dynamic Schedulers with Variables in a Dynamic Profile.
225
Example: Configuring Initial CoS Parameters Dynamically Obtained from RADIUS
Subscriber Activation and Service Management in an Access Network
Juniper Networks VSAs Supported by the AAA Service Framework
Dynamic Variables Overview
Configuring Static Default Values for Traffic Scheduling and Shaping
To provide subscribers with default values for CoS parameters, configure user-defined variables for CoS
parameters and assign static default values to the variables. If you have configured values to be supplied
by a RADIUS CoA, subscribers receive the default value when deactivating a service.
To configure user-defined variables with default values for CoS in a dynamic profile:
1. Specify that you want to configure variables in the dynamic profile.
[edit dynamic-profiles residential-silver variables]
2. Configure a default value for the shaping rate.

user@host# set srate default-value 5m
3. Configure a default value for the guaranteed rate.

user@host# set grate default-value 5m
4. Configure a default value for the delay buffer rate.

user@host# set dbrate default-value 10m
5. Configure a default value for the scheduler map.

226

user@host# set smap default-value triple-play
6. Configure the variables for the CoS parameters in the traffic-control profile.
Either the shaping rate or the guaranteed rate is required in the traffic-control profile.
a. Access the traffic-control profile in the dynamic profile.
user@host# edit dynamic-profiles residential-silver class-of-service traffic-control-profiles tcp1
b. Configure the scheduler map variable.
[edit dynamic-profiles residential-silver class-of-service traffic-control-profiles tcp1]

user@host# set scheduler-map "$smap"
c. Configure the shaping rate variable.

user@host# set shaping-rate "$srate"
d. Configure the guaranteed rate variable.

user@host# set guaranteed-rate "$grate"
e. Configure the delay buffer rate variable.

user@host# set delay-buffer-rate "$dbrate"

227
Applying CoS Traffic-Shaping Attributes to Dynamic Interface Sets and

Member Subscriber Sessions
To control bandwidth at a household level in a subscriber access network, you can apply RADIUS dynamic
class of service (CoS) traffic-shaping attributes to a dynamic interface set or agent-circuit-identifer (ACI)
interface set and its member subscriber sessions when the member sessions are authenticated. The dynamic
interface set or ACI interface set represents the household from which the subscriber sessions originate.
The subscriber sessions, also referred to as client sessions or subscriber interfaces, can be dynamic VLAN,
PPPoE, or IP demultiplexing (IP demux, for DHCP) subscriber interfaces.
To apply RADIUS dynamic CoS traffic-shaping attributes to both the dynamic interface set and its member
subscriber sessions, you must configure two traffic-control profiles in the dynamic profile for the subscriber
interface: one traffic-control profile for the “parent” dynamic interface set, and a second traffic-control
profile for the dynamic subscriber interfaces. RADIUS tag values for the Junos OS CoS traffic shaping
predefined variables used in both traffic-control profiles must be in the 100s range.
Before you begin:
• Create a dynamic profile that defines the VLAN, PPPoE, or IP demux logical subscriber interface.
See the following topics:
• Configuring a Basic Dynamic Profile
• Configuring a Dynamic Profile Used to Create Single-Tag VLANs
• Configuring a Dynamic Profile Used to Create Stacked VLANs
• Configuring Dynamic PPPoE Subscriber Interfaces
• Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles
To apply dynamic CoS traffic-shaping attributes to a dynamic ACI or non-ACI interface set and its member
subscriber sessions in a dynamic profile for the subscriber interface:
1. Configure two traffic-control profiles at the [edit dynamic-profiles profile-name class-of-service

traffic-control profiles] hierarchy level:
• Traffic-control profile for the VLAN, PPPoE, or IP demux dynamic subscriber interfaces
• Traffic-control profile for the dynamic interface set or dynamic ACI interface set to which the
subscriber interfaces belong
2. In the traffic-control profiles configured for the dynamic interface set and the subscriber interfaces,
reference Junos OS CoS traffic-shaping predefined variables with RADIUS tag values in the 100s range.
See “CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets” on page 229 for a complete
list of the Junos OS predefined variables and RADIUS tag values that you must use in the traffic-control
profiles for the dynamic subscriber interfaces and the dynamic interface set.
228
3. At the [edit dynamic-profiles profile-name interfaces] hierarchy level, use the

output-traffic-control-profile statement to apply the traffic-control profiles to the dynamic subscriber
interface and the dynamic interface set or dynamic ACI interface set.
Example: Dynamic PPPoE Subscriber Interface over Dynamic ACI Interface Set
The following example shows a dynamic profile named pppoe-subscriber that configures a dynamic PPPoE
(pp0) subscriber interface over a dynamic ACI interface set.
The traffic-control-profiles stanza defines two traffic-control profiles: tcp-pppoe-session for the dynamic
PPPoE subscriber interface, and tcp-parent-aci-set for the dynamic “parent” ACI interface set. The
$junos-cos-shaping-rate predefined variable included in each of these traffic-control profiles is assigned
RADIUS vendor ID 4874, attribute number 108, and tag value 102. The $junos-cos-shaping-mode variable
is assigned RADIUS vendor ID 4874, attribute number 108, and tag value 107.
The interfaces stanza applies output traffic-control profile tcp-pppoe-session to the dynamic PPPoE (pp0)
subscriber interface, and output traffic-control profile tcp-parent-aci-set to the dynamic ACI interface set.
[edit dynamic-profiles]
pppoe-subscriber {
interfaces {
interface-set "$junos-interface-set-name" {
interface pp0 {
unit "$junos-interface-unit";
}
}
pp0 {
ppp-options {
pap;
}
pppoe-options {
underlying-interface "$junos-underlying-interface";
server;
}
no-keepalives;
family inet {
unnumbered-address lo0.0;
}
}
229
}
}
class-of-service {
tcp-pppoe-session {
scheduler-map smap-1;
shaping-rate $junos-cos-shaping-rate;
overhead-accounting $junos-cos-shaping-mode frame-mode-bytes -4 cell-mode-bytes 12;
}
tcp-parent-aci-set {
overhead-accounting $junos-cos-shaping-mode frame-mode-bytes -4 cell-mode-bytes 12;
}
}
interfaces {
pp0 {
output-traffic-control-profile tcp-pppoe-session;
}
}
interface-set $junos-interface-set-name {
output-traffic-control-profile tcp-parent-aci-set;
}
}
}
}
}
Overview | 221
CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets
To control bandwidth at a household level in a subscriber access network, you can apply RADIUS CoS
traffic-shaping attributes to a dynamic interface set and its member subscriber sessions when the member
230
sessions are authenticated. The dynamic interface set, which represents the household level in a subscriber
access network, can be either a dynamic agent-circuit-identifier (ACI) interface set or a non-ACI–based
dynamic interface set. The subscriber sessions belonging to the interface set can be dynamic VLAN, DHCP,
or PPPoE subscriber interfaces.
To apply RADIUS CoS traffic-shaping attributes to both the dynamic interface set and its member subscriber
sessions, you must configure two traffic-control profiles in the dynamic profile for the subscriber interface:
one traffic-control profile for the “parent” dynamic interface set, and a second traffic-control profile for
the dynamic subscriber interfaces. RADIUS tag values for the Junos OS CoS traffic-shaping predefined
variables used in these traffic-control-profiles must be in the 100s range, as described in
Table 23 on page 230.
To accommodate this feature, the set of existing $junos-cos-parameter predefined dynamic variables for
traffic shaping have been duplicated and assigned a tag value in the 100s range, as listed in
Table 23 on page 230. The tag value is the only difference between the existing predefined dynamic variables
and the predefined dynamic variables that you must use with this feature.
For example, the existing $junos-cos-shaping-rate predefined variable is assigned RADIUS vendor ID
4874, attribute number 108, and tag value 2. To apply RADIUS CoS traffic-shaping attributes to the
dynamic interface set and its member subscriber sessions, you must instead use the $junos-cos-shaping-rate
predefined variable that is assigned RADIUS vendor ID 4874, attribute number 108, and tag value 102.
Table 23 on page 230 describes the Junos OS predefined dynamic variables and RADIUS tag values that
you can use in a dynamic profile to apply RADIUS CoS traffic-shaping attributes to the dynamic interface
set and its member subscriber sessions. The table lists the predefined dynamic variables in ascending order
by tag value.
NOTE: All of the predefined variables listed in Table 23 on page 230 use RADIUS vendor ID 4874
and RADIUS attribute value 108.
Table 23: Junos OS CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets
RADIUS Tag
Predefined Variable Value Description
$junos-cos-scheduler-map 101 Scheduler-map name configured in a

traffic-control profile in a dynamic profile.
$junos-cos-shaping-rate 102 Shaping rate configured in a traffic-control

profile in a dynamic profile. Represents the
maximum bandwidth of a CoS scheduler
node.
231
Table 23: Junos OS CoS Traffic Shaping Predefined Variables for Dynamic Interface Sets (continued)
RADIUS Tag
$junos-cos-guaranteed-rate 103 Guaranteed rate configured in a

Represents the minimum bandwidth of a
CoS scheduler node.
$junos-cos-delay-buffer-rate 104 Delay-buffer rate configured in a

$junos-cos-excess-rate 105 Excess rate configured in a traffic-control

profile in a dynamic profile; scheduler
weighting when operating in the excess
region between the guranteed rate and the
shaping rate.
NOTE: Do not configure the

$junos-cos-excess-rate variable when
either the $junos-cos-excess-rate-high
variable or the $junos-cos-excess-rate-low
variable is configured.
$junos-cos-traffic-control-profile 106 Traffic-control profile configured in a

dynamic profile for subscriber access.
$junos-cos-shaping-mode 107 Overhead-accounting mode configured in

a traffic-control profile in a dynamic profile
to shape downstream ATM traffic based
on either frames (frame-mode) or cells
(cell-mode).
$junos-cos-byte-adjust 108 Byte adjustment value for the cell or frame

shaping mode configured in a

$junos-cos-byte-adjust variable when
either the $junos-cos-byte-adjust-frame
variable or the $junos-cos-byte-adjust-cell
variable is configured.
232
RADIUS Tag
$junos-cos-adjust-minimum 109 Minimum adjusted shaping rate configured

in a traffic-control profile for a dynamic
subscriber interface. Specifying this
variable in a traffic-control profile for a
dynamic interface set has no effect.
$junos-cos-excess-rate-high 110 Shaping rate configured for excess

high-priority traffic in a traffic-control
profile in a dynamic profile.

$junos-cos-excess-rate-high variable when
the $junos-cos-excess-rate variable is
configured.
$junos-cos-excess-rate-low 111 Shaping rate configured for excess

low-priority traffic in a traffic-control
profile in a dynamic profile.

$junos-cos-excess-rate-low variable when
the $junos-cos-excess-rate variable is
configured.
$junos-cos-shaping-rate-burst 112 Burst size for the shaping rate configured

in a traffic-control profile in a dynamic
profile.
$junos-cos-guaranteed-rate-burst 113 Burst size for the guaranteed rate

configured in a traffic-control profile in a
dynamic profile.
$junos-cos-byte-adjust-frame 114 Overhead bytes when downstream ATM

traffic is in frame-mode.

$junos-cos-byte-adjust-frame variable
when the $junos-cos-byte-adjust variable
is configured.
233
RADIUS Tag
$junos-cos-byte-adjust-cell 115 Overhead bytes when downstream ATM

traffic is in cell-mode.

$junos-cos-byte-adjust-cell variable when
the $junos-cos-byte-adjust variable is
configured.
$junos-cos-shaping-rate-priority-high 116 Shaping rate configured for high-priority

traffic in a traffic-control profile for a
dynamic interface set or dynamic ACI
interface set at a household level.
Specifying this variable in a traffic-control
profile for a dynamic subscriber interface
is prohibited.
$junos-cos-shaping-rate-priority-high-burst 117 Shaping rate burst size configured for

profile for a dynamic interface set or
dynamic ACI interface set at a household
level. Specifying this variable in a
traffic-control profile for a dynamic
subscriber interface is prohibited.
$junos-cos-shaping-rate-priority-medium 118 Shaping rate configured for

medium-priority traffic in a traffic-control
$junos-cos-shaping-rate-priority-medium-burst 119 Shaping rate burst size configured for

medium-priority traffic in a traffic-control
234
RADIUS Tag
$junos-cos-shaping-rate-priority-low 120 Shaping rate configured for low-priority

traffic in a traffic-control profile for a
dynamic interface set or dynamic ACI
interface set at a household level.
Specifying this variable in a traffic-control
profile for a dynamic subscriber interface
is prohibited.
$junos-cos-shaping-rate-priority-low-burst 121 Shaping rate burst size configured for

$junos-cos-shaping-rate-excess-high 122 Shaping rate configured for excess

$junos-cos-shaping-rate-excess-high-burst 123 Shaping rate burst size configured for

excess high-priority traffic in a
interface set or dynamic ACI interface set
at a household level. Specifying this
dynamic subscriber interface is prohibited.
$junos-cos-shaping-rate-excess-low 124 Shaping rate configured for excess

235
RADIUS Tag
$junos-cos-shaping-rate-excess-low-burst 125 Shaping rate burst size configured for

excess low-priority traffic in a
interface set or dynamic ACI interface set
at a household level. Specifying this
dynamic subscriber interface is prohibited.
Overview | 221
Example: Configuring Dynamic Hierarchical Scheduling for Subscribers
In this example, subscribers are provided with a data and voice service defined in an access profile when
they initially log in. The RADIUS administrator supplies the initial values on the RADIUS server, and the
service activation is performed at subscriber login.
After the initial login, the subscriber adds an assured forwarding service that is not defined in the original
access profile. A service profile is used to configure the schedulers and a RADIUS CoA activates the service.
The queues defined for the schedulers in the initial scheduler map and the new scheduler map are merged.
In addition, the values for the initial data and voice service are upgraded by the RADIUS administrator
through a separate RADIUS CoA message.
To configure the initial service and enable the activation through a RADIUS CoA:
1. Configure the access profile for the service activation.
a. Configure the VLAN interface for the access profile.

236
[edit]
dynamic-profiles access-profile {
interfaces {
family inet;
}
}
}
}
b. Configure the class of service parameters in the access profile. In this example, you configure Junos
OS predefined variables that provide the initial scheduler name and scheduler parameters obtained
from the RADIUS authentication server when the subscriber logs in.
Include the configurations for the interfaces, schedulers, and the scheduler maps.
[edit]
dynamic-profiles access-profile {
class-of-service {
tcp1 {
scheduler-map $junos-cos-scheduler-map;
guaranteed-rate $junos-cos-guaranteed-rate;
delay-buffer-rate $junos-cos-delay-buffer-rate;
}
}
interfaces {
classifiers {
ieee-802.1 l2_classifier;
}
rewrite-rules {
ieee-802.1 l2_rewrite;
}
output-traffic-control-profile tcp1;
}
}
}
schedulers {
$junos-cos-scheduler {
buffer-size percent $junos-cos-scheduler-bs;
237
priority $junos-cos-scheduler-pri;
transmit-rate percent $junos-cos-scheduler-tx;
drop-profile-map loss-priority low protocol any $junos-cos-scheduler-low;
drop-profile-map loss-priority medium-low protocol any $junos-cos-scheduler-medium-low;
drop-profile-map loss-priority medium-high protocol any $junos-cos-scheduler-medium-high;
drop-profile-map loss-priority high protocol any $junos-cos-scheduler-high;
}
}
scheduler-maps {
data_voice_smap {
}
}
}
}
Table 24 on page 237 lists the initial values defined by the RADIUS administrator for the scheduler
map and shaping rates.
Table 24: Initial Scheduler Map and Shaping Values at Subscriber Login
Predefined Variable RADIUS Tag Value
$junos-cos-scheduler-map T01 data_voice_smap
$junos-cos-shaping-rate T02 6m
$junos-cos-guaranteed-rate T03 4m
$junos-cos-delay-buffer-rate T04 4m
Table 25 on page 237 lists the initial values defined by the RADIUS administrator for the voice
(expedited forwarding) scheduler.
Table 25: Initial CoS Values for the Voice Scheduler at Subscriber Login
Predefined Variable Tag Value
$junos-cos-scheduler — ef_sch
$junos-cos-scheduler-tx T01 10
$junos-cos-scheduler-bs T02 10
$junos-cos-scheduler-pri T03 medium-high

238
Table 25: Initial CoS Values for the Voice Scheduler at Subscriber Login (continued)
$junos-cos-scheduler-dropfile-low T04 d3
$junos-cos-scheduler-dropfile-medium-low T05 d2
$junos-cos-scheduler-dropfile-medium-high T06 d1
$junos-cos-scheduler-dropfile-high T07 d0
Table 26 on page 238 lists the initial values defined by the RADIUS administrator for the data (best
effort) scheduler.
Table 26: Initial CoS Values for the Data Scheduler at Subscriber Login
$junos-cos-scheduler — be_sch
$junos-cos-scheduler-pri T03 low
2. Configure the classifiers, drop profiles, forwarding classes, and rewrite rules in the static [edit
class-of-service] hierarchy.
[edit]
class-of-service {
classifiers {
239
dscp dscp_classifier {
}
loss-priority medium-low code-points 000001;
}
}
ieee-802.1 l2_classifier {
}
}
}
}
}
drop-profiles {
d0 {
fill-level 25 drop-probability 100;
}
d1 {
}
d2 {
}
d3 {
}
}
queue 0 be;
queue 1 ef;
queue 2 af;
queue 3 nc;
}
240
interfaces {
ge-1/2/9 {
shaping-rate 100m;
}
}
rewrite-rules {
ieee-802.1 l2_rewrite {
loss-priority medium-low code-point 000;
}
}
}
dscp l2_rewrite {
}
}
}
}
}
3. Configure the service profile enable RADIUS to activate the video service after login. The video service
corresponds to assured forwarding PHB.
In this example, you configure Junos OS predefined variables that provide the initial scheduler name
and scheduler parameters obtained from the RADIUS authentication server when the subscriber logs
in.
[edit]
dynamic-profiles service-af {
variables {
af_fc default-value video;
af_sch default-value af_sch;
sch-drop-any default-value all;
sch-pri-2 default-value strict-high;
sch-bs-2 default-value 40;
241
sch-tx-2 default-value 3m;

smap default-value any
}
class-of-service {
scheduler-maps {
"$smap" {
forwarding-class “$af_fc” scheduler “$af_sch”;
}
}
schedulers {
"$af_sch" {
transmit-rate percent "$sch-tx-2";
buffer-size percent "$sch-bs-2";
priority "$sch-pri-2";
drop-profile-map loss-priority any protocol any drop-profile “$sch-drop-any”;
}
}
}
}
After the three services are activated, subscribers receive upgraded values for the data and voice service
when RADIUS sends a change of authorization (CoA). In this case, the CoS parameters are replaced, because
multiple subscribers were not enabled on the logical interface.
Table 27 on page 241 lists the upgraded values defined by the RADIUS administrator.
Table 27: Upgraded CoS Values for the Video Service
Variable RADIUS Tag Value
junos-cos-scheduler-map T01 data_voice_smap
junos-cos-shaping-rate T02 14m
junos-cos-guaranteed-rate T03 13m
junos-cos-delay-buffer-rate T04 12m
Table 28 on page 242 lists the values defined by the RADIUS administrator for the video (assured forwarding)
scheduler.
242
Table 28: Upgraded CoS Values for the Video Scheduler
$junos-cos-scheduler — af_sch
$junos-cos-scheduler-pri T03 medium
Table 29 on page 242 lists the values defined by the RADIUS administrator for the expedited forwarding
scheduler in the CoA message. The values are the same as the initial service.
Table 29: Initial CoS Values for the Expedited Forwarding Scheduler at Subscriber Login
$junos-cos-scheduler — ef_sch
$junos-cos-scheduler-pri T03 medium-high
Table 30 on page 243 lists the values defined by the RADIUS administrator for the best effort scheduler in
the CoA message. The values are the same as the initial service.
243
Table 30: Initial CoS Values for the Best Effort Scheduler at Subscriber Login
$junos-cos-scheduler — be_sch
$junos-cos-scheduler-pri T03 low

3 PART
Configuration Statements and

Operational Commands
Configuration Statements | 245
Operational Commands | 563

245
CHAPTER 10
Configuration Statements
IN THIS CHAPTER
accept | 250
address-assignment (Address-Assignment Pools) | 252
authentication (DHCP Local Server) | 255
authentication (DHCP Relay Agent) | 257
authentication-order | 259
auto-configure | 261
adjust-minimum | 263
adjust-percent | 264
atm-service | 265
buffer-size (Schedulers) | 266
cbr | 268
classifiers (Definition) | 270
classifiers (Logical Interface) | 272
classifiers (Physical Interface) | 273
code-points (CoS) | 274
delay-buffer-rate | 276
demux0 (Dynamic Interface) | 278
demux-options (Dynamic Interface) | 280
demux-source (Dynamic IP Demux Interface) | 281
demux-source (Dynamic Underlying Interface) | 282
demux-source (Underlying Interface) | 283
dhcp-attributes (Address-Assignment Pools) | 284
dhcp-local-server | 291
dhcp-relay | 308
drop-probability (Interpolated Value) | 327
drop-probability (Percentage) | 328
drop-profile (Schedulers) | 329
drop-profile-map (Schedulers) | 330

246
drop-profiles | 331
dscp (CoS Classifiers) | 332
dynamic-profile (DHCP Local Server) | 337
dynamic-profile (VLAN) | 339
dynamic-profiles | 340
excess-bandwidth-share | 356
excess-priority | 358
excess-rate (Dynamic Traffic Shaping) | 360
excess-rate-high (Dynamic Traffic Shaping) | 362
excess-rate-low (Dynamic Traffic Shaping) | 364
family | 366
family (Address-Assignment Pools) | 372
family (Dynamic Demux Interface) | 374
family (Dynamic PPPoE) | 376
family (Dynamic Standard Interface) | 378
fill-level (Drop Profiles) | 380
fill-level (Interpolated Value) | 381
filter (Configuring) | 382
forwarding-classes (Class-of-Service) | 385
group (DHCP Local Server) | 386
guaranteed-rate | 392
ieee-802.1ad | 397
inet-precedence (CoS Classifiers) | 398
input-excess-bandwidth-share | 399
input-shaping-rate (Physical Interface) | 404
247
input-traffic-control-profile-remaining | 406
interface (DHCP Local Server) | 407
interface-set (Ethernet Interfaces) | 410
interface-set (IP Demux Interfaces) | 412
interfaces | 413
interfaces (CoS) | 415
interfaces (Static and Dynamic Subscribers) | 418
internal-node | 425
interpolate | 426
loss-priority (BA Classifiers) | 427
loss-priority (Scheduler Drop Profiles) | 428
max-queues | 430
max-queues-per-interface | 432
member-link-scheduler | 434
overhead-accounting | 441
pap (Dynamic PPP) | 442
peak-rate | 443
per-unit-scheduler | 444
pool (Address-Assignment Pools) | 446
pppoe-options (Dynamic PPPoE) | 448
ppp-options (Dynamic PPP) | 449
priority (Schedulers) | 452
profile (Access) | 454
protocols | 461
proxy-arp | 465
queue (Global Queues) | 468
radius (Access Profile) | 469
radius-server | 473
range (Address-Assignment Pools) | 479

248
ranges (Dynamic VLAN) | 480
rewrite-rules (Interfaces) | 482
routing-instances (Multiple Routing Entities) | 484
scheduler (Scheduler Map) | 486
scheduler-map (Interfaces and Traffic-Control Profiles) | 487
scheduler-maps (For Most Interface Types) | 488
schedulers (CoS) | 489
secret (RADIUS) | 491
server (Dynamic PPPoE) | 492
server-group | 493
shaping-rate (Applying to an Interface) | 495
shaping-rate (Schedulers) | 498
shaping-rate (Oversubscribing an Interface) | 500
shared-bandwidth-policer (Configuring) | 512
shared-instance | 513
shared-scheduler | 514
simple-filter | 516
site-identifier (VPLS) | 518
stacked-interface-set (Dynamic Profiles) | 519
term (Simple Filter) | 522
three-color-policer (Applying) | 524
three-color-policer (Configuring) | 525
transmit-rate (Schedulers) | 535
transparent | 537
249
underlying-interface (demux0) | 538
underlying-interface (Dynamic PPPoE) | 540
unit | 541
unit (Dynamic Demux Interface) | 543
unit (Dynamic PPPoE) | 545
unnumbered-address (Dynamic PPPoE) | 547
unnumbered-address (Dynamic Profiles) | 548
unnumbered-address (Ethernet) | 550
user-prefix (DHCP Relay Agent) | 551
vlan-id (Dynamic Profiles) | 553
vlan-id (VLAN ID to Be Bound to a Logical Interface) | 554
vlan-model | 555
vlan-ranges | 556
vlan-tag | 558
vlan-tags | 559
vlan-tags-outer | 560
vlan-tags (Stacked VLAN Tags) | 561

250
accept
Syntax
accept (any | dhcp-v4 | dhcp-v6 | inet | inet6 | pppoe);
Hierarchy Level
[edit interfaces interface-name auto-configure stacked-vlan-ranges dynamic-profile profile-name],

[edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name]
Release Information
Statement introduced in Junos OS Release 9.5.
dhcp-v4 option added in Junos OS Release 10.0.
dhcp-v6, inet6 and pppoe options added in Junos OS Release 10.2.
any option added in Junos OS Release 10.4.
Description
Specify the type of VLAN Ethernet packet accepted by an interface that is associated with a VLAN dynamic
profile or stacked VLAN dynamic profile.
Options
any—Any packet type. Specifies that any incoming packets trigger the dynamic creation of a VLAN with
properties determined by the auto-configure interface configuration stanza and associated profile attributes.
This option is used when configuring wholesaling in a Layer 2 network.
dhcp-v4—IPv4 DHCP packet type. Specifies that incoming IPv4 DHCP discover packets trigger the dynamic
creation of a VLAN with properties determined by the auto-configure interface configuration stanza and
associated profile attributes
NOTE: The DHCP-specific mac-address and option-82 options are rejected if the accept
statement is not set to dhcp-v4.
dhcp-v6—IPv6 DHCP packet type. Specifies that incoming IPv6 DHCP discover packets trigger the dynamic
creation of a VLAN with properties determined by the auto-configure interface configuration stanza and
associated profile attributes.
inet—IPv4 Ethernet and ARP packet type.
inet6—IPv6 Ethernet packet type.
pppoe—Point-to-Point Protocol over Ethernet packet type.

251
NOTE: The pppoe VLAN Ethernet packet type option is supported only for MPC/MIC interfaces.
Required Privilege Level

interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs
Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs
Configuring VLAN Interfaces for the Layer 2 Wholesale Solution
Configuring Subscriber Packet Types to Trigger VLAN Authentication
252
address-assignment (Address-Assignment Pools)

Syntax
address-assignment {
abated-utilization percentage;
abated-utilization-v6 percentage;
high-utilization percentage;
high-utilization-v6 percentage;
neighbor-discovery-router-advertisement ndra-pool-name;
pool pool-name {
active-drain;
family family {
dhcp-attributes {
protocol-specific attributes;
}
excluded-address ip-address;
excluded-range name low minimum-value high maximum-value;
host hostname {
hardware-address mac-address;
ip-address ip-address;
}
network ip-prefix/<prefix-length>;
prefix ipv6-prefix;
range range-name {
high upper-limit;
low lower-limit;
prefix-length prefix-length;
}
}
hold-down;
link pool-name;
}
}
Hierarchy Level
[edit access]
Release Information
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Description
253
Configure address-assignment pools that can be used by different client applications.
NOTE: Support for subordinate statements is platform-specific. See individual statement topics
for support information.
Options
abated-utilization—(ACX Series, MX Series only) Starting in Junos OS Release 11.2, generate SNMP traps
for DHCP address pools or linked set of address pools. No SNMP traps are generated unless a value
is configured. Default: Abated utilization is not set. Delete the abated-utilization value to unset.
Values: percentage—Threshold below which an SNMP trap clear is generated. Range: 1 through 98.
abated-utilization-v6—(ACX Series, MX Series only) Starting in Junos OS Release 11.2, generate SNMP
traps for DHCPv6 address pools or linked set of address pools. No SNMP traps are generated unless
a value is configured. Default: Abated utilization is not set. Delete the abated-utilization value to unset.
Values: percentage—Threshold below which an SNMP trap clear is generated. Range: 1 through 98.
high-utilization—(ACX Series, MX Series only) Starting in Junos OS Release 11.2, generate an SNMP trap
when the DHCP address pool or linked set of address pools use surpasses the specified percentage.
Default: High utilization is not set. Delete the high-utilization value to unset.
Values: percentage—Percentage used to generate a trap. Range: 2 through 99.
high-utilization-v6—(ACX Series, MX Series only) Starting in Junos OS Release 11.2, generate an SNMP
trap when the DHCPv6 address pool or linked set of address pools use surpasses the specified
percentage. Default: High utilization is not set. Delete the high-utilization value to unset.
Values: percentage—Percentage used to generate a trap. Range: 2 through 99.
neighbor-discovery-router-advertisement—(M Series, MX Series, SRX Series, T Series only) Configure the

name of the address-assignment pool used to assign the router advertisement prefix.
Values: ndra-pool-name—Name of the address-assignment pool.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked
statement in the Syntax section for details.

admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
254
Address-Assignment Pools Overview

Address-Assignment Pool Configuration Overview
Configuring an Address-Assignment Pool for L2TP LNS with Inline Services
Configuring Address-Assignment Pool Usage Threshold Traps
Configuring an Address-Assignment Pool Used for Router Advertisements
255
authentication (DHCP Local Server)

Syntax
authentication {
password password-string;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-interface);
interface-name ;
logical-system-name;
mac-address;
option-60;
option-82 <circuit-id> <remote-id>;
relay-agent-interface-id;
relay-agent-remote-id;
relay-agent-subscriber-id;
routing-instance-name;
user-prefix user-prefix-string;
vlan-tags;
}
}
Hierarchy Level
[edit system services dhcp-local-server],

[edit system services dhcp-local-server dual-stack-group dual-stack-group-name],
[edit system services dhcp-local-server dhcpv6],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit system services dhcp-local-server group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name system services dhcp-local-server
...],
[edit logical-systems logical-system-name system services dhcp-local-server ...],
[edit routing-instances routing-instance-name system services dhcp-local-server ...]
Release Information
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Description
256
Configure the parameters the router sends to the external AAA server. A group configuration takes
precedence over a global DHCP relay or DHCP local server configuration.

system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Specifying Authentication Support

257
authentication (DHCP Relay Agent)

Syntax
authentication {
username-include {
circuit-type;
client-id;
interface-name;
mac-address;
option-60;
vlan-tags;
}
}
Hierarchy Level
[edit forwarding-options dhcp-relay],

[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwarding-options dhcp-relay group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay
...],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay ...]
Release Information
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1.
258
Description
Configure the parameters the router sends to the external AAA server. A group configuration takes
precedence over a global DHCP relay configuration. Use the statement at the [edit...dhcpv6] hierarchy
levels to configure DHCPv6 support.

dhcp-relay | 308
259
authentication-order
Syntax
authentication-order [ authentication-methods ];
Hierarchy Level
[edit access profile profile-name]
Release Information
Statement introduced before Junos OS Release 7.4.
none option added in Junos OS Release 11.2.
nasreq option added in Junos OS Release 16.1.
s6a option added in Junos OS Release 19.3R1.
Description
Set the order in which AAA tries different authentication methods when verifying that a client can access
the router or switch. For each login attempt, AAA tries the authentication methods in order, from first to
last.
A given subscriber does not undergo both authentication and authorization as separate steps. When both
authentication-order and authorization-order are specified, DHCP subscribers honor the configured
authorization order, all other subscribers use the configured authentication-order.
Starting in Junos OS Release 18.2R1, the password option can also be used to specify that local
authentication and local authorization is attempted for individual subscribers that are configured with the
subscriber statement at the [edit access profile profile-name] hierarchy level.
Options
authentication-methods—Ordered list of methods to use for authentication attempts. The list includes one
or more of the following methods in any combination:
• nasreq—Verify subscribers using the Diameter-based Network Access Server Requirements (NASREQ)
protocol.
• none—No authentication is performed. Grants authentication without examining the client credentials.
Can be used, for example, when the Diameter function Gx-Plus is employed for notification during
subscriber provisioning.
260
NOTE: Subscriber access management does not support the none option; authentication
fails when this option is specified.
• password—Verify the client using the information configured at the [edit access profile profile-name
client client-name] hierarchy level.
Subscriber access management does not support the password option until Junos OS Release 18.2R1.
Starting in Junos OS Release 18.2R1, this option is used to enable local authentication and optionally
local authorization for individual subscribers. Local authentication is typically used when you do not
have external authentication and authorization servers. The password itself must be configured with
the subscriber statement in the same access profile. Local authentication is performed when a
subscriber logs in with a matching username; it succeeds if the subscribers login password matches
the password in the profile.
If you have external authentication and authorization servers, you can use local authentication as a
backup authentication method. In this case, configure password other than first in the list of methods.
• radius—Verify the client using RADIUS authentication services.
• s6a—Verify subscribers using the Diameter-based s6a protocol.
Default: password

Example: Configuring CHAP Authentication with RADIUS

Specifying the Authentication and Accounting Methods for Subscriber Access
Configuring Access Profiles for L2TP or PPP Parameters
Configuring Local Authentication and Authorization for Subscribers
Example: Configure S6a Application
261
auto-configure
Syntax
auto-configure {
vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
username-include{
circuit-id;
circuit-type;
interface-name;
mac-address;
option-18;
option-37;
radius-realm radius-realm-string;
remote-id;
vlan-tags;
}
}
dynamic-profile profile-name {
accept-out-of-band protocol;
ranges (any | low-tag)–(any | high-tag);
}
override;
}
stacked-vlan-ranges {
authentication {
username-include {
circuit-type;
interface-name;
mac-address;
option-18;
262
option-37;
vlan-tags;
}
}
ranges (any | low-tag–high-tag),(any | low-tag–high-tag);
}
override;
}
remove-when-no-subscribers;
}
Hierarchy Level
Release Information
Description
Enable the configuration of dynamic, auto-sensed VLANs.

Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs
263
adjust-minimum
Syntax
adjust-minimum rate;
Hierarchy Level
[edit class-of-service schedulers scheduler-name],

[edit class-of-service traffic-control-profiles traffic-control-profile-name]
Release Information
Description
For adjustments performed by the ANCP or multicast applications on EQ DPC, MIC, or MPC interfaces,
specify the minimum shaping rate for an adjusted scheduler node. The node is associated with a
traffic-control profile.
For adjustments performed by the multicast application on MIC or MPC interfaces, specify the minimum
shaping rate for an adjusted queue. The queue is associated with a scheduler.
Options
rate—Minimum shaping rate for a node or a queue, in Mbps

264
adjust-percent
Syntax
adjust-percent percentage;
Hierarchy Level
Release Information
Description
For a MIC or MPC interface, determine the percentage of adjustment for the shaping rate of a queue.
Options
percentage—Percentage of the shaping rate to adjust.
Range: 0 through 100 percent


265
atm-service
Syntax
atm-service (cbr | rtvbr| nrtvbr);
Hierarchy Level

[edit firewall atm-policer atm-policer-name]
Release Information
Description
(MX Series routers) Configure the ATM service category on ATM MICs to define bandwidth shaping and
utilization. Shaping is based on the ATM service category.
Default
If the ATM service category is not specified, bandwidth utilization is unlimited.
Options
cbr—Use the constant bit rate.
nrtvbr—Use the non real-time variable bit rate.
rtvbr—Use the real-time variable bit rate.
NOTE: (MX Series with MPCs and ATM MICs with SFP) To configure up to OC12 CBR bandwidth
speed per virtual circuit (VC) on an ATM MIC with SFP (MIC-3D-8OC3-2OC12-ATM), specify
cbr as the ATM service category.

show class-of-service traffic-control-profile

266
buffer-size (Schedulers)
Syntax
buffer-size (percent percentage | remainder | shared | temporal microseconds);
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport Routers.
Statement introduced in Junos OS Release 12.2 for ACX Series Routers.
shared option introduced in Junos OS Release 18.1 for PTX Series Packet Transport Routers.
Description
Specify buffer size.
NOTE: On PTX Series Packet Transport Routers, buffer-size cannot be configured on rate-limited
queues.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent, respectively.
Options
percent percentage—Buffer size as a percentage of the total buffer.
Range: 0 through 100
NOTE: For the routers with channelized OC12/STM4 IQE PIC with SFP
(PB-4CHOC12-STM4-IQE-SFP) and channelized OC48/STM16 IQE PIC with SFP
(PB-1CHOC48-STM16-IQE-SFP), the minimum buffer allocated to any queue is 18,432 bytes.
If a queue is configured to have a buffer size less than 18K, the queue retains a buffer size of
18,432 bytes.
remainder—Remaining buffer available.

267
shared—On PTX Series routers, set a queue’s buffer to be up to 100 percent of the interface’s buffer. This
option allows the queue’s buffer to grow as large as 100 percent of the interface's buffer if and only if it
is the only active queue for the interface.
temporal microseconds—Buffer size as a temporal value. The queuing algorithm starts dropping packets
when it queues more than a computed number of bytes. This maximum is computed by multiplying the
logical interface speed by the configured temporal value.
Range: The ranges vary by platform as follows:
• For SRX Series Services Gateways: 1 through 2,000,000 microseconds.
• For vSRX instances: 1 through 32,000,000 microseconds.

Managing Congestion on the Egress Interface by Configuring the Scheduler Buffer Size
Buffer Size Temporal Value Ranges by Router Type
268
cbr
Syntax
cbr rate;
Hierarchy Level
[edit interfaces at-fpc/pic/port atm-options vpi vpi-identifier shaping],

[edit interfaces at-fpc/pic/port unit logical-unit-number address address family family
multipoint-destination address shaping],
[edit interfaces at-fpc/pic/port unit logical-unit-number shaping],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number address address family
family multipoint-destination address shaping],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number shaping]
Release Information
Description
For ATM encapsulation only, define a constant bit rate bandwidth utilization in the traffic-shaping profile.
Default
Unspecified bit rate (UBR); that is, bandwidth utilization is unlimited.
Options
rate—Peak rate, in bits per second (bps) or cells per second (cps). You can specify a value in bits per second
either as a complete decimal number or as a decimal number followed by the abbreviation k (1000),
m (1,000,000), or g (1,000,000,000). You can also specify a value in cells per second by entering a
decimal number followed by the abbreviation c; values expressed in cells per second are converted
to bits per second by means of the formula 1 cps = 384 bps.
For ATM1 and ATM2 OC3 interfaces, the maximum available rate is 100 percent of line-rate, or
135,600,000 bps. For ATM1 OC12 interfaces, the maximum available rate is 50 percent of line-rate,
or 271,263,396 bps. For ATM2 IQ interfaces, the maximum available rate is 542,526,792 bps.

269
Defining the ATM Traffic-Shaping Profile Overview

rtvbr
shaping
vbr
270
classifiers (Definition)
Syntax
classifiers {
type classifier-name {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level code-points [ aliases ] [ bit-patterns ];
}
}
}
Hierarchy Level
[edit class-of-service],
[edit class-of-service routing-instances routing-instance-name]
Release Information
ieee-802.1ad option introduced in Junos OS Release 9.2.
Description
Define a CoS behavior aggregate (BA) classifier for classifying packets. You can associate the classifier
with a forwarding class or code-point mapping, and import a default classifier or one that is previously
defined.
NOTE: The [edit class-of-service routing-instances routing-instance-name] hierarchy level and

the dscp-ipv6 and ieee-802.1ad classifier types are not supported on ACX Series routers.
Options
classifier-name—Name of the aggregate behavior classifier.
type—Traffic type: dscp, dscp-ipv6, exp, ieee-802.1, ieee-802.1ad, inet-precedence.

271
Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic

272
classifiers (Logical Interface)

Syntax
classifiers {
type (classifier-name | default) family (mpls | inet);
no-default;
}
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 14.2 for PTX Series Packet Transport Routers.
no-default option added for MX Series devices only in Junos OS Release 16.1.
Description
Apply a CoS aggregate behavior classifier to a logical interface. You can apply a default classifier or one
that is previously defined.
On MX Series devices, if you do not explicitly apply a classifier configuration to the interface, the default
classifier is applied to the interface. Apply the no-default option to disable the application of any default
classifier to the routing instance.
Options
type—Traffic type.
Values: dscp, dscp-ipv6, exp, ieee-802.1, inet-precedence
NOTE: You can only specify a family for the dscp and dscp-ipv6 types.

273
Default DSCP and DSCP IPv6 Classifiers

Applying Behavior Aggregate Classifiers to Logical Interfaces
classifiers (Physical Interface)

Syntax
classifiers {
type (classifier-name | default) ;
}
Hierarchy Level
[edit class-of-service interfaces interface-name ]
Release Information
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Metro routers.
Description
Apply a CoS aggregate behavior classifier to a physical interface. You can apply a default classifier or one
that is previously defined.
Options
Values: dscp, ieee-802.1, and inet-precedence

dscp
inet-precedence
ieee-802.1
274
code-points (CoS)
Syntax
code-points ([ aliases ] | [ bit-patterns ]);
Hierarchy Level
[edit class-of-service classifiers type classifier-name forwarding-class class-name loss-priority level]
Release Information
Statement introduced in Junos OS Release 9.2 for SRX Series devices.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 12.1X44 for the SRX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description
Specify one or more DSCP code-point aliases or bit sets to apply to a forwarding class..
NOTE: OCX Series switches do not support MPLS, and therefore, do not support EXP code
points or code point aliases.
Options
aliases—Name of the DSCP alias.
bit-patterns—Value of the code-point bits, in six-bit binary form.

Understanding Interfaces
Example: Configuring Behavior Aggregate Classifiers
275
Example: Configuring BA Classifiers on Transparent Mode Security Devices

276
delay-buffer-rate
Syntax
Hierarchy Level
Release Information
Description
For Gigabit Ethernet IQ, Channelized IQ PICs, and FRF.15 and FRF.16 LSQ interfaces only, base the
delay-buffer calculation on a delay-buffer rate.
Default
If you do not include this statement, the delay-buffer calculation is based on the guaranteed rate if one is
configured, or the shaping rate if no guaranteed rate is configured. For more information, see Bandwidth
and Delay Buffer Allocations by Configuration Scenario.
Options
percent percentage—For LSQ interfaces, delay-buffer rate as a percentage of the available interface
bandwidth.
rate—For IQ and IQ2 interfaces, delay-buffer rate, in bits per second (bps). You can specify a value in bits
per second either as a complete decimal number or as a decimal number followed by the abbreviation
k (1000), m (1,000,000), or g (1,000,000,000).
Range: 1000 through 6,400,000,000,000 bps
NOTE: Through Junos OS Release 13.3, the upper limit is 160,000,000,000 bps. Beginning with
Junos OS Release 14.1, the upper limit is 6,400,000,000,000 bps.

277

278
demux0 (Dynamic Interface)

Syntax
demux0 {
unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
address address;
demux-source {
source-prefix;
}
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
input filter-name;
output filter-name;
}
mac-validate (loose | strict):
max-sessions number;
max-sessions-vsa-ignore;
rpf-check {
fail-filter filter-name;
mode loose;
}
service-name-table table-name
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max maximum-seconds>;
unnumbered-address interface-name <preferred-source-address address>;
}
filter {
input filter-name;
output filter-name;
}
vlan-id number;
}
}
Hierarchy Level

279
Release Information
Description
Configure the logical demultiplexing (demux) interface in a dynamic profile.
Logical IP demux interfaces do not support IPv4 and IPv6 dual stack.

Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles

Demultiplexing Interface Overview
280
demux-options (Dynamic Interface)

Syntax
demux–options {
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces demux0 interface-name unit logical-unit-number]
Release Information
Description
Configure logical demultiplexing (demux) interface options in a dynamic profile.


281
demux-source (Dynamic IP Demux Interface)

Syntax
demux-source {
source-address;
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family]
Release Information
Description
Configure a logical demultiplexing (demux) source address for a subscriber in a dynamic profile.
Options
source-address—Either the specific source address you want to assign to the subscriber interface or the
source address variable. For IPv4, specify $junos-subscriber-ip-address; for IPv6, specify
$junos-subscriber-ipv6-address. The source address for the interface is dynamically supplied by DHCP
when the subscriber accesses the router.


282
demux-source (Dynamic Underlying Interface)

Syntax
demux-source family;
Hierarchy Level
[edit dynamic-profiles interfaces interface-name unit logical-unit-number]
Release Information
Description
Configure the logical demultiplexing (demux) source family type on the IP demux underlying interface
within a dynamic profile.
NOTE: The IP demux interface feature currently supports only Fast Ethernet, Gigabit Ethernet,
10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces.
Options
family—Protocol family:
• inet—Internet Protocol version 4 suite
• inet6—Internet Protocol version 6 suite

283
demux-source (Underlying Interface)

Syntax
demux-source family;
Hierarchy Level
[edit interfaces interface-name unit logical-unit-number],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces interface-name unit
logical-unit-number]
Release Information
Support for aggregated Ethernet added in Junos OS Release 9.4.
Description
Configure the logical demultiplexing (demux) source family type on the IP demux underlying interface.
NOTE: The IP demux interface feature currently supports only Fast Ethernet, Gigabit Ethernet,
10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces.
Options

Configuring an IP Demultiplexing Interface

Configuring a VLAN Demultiplexing Interface
284
dhcp-attributes (Address-Assignment Pools)

Syntax
dhcp-attributes {
boot-file filename;
boot-server (address | hostname);
dns-server [ ipv6-address ];
domain-name domain-name;
exclude-prefix-len exclude-prefix-length;
grace-period seconds;
maximum-lease-time seconds;
name-server [ server-list ];
netbios-node-type node-type;
option {
[ (id-number option-type option-value)
(id-number array option-type option-value) ];
}
option-match {
option-82 {
circuit-id value range named-range;
remote-id value range named-range;
}
}
preferred-lifetime seconds;
router [ router-address ];
server-identifier ip4-address;
sip-server-address [ ipv6-address ];
sip-server-domain-name domain-name;
t1-percentage percentage;
t1-renewal-time;
t2-percentage percentage;
t2-rebinding-time;
tftp-server address;
valid-lifetime seconds;
wins-server [ servers ];
}
Hierarchy Level
[edit access address-assignment pool pool-name family family]
Release Information
285

exclude-prefix-len statement introduced in Junos OS Release 17.3 for MX Series.
Description
Configure DHCP attributes for the protocol family in a specific address pool. The attributes determine
options and behaviors for the DHCP clients.
286
Options
boot-file—(EX Series, M Series, MX Series, SRX Series, T Series only) Set the boot file advertised to DHCP
clients. After the client receives an IP address and the boot file location from the DHCP server, the
client uses the boot image stored in the boot file to complete DHCP setup. This configuration is
equivalent to DHCP option 67.
Values: filename—Location of the boot file on the boot server. The filename can include a pathname.
boot-server—(EX Series, M Series, MX Series, SRX Series, T Series only) Configure the name of the boot
server advertised to DHCP clients. The client uses a boot file located on the boot server to complete
DHCP setup. This configuration is equivalent to DHCP option 66.
Values:
• address—IPv4 address of a boot server.
• hostname—Fully qualified hostname of a boot server.
dns-server—(MX Series only) Specify a DNS server to which clients can send DNS queries. This is equivalent
to DHCPv6 option 23. To specify multiple DNS servers, add multiple dns-server statements in order
of preference.
Values: ipv6-address—IPv6 address of a DNS server.
domain-name—(EX Series, MX Series only) Configure the name of the domain in which clients search for
a DHCP server host. This is the default domain name that is appended to hostnames that are not fully
qualified. This is equivalent to DHCP option 15.
Values: domain-name—Name of the domain.
exclude-prefix-len exclude-prefix-length—Specify the length of the IPv6 prefix to be excluded from the
delegated prefix. Range: 1 through 128.
grace-period—(M Series, MX Series, SRX Series, T Series only) Configure the amount of time that the client
retains the address lease after the lease expires. The address cannot be reassigned to another client
during the grace period.
Values: seconds—Number of seconds the lease is retained.
Range: 0 through 4,294,967,295 seconds.
Default: 0 (no grace period).
maximum-lease-time—(EX Series, M120, MX Series, SRX240, SRX3400, T640, T1600 only) Specify the
maximum length of time, in seconds, that the lease is held for a client if the client does not renew the
lease. This is equivalent to DHCP option 51. The maximum-lease-time is mutually exclusive with both
the preferred-lifetime and the valid-lifetime, and cannot be configured with either timer.
Values: seconds—Maximum number of seconds the lease can be held.
Default: 86,400 (24 hours).
287
name-server—(M120, MX Series, SRX Series, T640, T1600 only) Configure one or more Domain Name
System (DNS) name servers available to the client to resolve hostname-to-client mappings. This is
equivalent to DHCP option 6.
Values: server-names—IP addresses of the domain name servers, listed in order of preference.
netbios-node-type—(M Series, MX Series, SRX Series, T Series only) Specify the NetBIOS node type. This
is equivalent to DHCP option 46.
Values: node-type—One of the following node types:
• b-node—Broadcast node.
• h-node—Hybrid node.
• m-node—Mixed node.
• p-node—Peer-to-peer node.
option—(EX Series, M Series, MX Series, SRX Series, T Series only) Specify user-defined options that are
added to client packets. Starting in Junos OS Release 13.3, the hex-string option type was introduced.
Values:
• array—An option can include an array of option types.
• id-number—Any whole number. The ID number is used to index the option and must be unique across
a DHCP server.
• option-type—Any of the following types: byte, byte-stream, flag, hex-string, integer, ip-address, short,
string, unsigned-integer, or unsigned-short.
• option-value—Value associated with an option. The option value must be compatible with the option
type (for example, an On or Off value for a flag type).
preferred-lifetime—(EX Series, M Series, MX Series only) Starting in Junos OS Release 13.3, specify the
length of time, in seconds, that the DHCPv6 server keeps the IPv6 prefix active. When the lifetime
expires, the address is deprecated. If the valid-lifetime is also configured, the preferred-lifetime must
be less than the valid-lifetime. The preferred-lifetime and the maximum-lease-time are mutually
exclusive and cannot both be configured.
Values: seconds—Number of seconds that the IPv6 prefix is active.
router—(EX Series, MX Series only) Specify one or more routers located on the client’s subnet. This
statement is the equivalent of DHCP option 3.
Values: router-address—IP address of one or more routers.
288
server-identifier—(EX Series, MX Series, SRX Series only) Specify the IP address that is used as the source
address the DHCP server includes in IP packets when communicating with clients. The address is
included in the DHCP packet in option 54.
Values: ipv4-address—IP address.
sip-server-address—(EX Series, M Series, MX Series, SRX Series, T Series only) Specify a SIP outbound
proxy server that DHCPv6 local server clients can use. This is equivalent to DHCPv6 option 22. To
specify multiple servers, add multiple sip-server-address statements in order of preference.
Values: ipv6-address—IPv6 address of a SIP outbound proxy server.
sip-server-domain-name—(M Series, MX Series, SRX Series, T Series only) Configure the domain name of
the SIP outbound proxy server that DHCPv6 local server clients can use. This is equivalent to DHCPv6
option 21.
Values: domain-name—Name of the domain.
t1-percentage—(EX Series, M Series, MX Series only) Specify a percentage of the preferred-lifetime value.
After this percentage of the preferred-lifetime value elapses, the DHCPv4 or DHCPv6 client requests
an extension on its lease from the originating DHCP local server. The t1-percentage is also referred
to as the renewal time. The t1-percentage value must be less than the t2-percentage value. DHCPv4
server support was added in Junos OS Release 17.2.
Values: percentage—Percentage of the preferred-lifetime value.
Range: 0 through 100.
Default: If the t1-percentage value is not configured, the default is based on the preferred-lifetime
value:
• If the preferred-lifetime value is finite, the default is 50 percent of the preferred-lifetime value.
• If the preferred-lifetime value is infinite, the default is also infinite.
t1-renewal-time—(MX Series only) Starting in Junos OS Release 17.2, specify the time (T1) at which the
DHCPv4 or DHCPv6 client requests an extension (renewal) of the existing lease. This time is expressed
as the number of seconds since the beginning of the lease. Using this statement to configure a duration
in seconds is an alternative to using the t1-percentage statement.
Values: seconds—Number of seconds.
Default: 50 percent of the lease duration (preferred-lifetime).
289
t2-percentage—(EX Series, M Series, MX Series only) Starting in Junos OS Release 13.3, specify a percentage
of the preferred-lifetime value. After this percentage of the preferred-lifetime value elapses, the
DHCPv4 or DHCPv6 client requests an extension on its lease from any available DHCPv4 or DHCPv6
server. The t2-percentage is also referred to as the rebinding time. The t2-percentage value must be
greater than the t1-percentage value. DHCPv4 server support was added in Junos OS Release 17.2.
Values: percentage—Percentage of the preferred-lifetime value.
Range: 0 through 100.
Default: Default: If the t2-percentage value is not configured, the default is based on the
preferred-lifetime value:
• If the preferred-lifetime value is finite, the default is 80 percent of the preferred-lifetime value.
• When the preferred-lifetime value is infinite, the default is also infinite.
t2-rebinding-time—(MX Series only) Starting in Junos OS Release 17.2, specify the time (T2) at which the
DHCPv4 or DHCPv6 client attempts to contact any DHCP server to request an extension (rebinding)
of the existing lease. This time is expressed as the number of seconds since the beginning of the lease.
Using this statement to configure a duration in seconds is an alternative to using the t2-percentage
statement.
Values: seconds—Number of seconds.
Default: The default value depends on the client:
• (DHCPv4 clients) 87.5 percent of the lease duration (preferred-lifetime).
• (DHCPv6 clients) 80 percent of the lease duration (preferred-lifetime).
tftp-server—(ACX Series, SRX Series only) Specify the Trivial File Transfer Protocol (TFTP) server that the
client uses to obtain the client configuration file. This is equivalent to DHCP option 150.
Values: ip-address—IP address of the TFTP server.
valid-lifetime—(EX Series, M Series, MX Series only) Starting in Junos OS Release 13.3, specify the length
of time, in seconds, that the DHCPv6 server keeps the IPv6 prefix valid. When the lifetime expires,
the address becomes invalid. If the preferred-lifetime is also configured, the valid-lifetime must be
greater than the preferred-lifetime. The valid-lifetime and the maximum-lease-time are mutually
exclusive and cannot both be configured.
Values: seconds—Number of seconds that the IPv6 prefix is valid.
wins-server—(M Series, MX Series, SRX Series, T Series only) Specify one or more NetBIOS name servers
(NBNS) that the client uses to resolve NetBIOS names. This is equivalent to DHCP option 44.
Values: ipv4-address—IP address of each NetBIOS name server. Add them to the configuration in
order of preference.
290


Attributes That Can Be Applied to DHCP Clients
Configuring DHCP Client-Specific Attributes Applied When Clients Obtain an Address
DHCP Lease Timers
Configuring DHCP Attributes for All Clients or a Group of Clients
291
dhcp-local-server
Syntax
dhcp-local-server {
allow-active-leasequery {
idle-timeout seconds;
peer-address address;
timeout seconds;
}
allow-bulk-leasequery {
max-connections number-of-connections;
max-empty-replies number-of-replies;
restricted-requestor;
timeout seconds;
}
allow-leasequery {
}
authentication {
username-include {
circuit-type;
interface-name ;
mac-address;
option-60;
vlan-tags;
}
}
dhcpv6 {
allow-active-leasequery {
timeout seconds;
}
allow-bulk-leasequery {
292
max-connections number-of-connections;
max-empty-replies number-of-replies;
timeout seconds;
}
allow-leasequery {
}
authentication {
...
}
duplicate-clients incoming-interface;
293
group group-name {
authentication {
...
}
exclude;
overrides {
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
delay-advertise {
based-on (option-15 | option-16 | option-18 | option-37) {
equals {
ascii ascii-string;
hexadecimal hexadecimal-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
dual-stack dual-stack-group-name;
interface-client-limit number;
multi-address-embedded-option-response;
process-inform {
pool pool-name;
}
protocol-attributes attribute-set-name;
rapid-commit;
}
service-profile dynamic-profile-name;
short-cycle-protection <lockout-min-time seconds> <lockout-max-time seconds>;
trace;
upto upto-interface-name;
}
liveness-detection {
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
294
method {
bfd {
version (0 | 1 | automatic);
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
threshold milliseconds;
}
detection-time {
}
session-mode (automatic | multihop | singlehop);
holddown-interval milliseconds;
}
layer2-liveness-detection {
max-consecutive-retries number;
transmit-interval interval;
}
}
}
295
overrides {
delay-advertise {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delegated-pool;
process-inform {
pool pool-name;
}
rapid-commit;
}
route-suppression;
server-duid-type type;
}
296
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
}
}
297
overrides {
delay-advertise {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delegated-pool;
include-option-82 {
forcerenew;
nak;
}
process-inform {
pool pool-name;
}
rapid-commit;
}
298
reconfigure {
attempts attempt-count;
clear-on-abort;
strict;
support-option-pd-exclude;
timeout timeout-value;
token token-value;
trigger {
radius-disconnect;
}
}
reauthenticate (<lease-renewal> <remote-id-mismatch >);
requested-ip-network-match subnet-mask;
route-suppression;
server-duid-type type;
}
299
dual-stack-group name {
access-profile access-profile;
authentication {
username-include {
circuit-type;
interface-name ;
mac-address;
vlan-tags;
}
}
classification-key {
circuit-id circuit-id;
mac-address mac-address;
remote-id remote-id;
}
dual-stack-interface-client-limit number;
aggregate-clients (merge | replace);
use-primary primary-profile-name;
}
method {
}
}
}
on-demand-address-allocation;
protocol-master (inet | inet6);
service-profile service-profile;
}
300
duplicate-clients-in-subnet (incoming-interface | option-82);

dynamic-profile profile-name <aggregate-clients (merge | replace) | use-primary primary-profile-name>;
forward-snooped-clients (all-interfaces | configured-interfaces | non-configured-interfaces);
301
group group-name {
authentication {
...
}
exclude;
overrides {
client-discover-match (option60-and-option82 | incoming-interface);
delay-offer {
based-on (option-60 | option-77 | option-82) {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
include-option-82 {
forcerenew;
nak;
}
process-inform {
pool pool-name;
}
}
trace;
}
302

method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
session-mode(automatic | multihop | singlehop);
}
}
}
}
303
overrides {
delay-offer {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
include-option-82 {
forcerenew;
nak;
}
process-inform {
pool pool-name;
}
}
requested-ip-network-match subnet-mask
route-suppression;
}
304
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
}
}
on-demand-address-allocation;
305
overrides {
client-discover-match <option60-and-option82 | incoming-interface>;
delay-offer {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
process-inform {
pool pool-name;
}
}
pool-match-order {
external-authority;
ip-address-first;
option-82;
}
protocol-master;
reconfigure {
clear-on-abort;
strict;
token token-value;
trigger {
radius-disconnect;
}
}
306
requested-ip-network-match subnet-mask;
route-suppression;
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name system services],

[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services],
[edit system services]
Release Information
Statement introduced in Junos OS Release 13.2X51 for the QFX Series.
Description
Configure Dynamic Host Configuration Protocol (DHCP) local server options on the router or switch to
enable the router or switch to function as an extended DHCP local server. The DHCP local server receives
DHCP request and reply packets from DHCP clients and then responds with an IP address and other
optional configuration information to the client.
The extended DHCP local server is incompatible with the DHCP server on J Series routers and, therefore,
is not supported on J Series routers. Also, the DHCP local server and the DHCP/BOOTP relay server,
which are configured under the [edit forwarding-options helpers] hierarchy level, cannot both be enabled
on the router or switch at the same time. The extended DHCP local server is fully compatible with the
extended DHCP relay feature.
The dhcpv6 stanza configures the router or switch to support Dynamic Host Configuration Protocol for
IPv6 (DHCPv6). The DHCPv6 local server is fully compatible with the extended DHCP local server and
the extended DHCP relay feature.
NOTE: When you configure the dhcp-local-server statement at the routing instance hierarchy
level, you must use a routing instance type of virtual-router.
307

Understanding Differences Between Legacy DHCP and Extended DHCP

DHCPv6 Local Server Overview
308
dhcp-relay
Syntax
dhcp-relay {
active-leasequery {
timeout seconds;
topology-discovery;
}
active-server-group server-group-name;
authentication {
username-include {
circuit-type;
interface-name;
mac-address;
option-60;
vlan-tags;
}
}
bulk-leasequery {
attempts number-of-attempts;
timeout seconds;
}
dhcpv6 {
active-leasequery {
timeout seconds;
topology-discovery;
}
}
authentication {
309
username-include {
circuit-type;
client-id;
interface-name interface-name;
vlan-tags;
}
}
bulk-leasequery {
timeout seconds;
trigger automatic;
}
duplicate-clients incoming-interface;
}
forward-only {
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
}
forward-only-replies;
}
310
group group-name {
authentication {
username-include {
circuit-type;
client-id;
vlan-tags;
}
}
}
forward-only {
}
}
exclude;
overrides {
allow-snooped-clients;
client-negotiation-match incoming-interface;
delay-authentication;
delete-binding-on-renegotiation;
311
no-allow-snooped-clients;
no-bind-on-request;
relay-source interface-name;
send-release-on-delete;
}
trace;
}
}
lease-time-validation {
lease-time-threshold seconds;
violation-action action;
}
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
}
}
312
overrides {
no-bind-on-request;
}
relay-agent-interface-id {
include-irb-and-l2;
keep-incoming-interface-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-option-82 <strict>;
use-vlan-id;
}
relay-agent-remote-id {
include-irb-and-l2;
prefix prefix;
use-vlan-id;
}
313
relay-option {
option-number option-number;
default-action {
drop;
forward-only;
relay-server-group relay-server-group;
}
equals (ascii ascii-string | hexadecimal hexadecimal-string) {
drop;
forward-only;
}
starts-with (ascii ascii-string | hexadecimal hexadecimal-string) {
drop;
forward-only;
}
}
remote-id-mismatch disconnect;
route-suppression;
}
leasequery {
timeout seconds;
}
}
314
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
route-suppression;
}
}
no-snoop;
overrides {
no-bind-on-request;
}
315
include-irb-and-l2;
prefix prefix;
use-vlan-id;
}
include-irb-and-l2;
keep-incoming-remote-id ;
prefix prefix;
use-vlan-id;
}
relay-option {
default-action {
drop;
forward-only;
}
drop;
forward-only;
}
drop;
forward-only;
}
}
relay-option-vendor-specific{
host-name;
location;
route-suppression;
316
server-group {
server-group-name {
server-ip-address;
}
}
server-response-time seconds;
}
317
dual-stack-group dual-stack-group-name {
authentication {
username-include {
circuit-type;
interface-name;
mac-address;
vlan-tags;
}
}
classification-key {
circuit-id circuit-id;
remote-id remote-id;
}
dual-stack-interface-client-limit number;
}
method {
}
}
}
protocol-master (inet | inet6);
include-irb-and-l2;
prefix prefix;
318

use-vlan-id;
}
include-irb-and-l2;
keep-incoming-remote-id ;
prefix prefix;
use-vlan-id;
}
}
duplicate-clients-in-subnet (incoming-interface | option-82):
}
forward-only {
}
forward-only-replies;
319
group group-name {
authentication {
username-include {
circuit-type;
mac-address;
option-60;
option-82 [circuit-id] [remote-id];
}
vlan-tags;
}
}
forward-only {
}
forward-only {
}
exclude;
method {
bfd {
multiplier number;
no-adaptation;
320
transmit-interval {
}
detection-time {
}
}
}
}
overrides {
allow-no-end-option;
always-write-giaddr;
always-write-option-82;
disable-relay;
layer2-unicast-replies;
no-bind-on-request;
proxy-mode;
relay-source
replace-ip-source-with;
trust-option-82;
}
trace;
}
321
overrides {
allow-no-end-option
disable-relay;
no-bind-on-request;
proxy-mode;
relay-source
trust-option-82;
}
relay-option {
default-action {
drop;
forward-only;
relay-server-group group-name;
}
drop;
forward-only;
}
drop;
forward-only;
local-server-group local-server-group;
}
}
322
relay-option-82 {
circuit-id {
prefix prefix;
}
remote-id {
prefix prefix;
}
server-id-override
}
route-suppression:
}
leasequery {
timeout seconds;
}
}
323
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
}
}
no-snoop;
324
overrides {
allow-no-end-option
disable-relay;
no-bind-on-request;
proxy-mode;
relay-source
trust-option-82;
}
relay-option {
default-action {
drop;
forward-only;
relay-server-group group-name;
}
drop;
forward-only;
}
drop;
forward-only;
local-server-group local-server-group;
}
}
325
relay-option-82 {
circuit-id {
prefix prefix;
}
remote-id {
prefix prefix;
}
server-id-override
}
}
route-suppression:
server-group {
server-group-name {
server-ip-address;
}
}
server-response-time seconds;
}
Hierarchy Level
[edit forwarding-options],
[edit logical-systems logical-system-name forwarding-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options],
[edit routing-instances routing-instance-name forwarding-options]
Release Information
Statement introduced in Junos OS Release 13.2X51 for the QFX Series.
326
Description
Configure extended Dynamic Host Configuration Protocol (DHCP) relay and DHCPv6 relay options on
the router or switch to enable the router (or switch) to function as a DHCP relay agent. A DHCP relay
agent forwards DHCP request and reply packets between a DHCP client and a DHCP server.
DHCP relay supports the attachment of dynamic profiles and also interacts with the local AAA Service
Framework to use back-end authentication servers, such as RADIUS, to provide subscriber authentication
or client authentication. You can attach dynamic profiles and configure authentication support on a global
basis or for a specific group of interfaces.
The extended DHCP and DHCPv6 relay agent options configured with the dhcp-relay and dhcpv6
statements are incompatible with the DHCP/BOOTP relay agent options configured with the bootp
statement. As a result, the extended DHCP or DHCPv6 relay agent and the DHCP/BOOTP relay agent
cannot both be enabled on the router (or switch) at the same time.

Extended DHCP Relay Agent Overview

DHCPv6 Relay Agent Overview
DHCP Relay Proxy Overview
327
drop-probability (Interpolated Value)

Syntax
drop-probability [values];
Hierarchy Level
[edit class-of-service drop-profiles profile-name interpolate]
Release Information
Statement introduced before Junos OS 11.4 for EX Series switches.
Description
Define values for interpolated drop probabilities. The maximum number of drop probability values supported
per drop profile is based on the line card.
On EX Series switches, this statement is supported only on the EX9200 switch, EX8200 standalone
switches, and EX8200 Virtual Chassis.
Options
percentage—The probability (expressed in percentage) for a packet to be dropped from the queue.

Managing Congestion Using RED Drop Profiles and Packet Loss Priorities
Defining Packet Drop Behavior by Configuring RED Drop Profiles
328
drop-probability (Percentage)
Syntax
drop-probability percentage;
Hierarchy Level
[edit class-of-service drop-profiles profile-name]
Release Information
Description
Define drop probability percentages. The maximum number of drop probability values supported per drop
profile is based on the line card.
Options
percentage—Probability that a packet is dropped, expressed as a percentage. A value of 0 means that a
packet is never dropped, and a value of 100 means that all packets are dropped.

329
drop-profile (Schedulers)
Syntax
drop-profile profile-name;
Hierarchy Level
[edit class-of-service schedulers scheduler-name drop-profile-map loss-priority (any | low | medium-low | medium-high
| high) protocol (any | non-tcp | tcp)]
Release Information
Description
Define drop profiles for RED. When a packet arrives, RED checks the queue fill level. If the fill level
corresponds to a nonzero drop probability, the RED algorithm determines whether to drop the arriving
packet.
Options
profile-name—Name of the drop profile.

Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers
330
drop-profile-map (Schedulers)
Syntax
drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any | non-tcp | tcp) drop-profile
(Schedulers) profile-name;
Hierarchy Level
Release Information
Description
Define the loss-priority value for a drop profile.
The remaining statements are explained separately. See CLI Explorer.


331
drop-profiles
Syntax
drop-profiles {
profile-name {
fill-level percentage drop-probability percentage;
interpolate {
fill-level [values]
}
}
}
Hierarchy Level
Release Information
Description
Define drop profiles for RED.
For a packet to be dropped, it must match the drop profile. When a packet arrives, RED checks the queue
fill level. If the fill level corresponds to a nonzero drop probability, the RED algorithm determines whether
to drop the packet.
Options
profile-name—Name of the drop profile.
The remaining statements are explained separately.


332
dscp (CoS Classifiers)

Syntax
dscp classifier-name {
loss-priority level ] {
code-points [ aliases ] [ bit-patterns;
}
}
}
Hierarchy Level
[edit class-of-service classifiers]
Release Information
Description
Define the diffserv code point (DSCP) mapping that is applied to the packets.
Options
classifier-name—Name of the classifier.

interfaces—To view this statement in the configuration.

Applying DSCP Classifiers to MPLS Traffic
333
dscp (Rewrite Rules)

Syntax
dscp (rewrite-name | default) protocol (inet-both | inet-outer | mpls);
Hierarchy Level
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules]
Release Information
Description
For IPv4 traffic, apply a Differentiated Services (DiffServ) code point (DSCP) rewrite rule.
Logical interfaces do not support multiple dscp rewrite rules for the same protocol.
DSCP and DSCP IPv6 rewrite rules are supported on M Series and T Series routers when non-queuing
PICs are installed, but are disabled when queuing PICs are installed with the following exceptions:
• On M320 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs when used with the
Enhanced III FPC.
• On M120 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs.
DSCP and DCSP IPv6 rewrite rules are supported on MIC and MPC interfaces on MX Series routers.
DSCP rewrite rules are not supported on T Series routers when IQ, IQ2, IQE, IQ2E, SONET/SDH
OC48/STM16 IQE, or PD-5-10XGE-SFPP PICs are installed.
Options
rewrite-name—Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules
dscp] hierarchy level.
default—The default mapping.
protocol inet-both—For gr- interfaces (GRE tunnels) on MPCs, rewrite the DSCP CoS value to both the
inner and outer header for Unicast/Multicast IPv4 traffic. The first six bits of the CoS value are rewritten
and the final two bits are taken from the incoming CoS value.
protocol inet-outer—For gr- interfaces on MPCs, rewrite the DSCP CoS value to the outer header for
Unicast/Multicast IPv4 traffic. The first six bits of the CoS value are rewritten and the final two bits
are taken from the incoming CoS value.
334
protocol mpls—(Optional for ingress MPLS tunnel nodes) For interfaces on MX Series routers or hosted
on Enhanced III FPCs in M120 or M320 routers only, rewrite the MPLS EXP bits in the MPLS header
independently of the IPv4 DSCP value for IPv4 packets entering an MPLS tunnel.

Configuring Rewrite Rules

Applying Rewrite Rules to Output Logical Interfaces
protocol (Rewrite Rules)
Rewriting MPLS and IPv4 Packet Headers
335
dscp-ipv6 (CoS Rewrite Rules)

Syntax
dscp-ipv6 (rewrite-name | <default>) protocol mpls;
Hierarchy Level
Release Information
Support for protocol mpls option introduced in Junos OS Release 10.4R2.
Description
For IPv6 traffic, apply a DSCP rewrite rule.
Logical interfaces do not support multiple dscp-ipv6 rewrite rules for the same protocol.
DSCP and DSCP IPv6 rewrite rules are supported on M Series and T Series routers when non-queuing
PICs are installed, but are disabled when queuing PICs are installed with the following exceptions:
• On M320 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs when used with the
Enhanced III FPC.
• On M120 routers, DSCP rewrite is supported on IQ, IQ2, IQE, and IQ2E PICs.
DSCP and DCSP IPv6 rewrite rules are supported on MIC and MPC interfaces on MX Series routers.
DSCP rewrite rules are not supported on T Series routers when IQ, IQ2, IQE, IQ2E, SONET/SDH
OC48/STM16 IQE, or PD-5-10XGE-SFPP PICs are installed.
Options
dscp-ipv6] hierarchy level.
default—Default mapping.
protocol mpls—(Optional for ingress MPLS tunnel nodes) For interfaces on MX Series routers or hosted
on Enhanced III FPCs in M120 or M320 routers only, rewrite the MPLS EXP bits in the MPLS header
independently of the IPv6 DSCP value for IPv6 packets entering an MPLS tunnel.

336

protocol
Setting IPv6 DSCP and MPLS EXP Values Independently
Configuring DSCP Values for IPv6 Packets Entering the MPLS Tunnel
337
dynamic-profile (DHCP Local Server)

Syntax
}
Hierarchy Level

[edit system services dhcp-local-server dual-stack-group dual-stack-group-name],
[edit system services dhcp-local-server dhcpv6 group group-name interface interface-name],
[edit system services dhcp-local-server group group-name interface interface-name],
...],
Release Information
Options aggregate-clients and use-primary introduced in Junos OS Release 9.3.
Support at the [edit ... interface] hierarchy levels introduced in Junos OS Release 11.2.
Description
Specify the dynamic profile that is attached to all interfaces, a named group of interfaces, or a specific
interface.
Options
profile-name—Name of the dynamic profile.

338
Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces

Configuring a Default Subscriber Service
339
dynamic-profile (VLAN)
Syntax
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
access-profilevlan-dynamic-profile-name;
}
Hierarchy Level
[edit interfaces interface-name auto-configure vlan-ranges]
Release Information
Description
Configure a dynamic profile for use when configuring dynamic VLANs.
Options
profile-name—Name of the dynamic profile that you want to use when configuring dynamic VLANs.


340
dynamic-profiles
Syntax
dynamic-profiles {
profile-name {
class-of-service {
dynamic-class-of-service-options {
vendor-specific-tags tag;
}
interfaces {
interface-name ;
}
classifiers {
type (classifier-name | default);
}
output-traffic-control-profile (profile-name | $junos-cos-traffic-control-profile);
report-ingress-shaping-rate bps;
rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);
ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner);
inet-precedence (rewrite-name | default);
}
}
}
}
scheduler-maps {
map-name {
}
}
schedulers {
(scheduler-name) {
buffer-size (seconds | percent percentage | remainder | temporal microseconds);
drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any | non-tcp |
tcp) drop-profile profile-name;
excess-priority (low | high | $junos-cos-scheduler-excess-priority);
excess-rate (percent percentage | percent $junos-cos-scheduler-excess-rate);
overhead-accounting (shaping-mode) <bytes (byte-value>;
shaping-rate (rate | predefined-variable);
transmit-rate (percent percentage | rate | remainder) <exact | rate-limit>;
}
341
}
traffic-control-profiles profile-name {
excess-rate (percent percentage | proportion value | percent $junos-cos-excess-rate);
excess-rate-high (percent percentage | proportion value);
excess-rate-low (percent percentage | proportion value);
guaranteed-rate (percent percentage | rate) <burst-size bytes>;
max-burst-size cells;
overhead-accounting (frame-mode | cell-mode) <bytes byte-value>;
peak-rate rate;
shaping-rate (percent percentage | rate | predefined-variable) <burst-size bytes>;
shaping-rate-excess-high (percent percentage | rate) <burst-size bytes>;
shaping-rate-excess-medium-high (percent percentage | rate) <burst-size bytes>;
shaping-rate-excess-medium-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-excess-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-high (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-medium (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-medium-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-strict-high (percent percentage | rate) <burst-size bytes>;
sustained-rate rate;
}
}
342
firewall {
family family {
fast-update-filter filter-name {
interface-specific;
match-order [match-order];
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-create;
}
}
filter filter-name {
enhanced-mode-override;
fast-lookup-filter;
instance-shared;
interface-shared;
interface-specific;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-create;
interface-specific;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
hierarchical-policer uid {
aggregate {
343
if-exceeding {
bandwidth-limit-limit bps;
burst-size-limit bytes;
}
then {
policer-action;
}
}
premium {
if-exceeding {
bandwidth-limit bps;
}
then {
policer-action;
}
}
}
policer uid {
filter-specific;
if-exceeding {
(bandwidth-limit bps | bandwidth-percent percentage);
}
logical-bandwidth-policer;
logical-interface-policer;
physical-interface-policer;
then {
policer-action;
}
}
344
three-color-policer uid {
action {
loss-priority high then discard;
}
single-rate {
(color-aware | color-blind);
committed-burst-size bytes;
committed-information-rate bps;
excess-burst-size bytes;
}
two-rate {
peak-burst-size bytes;
peak-information-rate bps;
}
}
}
}
345
interfaces interface-name {
unit logical unit number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
}
}
actual-transit-statistics;
auto-configure {
agent-circuit-identifier {
}
line-identity {
include {
accept-no-ids;
circuit-id;
remote-id;
}
}
}
encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-cisco-nlpid | atm-tcc-vc-mux | atm-mlppp-llc |
atm-nlpid | atm-ppp-llc | atm-ppp-vc-mux | atm-snap | atm-tcc-snap | atm-vc-mux | ether-over-atm-llc
| ether-vpls-over-atm-llc | ether-vpls-over-fr | ether-vpls-over-ppp | ethernet | frame-relay-ccc |
frame-relay-ppp | frame-relay-tcc | frame-relay-ether-type | frame-relay-ether-type-tcc |
multilink-frame-relay-end-to-end | multilink-ppp | ppp-over-ether | ppp-over-ether-over-atm-llc |
vlan-bridge | vlan-ccc | vlan-vci-ccc | vlan-tcc | vlan-vpls);
family family {
address address;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name (
precedence precedence;
346
shared-name filter-shared-name;
}
output filter-name {
}
}
rpf-check {
mode loose;
}
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}
input-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(push | swap);
tag-protocol-id tpid;
vlan-id number;
}
output {
}
}
output-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(pop | swap);
tag-protocol-id tpid;
vlan-id number;
}
pcef pcef-profile-name {
activate rule-name | activate-all;
}
}
}
347
filter {
input filter-name (
}
}
}
host-prefix-only;
ppp-options {
aaa-options aaa-options-name;
authentication [ authentication-protocols ];
chap {
challenge-length minimum minimum-length maximum maximum-length;
local-name name;
}
ignore-magic-number-mismatch;
initiate-ncp (dual-stack-passive | ipv6 | ip)
ipcp-suggest-dns-option;
mru size;
mtu (size | use-lower-layer);
on-demand-ip-address;
pap;
peer-ip-address-optional;
local-authentication {
password password;
username-include {
circuit-id;
delimiter character;
domain-name name;
mac-address;
remote-id;
}
}
}
targeted-options {
backup backup;
group group;
primary primary;
weight ($junos-interface-target-weight | weight-value);
}
348
telemetry {
subscriber-statistics;
queue-statistics {
interface $junos-interface-name {
refresh rate;
queues queue set;
}
interface-set $junos-interface-set-name {
refresh rate;
queues queue set;
}
}
}
vlan-id number;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}
}
interfaces {
demux0 {...}
}
interfaces {
pp0 {...}
}
policy-options {
prefix-list uid {
ip-addresses;
dynamic-db;
}
}
predefined-variable-defaults predefined-variable <variable-option> default-value;
profile-type remote-device-service;
349
protocols {
igmp {
accounting;
disable;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave
log-interval seconds;
no-accounting;
oif-map;
passive;
promiscuous-mode;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name
static {
group group {
source source;
}
}
version version;
}
}
mld {
(accounting | no-accounting);
disable;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave;
log-interval seconds;
oif-map;
passive;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name;
static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
350
source-increment increment;
}
}
}
version version;
}
}
router-advertisement {
current-hop-limit number;
default-lifetime seconds;
(managed-configuration | no-managed-configuration);
max-advertisement-interval seconds;
min-advertisement-interval seconds;
(other-stateful-configuration | no-other-stateful-configuration);
prefix prefix;
reachable-time milliseconds;
retransmit-timer milliseconds;
}
}
}
351
routing-instances routing-instance-name {
interface interface-name;
routing-options {
access {
route prefix {
next-hop next-hop;
metric route-cost;
preference route-distance;
tag route-tag;
tag2 route-tag2;
}
}
access-internal {
route subscriber-ip-address {
qualified-next-hop underlying-interface {
mac-address address;
}
}
}
multicast {
no-qos-adjust;
}
}
}
rib routing-table-name {
access {
route prefix {
next-hop next-hop;
metric route-cost;
tag route-tag;
tag2 route-tag2;
}
}
access-internal {
}
}
}
}
}
352
routing-options {
access {
route prefix {
next-hop next-hop;
metric route-cost;
tag route-tag;
tag2 route-tag2;
}
}
access-internal {
}
}
}
multicast {
no-qos-adjust;
}
}
}
services {
captive-portal-content-delivery {
auto-deactivate value;
rule name {
match-direction (input | input-output | output);
term name {
then {
accept;
redirect url;
rewrite destination-address address <destination-port port-number>;
syslog;
}
}
}
}
}
353
variables {
variable-name {
default-value default-value;
equals expression;
mandatory;
uid;
uid-reference;
}
}
}
}
Hierarchy Level
[edit]
Release Information
Support at the filter, policer, hierarchical-policer, three-color-policer, and policy options hierarchy levels
introduced in Junos OS Release 11.4.
Description
Create dynamic profiles for use with DHCP or PPP client access.
Options
profile-name—Name of the dynamic profile; string of up to 80 alphanumeric characters.

routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.

Configuring Dynamic VLANs Based on Agent Circuit Identifier Information
Dynamic Profiles for Subscriber Management
354
egress-shaping-overhead
Syntax
egress-shaping-overhead number;
Hierarchy Level
[edit chassis fpc slot-number pic pic-number traffic-manager],

[edit chassis lcc number fpc slot-number pic pic-number traffic-manager]
Release Information
Description
Number of bytes to add to packet to determine shaped session packet length.
NOTE: On M Series and T Series routers with Gigabit Ethernet Intelligent Queuing 2 (IQ2) PICs
and Enhanced IQ2 (IQ2E) PICs and on MX Series routers with Dense Port Concentrators (DPCs)
only, to account for egress shaping overhead bytes added to output traffic on the line card, you
must use the egress-policer-overhead statement to explicitly configure corresponding egress
policing overhead for Layer 2 policers, MAC policers, or queue rate limits applied to output traffic
on the line card.
NOTE: For MIC and MPC interfaces on MX Series routers, by default the value of
egress-shaping-overhead is configured to 20, which means that the number of class-of-service
(CoS) shaping overhead bytes to be added to the packets is 20. The interfaces on DPCs in MX
Series routers, the default value is zero. For interfaces on PICs other than the 10-port 10-Gigabit
Oversubscribed Ethernet (OSE) Type 4, you should configure egress-shaping-overhead to a
minimum of 20 bytes to add a shaping overhead of 20 bytes to the packets.
NOTE: When you change the egress-shaping-overhead value, on M Series, T Series, and MX104
routers the PIC on which it is changed is restarted. On MX5 routers, the MIC on which it is
changed is restarted. On other MX Series routers, the DPC/MPC on which it is changed is
restarted.
355
Options
number—When traffic management (queuing and scheduling) is configured on the egress side, the number
of CoS shaping overhead bytes to add to the packets on the egress interface.
Range:
• –63 through 192.
• –62 through 192 for vSRX.
NOTE: The L2 headers (DA/SA + VLAN tags) are automatically a part of the shaping calculation.

egress-policer-overhead
Configuring CoS for L2TP Tunnels on ATM Interfaces
ingress-shaping-overhead
mode (Layer 2 Tunneling Protocol Shaping) | 435, ingress-shaping-overhead
356
excess-bandwidth-share
Syntax
excess-bandwidth-share (proportional value | equal);
Hierarchy Level
Release Information
Description
Specify the method of sharing excess bandwidth in a hierarchical scheduler environment. With hierarchical
schedulers, you can provide shaping and scheduling at the service VLAN level as well as other levels, such
as the physical interface. You can also group a set of logical interfaces and then apply scheduling and
shaping parameters to the logical interface set.
To configure CoS hierarchical schedulers, you must enable hierarchical scheduling by including the
hierarchical-scheduler statement at the [edit interfaces] hierarchy for the physical interface. If you do not
include this statement, the interfaces on the MX Series router cannot use hierarchical interfaces.
The Enhanced Queuing DPC supports the following hierarchical scheduler characteristics:
• Shaping at the physical interface level
• Shaping and scheduling at the service VLAN interface set level
• Shaping and scheduling at the customer VLAN logical interface level
• Scheduling at the queue level
Options
equal—Share excess bandwidth equally among the configured interfaces.
proportional value—(Default) Share excess bandwidth proportionally according to the specified value. In
this mode, the excess bandwidth is shared at the ratio of the logical interface shaping rates.
Default: 32.64 Mbps
This example sets the excess bandwidth sharing for an Enhanced Queuing DPC interface proportionally
at a rate of 100 Mbps and a shaping rate of 80 Mbps applied to the interface through the
output-traffic-control profile for scheduling and shaping:
357
[edit class-of-service interfaces interface-set example-interface-set]

user@host# set excess-bandwidth-share proportional 100m
user@host# set output-traffic-control-profile PIR-80Mbps


Configuring Interface Sets
Configuring MDRR on Enhanced Queuing DPCs
358
excess-priority
Syntax
excess-priority [ low | medium-low | medium-high | high | none];
Hierarchy Level
Release Information
Option none introduced in Junos OS Release 11.4.
Description
Determine the priority of excess bandwidth traffic on a scheduler.
NOTE: For Link Services IQ (LSQ) PICs or Multiservices PIC (MS-PICs), the excess-priority
statement is allowed for consistency, but ignored. If an explicit priority is not configured for
these interfaces, a default low priority is used. This default priority is also used in the excess
region.
Options
low—Excess traffic for this scheduler has low priority.
medium-low—Excess traffic for this scheduler has medium-low priority.
medium-high—Excess traffic for this scheduler has medium-high priority.
high—Excess traffic for this scheduler has high priority.
none—System does not demote the priority of guaranteed traffic when the bandwidth exceeds the shaping
rate or the guaranteed rate.

359
Configuring Excess Bandwidth Sharing on IQE PICs

Bandwidth Sharing on Nonqueuing Packet Forwarding Engines Overview
Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs
360
excess-rate (Dynamic Traffic Shaping)

Syntax
excess-rate (percent percentage | $junos-cos-excess-rate) | proportion value);
Hierarchy Level
Release Information
Description
For an MPC interface, determine the percentage or proportion of excess bandwidth traffic to share for all
priorities of traffic.
Options
percentage—Percentage of the excess bandwidth to share.
value—Proportion of the excess bandwidth to share.

NOTE: The proportion of excess bandwidth on MPC2-3D MPCs can be configured with
increments of 1 from 0 through 1000. All other MPCs should be configured with increments of
10 from 0 through 1000.
$junos-cos-excess-rate—Variable for the excess rate that is specified for the logical interface. The variable
is replaced with a value obtained from the RADIUS server when a subscriber authenticates over the
interface to which the dynamic profile is attached.


361
Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces
output-traffic-control-profile
362
excess-rate-high (Dynamic Traffic Shaping)

Syntax
excess-rate-high ((percent percentage | $junos-cos-excess-rate-high) | proportion value);
Hierarchy Level
Release Information
Description
For an MPC/MIC interface, determine the percentage of excess bandwidth for high-priority traffic to
share.
Options

$junos-cos-excess-rate-high—Variable for the excess rate that is specified for high-priority traffic on the
logical interface. The variable is replaced with a value obtained from the RADIUS server when a subscriber
authenticates over the interface to which the dynamic profile is attached.


363
364
excess-rate-low (Dynamic Traffic Shaping)

Syntax
excess-rate-low ((percent percentage | $junos-cos-excess-rate-low) | proportion value);
Hierarchy Level
Release Information
Description
For an MPC/MIC interface, determine the percentage of excess bandwidth for low-priority traffic to share.
Options

$junos-cos-excess-rate-low—Variable for the excess rate that is specified for low-priority traffic on the
logical interface. The variable is replaced with a value obtained from the RADIUS server when a subscriber
authenticates over the interface to which the dynamic profile is attached.


365
366
family
Syntax
family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
address address {
... the address subhierarchy appears after the main [edit interfaces interface-name unit logical-unit-number family
family-name] hierarchy ...
}
bundle interface-name;
core-facing;
demux-destination {
destination-prefix;
}
demux-source {
source-prefix;
}
direct-connect;
filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}
interface-mode (access | trunk);
ipsec-sa sa-name;
keep-address-and-control;
mac-validate (loose | strict);
mtu bytes;
multicast-only;
nd6-stale-time seconds;
negotiate-address;
no-neighbor-learn;
367
no-redirects;
policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
}
primary;
protocols [inet iso mpls];
proxy inet-address address;
receive-options-packets;
receive-ttl-exceeded;
remote (inet-address address | mac-address address);
rpf-check {
fail-filter filter-name
mode loose;
}
sampling {
input;
output;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max maximum-seconds> <filter [aci]>;
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
unnumbered-address interface-name destination address destination-profile profile-name;
vlan-id number;
vlan-id-list [number number-number];
368
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
master-only;
multipoint-destination address dlci dlci-identifier;
multipoint-destination address {
epd-threshold cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr burst length peak rate sustained rate | vbr burst length peak rate sustained rate);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
vrrp-groupgroup-id {
(accept-data | no-accept-data);
advertise-interval seconds;
authentication-key key;
authentication-type authentication;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
bandwidth-threshold bits-per-second priority-cost priority;
priority-cost priority;
}
priority-hold-time seconds;
route prefix routing-instance instance-name priority-cost priority;
}
}
virtual-address [ addresses ];
369
}
virtual-link-local-address ipv6-address;
}
}
Hierarchy Level

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Release Information
Option max-sessions-vsa-ignore introduced in Junos OS Release 11.4.
Description
Configure protocol family information for the logical interface.
Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC (Translational
cross-connect) encapsulation on MX series platforms. See Configuring VLAN TCC Encapsulation for more
details.
NOTE: Not all subordinate statements are available to every protocol family.
370
Options
• any—Protocol-independent family used for Layer 2 packet filtering
NOTE: This option is not supported on T4000 Type 5 FPCs.
• bridge—(M Series and T Series routers only) Configure only when the physical interface is configured
with ethernet-bridge type encapsulation or when the logical interface is configured with vlan-bridge
type encapsulation. You can optionally configure this protocol family for the logical interface on which
you configure VPLS.
• ethernet-switching—(M Series and T Series routers only) Configure only when the physical interface is
configured with ethernet-bridge type encapsulation or when the logical interface is configured with
vlan-bridge type encapsulation
• ccc—Circuit cross-connect protocol suite. You can configure this protocol family for the logical interface
of CCC physical interfaces. When you use this encapsulation type, you can configure the ccc family only.
• inet—Internet Protocol version 4 suite. You must configure this protocol family for the logical interface
to support IP protocol traffic, including Open Shortest Path First (OSPF), Border Gateway Protocol (BGP),
Internet Control Message Protocol (ICMP), and Internet Protocol Control Protocol (IPCP).
• inet6—Internet Protocol version 6 suite. You must configure this protocol family for the logical interface
to support IPv6 protocol traffic, including Routing Information Protocol for IPv6 (RIPng), Intermediate
System-to-Intermediate System (IS-IS), BGP, and Virtual Router Redundancy Protocol for IPv6 (VRRP).
• iso—International Organization for Standardization Open Systems Interconnection (ISO OSI) protocol
suite. You must configure this protocol family for the logical interface to support IS-IS traffic.
• mlfr-end-to-end—Multilink Frame Relay FRF.15. You must configure this protocol or multilink
Point-to-Point Protocol (MLPPP) for the logical interface to support multilink bundling.
• mlfr-uni-nni—Multilink Frame Relay FRF.16. You must configure this protocol or mlfr-end-to-end for
the logical interface to support link services and voice services bundling.
• multilink-ppp—Multilink Point-to-Point Protocol. You must configure this protocol (or mlfr-end-to-end)
for the logical interface to support multilink bundling.
• mpls—Multiprotocol Label Switching (MPLS). You must configure this protocol family for the logical
interface to participate in an MPLS path.
• pppoe—Point-to-Point Protocol over Ethernet
• tcc—Translational cross-connect protocol suite. You can configure this protocol family for the logical
interface of TCC physical interfaces.
371
• tnp—Trivial Network Protocol. This protocol is used to communicate between the Routing Engine and
the router’s packet forwarding components. The Junos OS automatically configures this protocol family
on the router’s internal interfaces only, as discussed in Understanding Internal Ethernet Interfaces.
• vpls—(M Series and T Series routers only) Virtual private LAN service. You can optionally configure this
protocol family for the logical interface on which you configure VPLS. VPLS provides an Ethernet-based
point-to-multipoint Layer 2 VPN to connect customer edge (CE) routers across an MPLS backbone.
When you configure a VPLS encapsulation type, the family vpls statement is assumed by default.
MX Series routers support dynamic profiles for VPLS pseudowires, VLAN identifier translation, and
automatic bridge domain configuration.
For more information about VPLS, see the Junos OS VPNs Library for Routing Devices.

Release Description
20.1R1 Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC
(Translational cross-connect) encapsulation on MX series platforms.
Configuring the Protocol Family

372
family (Address-Assignment Pools)

Syntax
family family {
dhcp-attributes {
[protocol-specific attributes]
}
host hostname {
}
network ip-prefix/<prefix-length>;
prefix ipv6-prefix;
range range-name {
high upper-limit;
low lower-limit;
}
}
Hierarchy Level
[edit access address-assignment pool pool-name]
Release Information
Description
Configure the protocol family for the address-assignment pool.
NOTE: Subordinate statement support depends on the platform. See individual statement topics
for more detailed support information.
Options

373


374
family (Dynamic Demux Interface)

Syntax
family family {
address address;
demux-source {
source-address;
}
direct-connect;
filter {
input filter-name;
output filter-name;
}
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number]
Release Information
pppoe option added in Junos OS Release 11.2.
Description
NOTE: Not all subordinate stanzas are available to every protocol family.
Options
375
• pppoe—(MX Series routers with MPCs only) Point-to-Point Protocol over Ethernet


Subscriber Interfaces and Demultiplexing Overview
376
family (Dynamic PPPoE)

Syntax
family family {
unnumbered-address interface-name;
address address;
service {
input {
}
}
output {
}
}
}
filter {
input filter-name {
}
}
}
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit”]
Release Information
Description
Options

377

Configuring a PPPoE Dynamic Profile

Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview
378
family (Dynamic Standard Interface)

Syntax
family family {
address address;
direct-connect;
filter {
adf {
counter;
not-mandatory;
rule rule-value;
}
input filter-name {
}
}
}
rpf-check {
mode loose;
}
service {
input {
}
}
output {
}
379
}
}
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number]
Release Information
pppoe option added in Junos OS Release 11.2.
Description
NOTE: Not all subordinate stanzas are available to every protocol family.
Options
• inet—IP version 4 suite
• inet6—IP version 6 suite
• pppoe—(MX Series routers with MPCs only) Point-to-Point Protocol over Ethernet
• vpls—Virtual private LAN service

380
Static Routing on Logical Systems

Configuring the Protocol Family
fill-level (Drop Profiles)

Syntax
fill-level percentage;
Hierarchy Level
Release Information
Description
When configuring RED, map the fullness of a queue to a drop probability.
Options
percentage—How full the queue is, expressed as a percentage. You configure the fill-level and
drop-probability statements in pairs. To specify multiple fill levels, include multiple fill-level and
drop-probability statements. The values you assign to each statement pair must increase relative to the
previous pair’s values. This is shown in the discrete graph in Managing Congestion Using RED Drop Profiles
and Packet Loss Priorities.

381
fill-level (Interpolated Value)

Syntax
fill-level [values];
Hierarchy Level
[edit class-of-service drop-profiles profile-name interpolate]
Release Information
Description
Define up to 64 values for interpolating queue fill level.
On EX Series switches, this statement is supported only on EX8200 standalone switches and EX8200
Virtual Chassis.
Options
values—Data points for mapping queue fill percentage.
Default: In the default tail drop profile, when the fill level is 0 percent, the drop probability is 0 percent. When
the fill level is 100 percent, the drop probability is 100 percent.

Defining Packet Drop Behavior by Configuring RED Drop Profiles.
382
filter (Configuring)
Syntax
accounting-profile name;
enhanced-mode;
fast-lookup-filter;
filter-list-template;
interface-shared;
interface-specific;
physical-interface-filter;
promote gre-key;
term term-name {
... term configuration ...
}
}
Hierarchy Level
[edit dynamic-profiles profile-name firewall family family-name],

[edit firewall family family-name],
[edit logical-systems logical-system-name firewall family family-name]
Release Information
Logical systems support introduced in Junos OS Release 9.3.
physical-interface-filter statement introduced in Junos OS Release 9.6.
Support for the interface-shared statement introduced in Junos OS Release 12.2.
Description
Configure firewall filters.
Options
filter-name—Name that identifies the filter. This must be a non-reserved string of not more than 64
characters. To include spaces in the name, enclose it in quotation marks (“ ”). Firewall filter names are
restricted from having the form __.*__ (beginning and ending with underscores) or __.* (beginning with an
underscore.

383
firewall—To view this statement in the configuration.

firewall-control—To add this statement to the configuration.
Guidelines for Configuring Firewall Filters

Guidelines for Applying Standard Firewall Filters
Configuring Multifield Classifiers
Using Multifield Classifiers to Set Packet Loss Priority
simple-filter | 516
384
flexible-vlan-tagging
Syntax
Hierarchy Level
[edit interfaces aex],

[edit interfaces ge-fpc/pic/port],
[edit interfaces et-fpc/pic/port],
[edit interfaces ps0],
[edit interfaces xe-fpc/pic/port]
Release Information
Support for aggregated Ethernet added in Junos OS Release 9.0.
Statement introduced in Junos OS Release 12.1x48 for PTX Series Packet Transport Routers.
Statement introduced in Junos OS Release 13.2X50-D15 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.
Description
Support simultaneous transmission of 802.1Q VLAN single-tag and dual-tag frames on logical interfaces
on the same Ethernet port, and on pseudowire logical interfaces.
This statement is supported on M Series and T Series routers, for Fast Ethernet and Gigabit Ethernet
interfaces only on Gigabit Ethernet IQ2 and IQ2-E, IQ, and IQE PICs, and for aggregated Ethernet interfaces
with member links in IQ2, IQ2-E, and IQ PICs or in MX Series DPCs, or on Ethernet interfaces for PTX
Series Packet Transport Routers or 100-Gigabit Ethernet Type 5 PIC with CFP.
This statement is supported on Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated
Ethernet interfaces on EX Series and QFX Series switches.

Enabling VLAN Tagging

Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers
Configuring Double-Tagged VLANs on Layer 3 Logical Interfaces
385
forwarding-classes (Class-of-Service)
Syntax
class queue-num queue-number priority (high | low);
queue queue-number class-name priority (high | low) [ policing-priority (premium | normal) ];
}
Hierarchy Level
Release Information
policing-priority option introduced in Junos OS Release 9.5.
Statement introduced on PTX Series Packet Transport Routers in Junos OS Release 12.1.
Description
Associate the forwarding class with a queue name and number. For M320, MX Series, T Series routers
and EX Series switches only, you can configure fabric priority queuing by including the priority statement.
For Enhanced IQ PICs, you can include the policing-priority option.
NOTE: The priority and policing-priority options are not supported on PTX Series Packet
Transport Routers.

Configuring a Custom Forwarding Class for Each Queue

Forwarding Classes and Fabric Priority Queues
Configuring Hierarchical Layer 2 Policers on IQE PICs
Classifying Packets by Egress Interface
386
group (DHCP Local Server)

Syntax
group group-name {
authentication {
username-include {
circuit-type;
client-id;
mac-address;
option-60;
relay-agent-interface-id
vlan-tags;
}
}
exclude;
overrides {
client-discover-match <option60-and-option82>;
delay-advertise {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
387
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delay-offer {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
process-inform {
pool pool-name;
}
rapid-commit;
}
trace;
}
388
method {
bfd {
multiplier number;
no-adaptation;
transmit-interval {
}
detection-time {
}
}
}
}
}
389
overrides {
client-discover-match <option60-and-option82>;
delay-advertise {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delay-offer {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delegated-pool;
process-inform {
390
pool pool-name;
}
rapid-commit;
}
reconfigure {
clear-on-abort;
strict;
token token-value;
trigger {
radius-disconnect;
}
}
route-suppression;
}
Hierarchy Level

...],
Release Information
Description
Configure a group of interfaces that have a common configuration, such as authentication parameters. A
group must contain at least one interface.
Options
group-name—Name of the group.
391


Grouping Interfaces with Common DHCP Configurations
Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces
DHCP Liveness Detection Using ARP and Neighbor Discovery Packets
392
guaranteed-rate
Syntax
Hierarchy Level
Release Information
Option burst-size introduced for Enhanced Queuing (EQ) DPC interfaces in Junos OS Release 9.4.
Option burst-size introduced for MIC and MPC interfaces in Junos OS Release 11.4.
Option burst-size introduced for IQ2 and IQ2E interfaces in Junos OS Release 12.3
Description
For Gigabit Ethernet IQ, Channelized IQ PICs, Multiservices and Services PICs FRF.16 LSQ interfaces, and
EQ DPCs only, configure a guaranteed minimum rate. You can also configure an optional burst size for a
logical interface on EQ DPCs and on IQ2 and IQ2E PICs. This can help to ensure that higher priority services
do not starve lower priority services.
Default
If you do not include this statement and you do not include the delay-buffer-rate statement, the logical
interface receives a minimal delay-buffer rate and minimal bandwidth equal to 2 MTU-sized packets.
Options
percent percentage—For LSQ interfaces, guaranteed rate as a percentage of the available interface
bandwidth.
rate—For IQ and IQ2 interfaces, guaranteed rate, in bits per second (bps). You can specify a value in bits
per second either as a complete decimal number or as a decimal number followed by the abbreviation
k (1000), m (1,000,000), or g (1,000,000,000).
burst-size bytes—(Optional) Maximum burst size, in bytes.

393


394
hierarchical-scheduler
Syntax
Hierarchy Level
Release Information
Description
On MX Series, M Series, and T Series routers with IQ2E PIC, enables the use of hierarchical schedulers.
NOTE: To enable hierarchical scheduling on MX80 and MX104 routers, configure the
hierarchical-scheduler statement at each member physical interface level of a particular
aggregated Ethernet interface as well as at that aggregated Ethernet interface level. On other
routing platforms, it is enough if you include this statement at the aggregated Ethernet interface
level.
Default
If you do not include this statement, the interfaces on the MX Series router cannot use hierarchical
interfaces.


395
hierarchical-scheduler (Subscriber Interfaces on MX Series Routers)

Syntax
implicit-hierarchy;
maximum-hierarchy-levels number;
}
Hierarchy Level
Release Information
implicit-hierarchy option added in Junos OS Release 13.1.
Support on GRE tunnel interfaces configured on physical interfaces on MICs or MPCs in MX Series routers
added in Junos OS Release 13.3.
Support for up to four hierarchy levels added in Junos OS Release 16.1.
Description
Configure hierarchical scheduling options on the interface.
The statement is supported on the following interfaces:
• MIC and MPC interfaces in MX Series routers
• GRE tunnel interfaces configured on physical interfaces hosted on MIC or MPC line cards in MX Series
routers
To enable hierarchical scheduling on MX Series routers, configure the hierarchical-scheduler statement

at each member physical interface level of a particular aggregated Ethernet interface as well as at that
aggregated Ethernet interface level. On other routing platforms, it is enough if you include this statement
at the aggregated Ethernet interface level.
Options
implicit-hierarchy—Configure four-level hierarchical scheduling. When you include the implicit-hierarchy
option, a hierarchical relationship is formed between the CoS scheduler nodes at level 1, level 2, level 3,
and level 4. The implicit-hierarchy option is supported only on MPC/MIC subscriber interfaces and interface
sets on MX Series routers.
maximum-hierarchy-levels number—Specify the maximum number of hierarchical scheduling levels allowed

for node scaling, from 2 through 4 levels. The default number of levels is 3. The maximum-hierarchy-levels
option is supported on MPC/MIC or EQ DPC subscriber interfaces and interface sets on MX Series routers.
396
• If you set maximum-hierarchy-levels to 2, interface sets are not allowed. In this case, if you configure
a level 2 interface set, you generate Packet Forwarding Engine errors.
• If you do not include the maximum-hierarchy-levels option, keeping the default number of hierarchy
levels at 3, interface sets can be at either level 2 or level 3, depending on whether the member logical
interfaces within the interface set have a traffic control profile. If any member logical interface has a
traffic control profile, then the interface set is a level 2 CoS scheduler node. If no member logical interface
has a traffic control profile, the interface set is at level 3.
CAUTION: MPC3E, 32x10GE MPC4E, and 2x100GE + 8x10GE MPC4E MPCs support
only two levels of scheduling hierarchy. When enabling hierarchical scheduling on
these cards, you must explicitly set maximum-hierarchy-levels to 2.

view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.

397
ieee-802.1ad
Syntax
ieee-802.1ad (rewrite-name | default) vlan-tag (outer | outer-and-inner);
Hierarchy Level
Release Information
Description
Apply a IEEE-802.1ad rewrite rule.
Options
ieee-802.1ad] hierarchy level.
default—The default rewrite bit mapping.
vlan-tag—The rewrite rule is applied to the outer or outer-and-inner VLAN tag.


exp
exp-push-push-push
exp-swap-push-push
ieee-802.1 (Rewrite Rules on Logical Interface)
inet-precedence (CoS Rewrite Rules)
398
inet-precedence (CoS Classifiers)

Syntax
inet-precedence (classifier-name | default) {

loss-priority level code-points [ aliases ] [ bit-patterns ]
}
}
Hierarchy Level
[edit class-of-service classifiers]
Release Information
Description
Apply an IPv4 classifier.
Options
default—The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type
of service (ToS) byte while leaving the last three bits unchanged.


399
input-excess-bandwidth-share
Syntax
Hierarchy Level
[edit class-of-service interfaces interface-name],

Release Information
Description
Determines the method of sharing excess bandwidth on the ingress interface in a hierarchical scheduler
environment. If you do not include this statement, the node shares excess bandwidth proportionally at
32.64 Mbps.
Options
proportional value—(Default) Share ingress excess bandwidth proportionally (default value is 32.64 Mbps).
equal—Share ingress excess bandwidth equally.


400
input-scheduler-map
Syntax
Hierarchy Level

Release Information
Description
Associate a scheduler map with a physical or logical input interface. The input-scheduler-map and
input-traffic-control-profile statements are mutually exclusive at the same hierarchy level.
input-scheduler-map is supported on the following Ethernet interfaces:
• IQ2 and IQ2E PICs
• DPCs and MPCs that support Enhanced Queuing (Q/EQ)
• MX80 with support for per-VLAN queuing
NOTE:
For an Enhanced Queuing (EQ) DPC on an MX Series router, CoS queuing and scheduling are
enabled on the egress side but disabled on the ingress side by default. To enable ingress CoS on
the EQ DPC, you must configure the traffic-manager statement with ingress-and-egress mode:

Options
map-name—Name of scheduler map that you define at the [edit class-of-service scheduler-maps] hierarchy
level.
default—The default scheduler mapping.

401
Configuring an Input Scheduler on an Interface

402
input-shaping-rate (Logical Interface)

Syntax
Hierarchy Level
Release Information
Description
For Gigabit Ethernet IQ2, Enhanced Queuing DPC, MIC, and MPC interfaces, configure input traffic shaping
by specifying the amount of bandwidth to be allocated to the logical interface. You can configure hierarchical
shaping, meaning you can apply an input shaping rate to both the physical interface and the logical interface.
Default
If you do not include this statement, logical interfaces share a default scheduler. This scheduler has a
committed information rate (CIR) that equals 0. (The CIR is the guaranteed rate.) The default scheduler
has a peak information rate (PIR) that equals the physical interface shaping rate.
Options
percent percentage—Shaping rate as a percentage of the available interface bandwidth.
rate—Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete
decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or
g (1,000,000,000).

403

Configuring Input Shaping Rates for Both Physical and Logical Interfaces
404
input-shaping-rate (Physical Interface)

Syntax
Hierarchy Level
Release Information
Description
For Gigabit Ethernet IQ2, Enhanced Queuing DPC, MIC, and MPC interfaces, configure input traffic shaping
by specifying the amount of bandwidth to be allocated to the physical interface. You can configure
hierarchical shaping, meaning you can apply an input shaping rate to both the physical interface and the
logical interface.
Options
g (1,000,000,000).

Configuring Input Shaping Rates for Both Physical and Logical Interfaces
405
input-traffic-control-profile
Syntax
Hierarchy Level

Release Information
Description
For Gigabit Ethernet IQ2 and IQ2E PIC, Enhanced Queuing DPC , MIC, and MPC interfaces, apply an input
traffic scheduling and shaping profile to the logical interface. The input-traffic-control-profile and
input-scheduler-map statements are mutually exclusive at the same hierarchy level.
NOTE: The shared-instance statement applies only to Gigabit Ethernet IQ2 and IQ2E PICs.
NOTE:
For an Enhanced Queuing (EQ) DPC on an MX Series router, CoS queuing and scheduling are
enabled on the egress side but disabled on the ingress side by default. To enable ingress CoS on
the EQ DPC, you must configure the traffic-manager statement with ingress-and-egress mode:

Options
profile-name—Name of the traffic-control profile to be applied to this interface.
instance-name—Name of the shared scheduler and shaper to be applied to this interface.

406

input-traffic-control-profile-remaining
Syntax
Hierarchy Level

[edit class-of-service interfaces interface-name interface-set interface-set-name]
Release Information
Description
For Enhanced Queuing DPC, MICs, or MPC interfaces on MX Series routers, or for IQ2E PICs interfaces
on M Series and T Series router, apply an input traffic scheduling and shaping profile for the remaining
traffic to the logical interface or interface set.
Options
profile-name—Name of the traffic-control profile for the remaining traffic to be applied to this interface
or interface set.


407
interface (DHCP Local Server)

Syntax
exclude;
overrides {
delay-advertise {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
}
delay-offer {
equals {
ascii ascii-string;
}
not-equals {
ascii ascii-string;
}
starts-with {
ascii ascii-string;
}
}
delay-time seconds;
408
}
rapid-commit;
}
trace;
}
Hierarchy Level

...],
Release Information
Options upto and exclude introduced in Junos OS Release 9.1.
Description
Specify one or more interfaces, or a range of interfaces, that are within a specified group on which the
DHCP local server is enabled. You can repeat the interface interface-name statement to specify multiple
interfaces within a group, but you cannot specify the same interface in more than one group. Also, you
cannot use an interface that is being used by the DHCP relay agent.
NOTE: DHCP values are supported in integrated routing and bridging (IRB) configurations. When
you configure an IRB interface in a network that is using DHCP, the DHCP information (for
example, authentication, address assignment, and so on) is propagated in the associated bridge
domain. This enables the DHCP server to configure client IP addresses residing within the bridge
domain. IRB currently supports only static DHCP configurations.
409
Options
exclude—Exclude an interface or a range of interfaces from the group. This option and the overrides option
are mutually exclusive.
interface-name—Name of the interface. You can repeat this option multiple times.
upto-interface-name—Upper end of the range of interfaces; the lower end of the range is the interface-name
entry. The interface device name of the upto-interface-name must be the same as the device name of the
interface-name.


Grouping Interfaces with Common DHCP Configurations
410
interface-set (Ethernet Interfaces)

Syntax
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
}
Hierarchy Level
[edit interfaces]
Release Information
Description
The set of interfaces used to configure hierarchical CoS schedulers on Ethernet interfaces on the MX
Series router and IQ2E PIC on M Series and T Series routers.
The remaining statements are described separately.


411
interface-set (Hierarchical Schedulers)

Syntax
excess-bandwidth-share (proportional value | equal);
internal-node;
output-traffic-control-profile profile-name;
output-traffic-control-profile-remaining profile-name;
}
Hierarchy Level
Release Information
Description
For Enhanced Queuing DPC, MIC, or MPC interfaces on MX Series routers, or for IQ2E PIC interfaces on
M Series routers, configure hierarchical schedulers for an interface set.
Options
interface-set-name—Name of the interface set.

Configuring Interface Sets

412
interface-set (IP Demux Interfaces)

Syntax
unit unit-number;
}
}
Hierarchy Level
[edit interfaces]
Release Information
Description
The set of interfaces used to configure hierarchical CoS schedulers for subscribers on IP demux interfaces
on the MX Series router.
The remaining statements are described separately.

Junos Subscriber Access Configuration Guide

Interfaces Fundamentals for Routing Devices
413
interfaces
List of Syntax
Syntax (QFX Series) on page 413
Syntax (EX Series, MX Series and T Series) on page 413
Syntax (QFX Series)
interfaces interface-name {
no-mac-learning;
}
Syntax (EX Series, MX Series and T Series)
interfaces { ... }
QFX Series
[edit ethernet-switching-options]
EX Series, MX Series and T Series
[edit]
Release Information
Description
Configure settings for interfaces that have been assigned to family ethernet-switching.
Default
The management and internal Ethernet interfaces are automatically configured. You must configure all
other interfaces.
Options
interface-name —Name of an interface that is configured for family ethernet-switching.
The remaining statement is explained separately. See CLI Explorer.

414

Physical Interface Properties Overview

Configuring Aggregated Ethernet Link Protection
415
interfaces (CoS)
Syntax
interfaces {
interface-name {
classifiers{
dscp(classifier-name | default) {
}
ieee-802.1 (classifier-name | default) vlan-tag (inner | outer | classifier-name);
}
irb {
classifiers {
type (classifier-name | default);
no-default;
}
rewrite-rules {
exp (rewrite-name | default)protocol protocol-types;
}
}
}
rewrite-rules {
ieee-802.1 (rewrite-name | default) vlan-tag (outer);
}
}
scheduler-map-chassis map-name;
shaping-rate rate;
classifiers {
type (classifier-name | default) family (mpls | inet);
}
forwarding-class class-name;
fragmentation-map map-name;
416

output-traffic-control-profile profile-name shared-instance instance-name;
per-session-scheduler;
policy-map policy-map-name;
rewrite-rules {
exp (rewrite-name | default) protocol protocol-types;
exp-push-push-push default;
exp-swap-push-push default;
}
shaping-rate rate;
translation-table (to-dscp-from-dscp | to-dscp-ipv6-from-dscp-ipv6 | to-exp-from-exp |
to-inet-precedence-from-inet-precedence) table-name;
}
}
excess-bandwidth-share;
internal-node;
output-traffic-control-profile profile-name;
}
}
Hierarchy Level
Release Information
Interface-set level added in Junos OS Release 8.5.
Description
Configure interface-specific CoS properties for incoming packets.
Options
417


418
interfaces (Static and Dynamic Subscribers)

Syntax
interfaces {
interface-name {
actual-transit-statistics;
auto-configure {
agent-circuit-identifier {
}
line-identity {
include {
accept-no-ids;
circuit-id;
remote-id;
}
}
}
family family {
address address;
direct-connect;
filter {
adf {
counter;
not-mandatory;
rule rule-value;
}
input filter-name {
}
}
}
419
rpf-check {
mode loose;
}
service {
input {
}
}
output {
}
}
}
}
filter {
input filter-name (
}
}
}
host-prefix-only;
ppp-options {
chap;
pap;
}
proxy-arp;
service {
pcef pcef-profile-name {
activate rule-name | activate-all;
}
}
420
targeted-options {
backup backup;
group group;
primary primary;
weight ($junos-interface-target-weight | weight-value);
}
vlan-id;
}
vlan-tagging;
}
unit logical unit number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
}
pppoe-underlying-options {
}
}
421
demux0 {
demux-options {
}
family family {
address address;
direct-connect;
demux-source {
source-prefix;
}
filter {
input filter-name (
}
}
}
rpf-check {
mode loose;
}
}
filter {
input filter-name;
output filter-name;
}
vlan-id number;
}
}
422
pp0 {
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface interface-name;
server;
}
ppp-options {
chap {
local-name name;
}
mru size;
pap;
password password;
username-include {
circuit-id;
domain-name name;
mac-address;
remote-id;
}
}
}
family inet {
address address;
service {
input {
}
}
423
output {
}
}
}
filter {
input filter-name {
}
}
}
}
}
}
stacked-interface-set {
interface-set-name interface-set-name {
interface-set-name interface-set-name;
}
}
}
Hierarchy Level
[edit dynamic-profiles profile-name]
Release Information
Description
Define interfaces for dynamic client profiles.
424
Options
interface-name—The interface variable ($junos-interface-ifd-name). The interface variable is dynamically
replaced with the interface the DHCP client accesses when connecting to the router.
NOTE: Though we do not recommend it, you can also enter the specific name of the interface
you want to assign to the dynamic profile.


Configuring Dynamic PPPoE Subscriber Interfaces
Configuring Dynamic VLANs Based on Agent Circuit Identifier Information
DHCP Subscriber Interface Overview
Subscribers over Static Interfaces Configuration Overview
425
internal-node
Syntax
internal-node;
Hierarchy Level
Release Information
Description
The statement is used to raise the interface set without children to the same level as the other configured
interface sets with children, allowing them to compete for the same set of resources.
Default
If you do not include this statement, the node is internal only if its children have a traffic control profile
configured.

Configuring Internal Scheduler Nodes

426
interpolate
Syntax
interpolate {
fill-level [values];
}
Hierarchy Level
Release Information
Description
Specify values for interpolating relationship between queue fill level and drop probability.
On EX Series switches, this statement is supported only on EX8200 standalone switches and EX8200
Virtual Chassis.

See Defining Packet Drop Behavior by Configuring RED Drop Profiles.

427
loss-priority (BA Classifiers)

Syntax
loss-priority level;
Hierarchy Level
[edit class-of-service classifiers type classifier-name forwarding-class class-name]
Release Information
Description
Specify packet loss priority value for a specific set of code-point aliases and bit patterns.
Options
level can be one of the following:
• high—Packet has high loss priority.
• medium-high—Packet has medium-high loss priority.
• medium-low—Packet has medium-low loss priority.
• low—Packet has low loss priority.


Configuring and Applying Tricolor Marking Policers
428
loss-priority (Scheduler Drop Profiles)

Syntax
loss-priority (any | high | low | medium-high | medium-low);
Hierarchy Level
[edit class-of-service schedulers scheduler-name drop-profile-map]
Release Information
Description
Specify a loss priority to which to apply a drop profile. The drop profile map sets the drop profile for a
specific PLP and protocol type. The inputs for the map are the PLP designation and the protocol type. The
output is the drop profile.
Options
any—The drop profile applies to packets with any PLP.
high—The drop profile applies to packets with high PLP.
low—The drop profile applies to packets with low PLP.
medium-high—The drop profile applies to packets with medium-high PLP.
medium-low—The drop profile applies to packets with medium-low PLP.
NOTE: On ACX Series Routers, if you configure the protocol as tcp, then the loss-priority (any
| high | low | medium-high) values are supported. If you configure the protocol with either non-tcp
or any option, then irrespective of the loss-priority value, only one drop-profile can be specified.

429

Configuring Schedulers for Priority Scheduling
protocol (Schedulers)
430
max-queues
Syntax
max-queues queues-per-line-card;
Hierarchy Level
[edit chassis fpc slot-number]
Release Information
Support for MPC7E, MPC8E, and MPC9E from Junos OS Release 15.1F4.
Description
Configure the maximum number of queues allowed per MPC1 Q, MPC2 Q, MPC2 EQ, MPC7E, MPC8E,
and MPC9E line cards in an MX240, MX480, MX960, MX2010, or MX2020 router or per 2-port or 4-port
10-Gigabit Ethernet fixed MIC with XFP in an MX5, MX10, MX40, or MX80 modular chassis router.
Reducing the number of queues allowed in a hierarchical scheduling environment in turn reduces the
degree of jitter in the queues.
CAUTION: Committing a change to the maximum number of queues on a line card

causes a reset of the line card.
Options
queues-per-line-card—Maximum number of queues allowed for the line card. Only the following keywords
are valid: 8k, 16k, 32k, 64k, 96k, 128k, 256k, 512k, 768k, or 1M.
• Built-in 10-Gigabit Ethernet MICs and MPC1 Q line cards support up to 128 K queues. You can use
this statement to configure the single Packet Forwarding Engine to support a lower maximum number
of queues.
• MPC2 Q and MPC2 EQ line cards support up to 256 K queues. You can use this statement to
configure the two Packet Forwarding Engines to support a lower maximum number of queues.
If you configure a keyword for a value that exceeds the number of queues supported by the line card
hardware, the system uses the maximum number of queues supported by the line card.
If the max-queues statement is not configured on MPC7E, MPC8E, and MPC9E, which is the default
mode, the MPC starts with a message similar to the following:
431
FPC 0 supports only port based queuing. A license is required for per-VLAN and hierarchical features.
If the max-queues statement is configured on MPC7E, MPC8E, and MPC9E and the value is less than
or equal to 32,000, the MPC starts with a message similar to the following:
FPC 0 supports port based queuing and is configured in 16384 queue mode. A limited per-VLAN
queuing license is required for per VLAN and hierarchical queuing features.
If the max-queues statement is configured on MPC7E, MPC8E, and MPC9E and the value is greater
than 32,000, the MPC starts with a message similar to the following:
FPC 0 supports port based queuing and is configured in 524288 queue mode. A full scale per-VLAN
queuing license is required for per VLAN and hierarchical queuing features.


MPC1 Q
MPC2 Q
MPC2 EQ
MIC/MPC Compatibility
10-Gigabit Ethernet MICs with XFP
432
max-queues-per-interface
Syntax
max-queues-per-interface (8 | 4);
Hierarchy Level
[edit chassis fpc slot-number pic pic-number],

[edit chassis lcc number fpc slot-number pic pic-number] (Routing Matrix)
Release Information
Support for TX Matrix and TX Matrix Plus added in Junos OS Release 9.6.
Description
On IQ, MPC, and DPC interfaces on M120, T320, T640, T1600, TX Matrix, and TX Matrix Plus routers,
or on MIC or MPC interfaces on MX Series routers, set the number of egress queues per port to four or
eight.
NOTE: If you include the max-queues-per-interface 8 statement, the configuration at the [edit
class-of-service] hierarchy level must also support eight queues per interface.
NOTE: When you include the max-queues-per-interface statement and commit the configuration,
all physical interfaces on the PIC/MIC are deleted and readded. Also, the PIC/MIC is restarted
automatically. You should change modes between four queues and eight queues only when
there is no active traffic going to the PIC/MIC.
By default, IQ PICs on T Series and M320 routers are restricted to a maximum of four egress queues per
interface. If you include the max-queues-per-interface 4 statement, you can configure all four ports and
configure up to four queues per port.
For Quad T3 and Quad E3 PICs and for 4-port OC3c/STM1 Type I and Type II PICs on M320 and T Series
routers, when you include the max-queues-per-interface 8 statement, you can configure up to eight queues
on ports 0 and 2. After you commit the configuration, the PIC goes offline and comes back online with
only ports 0 and 2 operational. No interfaces can be configured on ports 1 and 3.
433
NOTE: Starting from Junos OS Release 14.1R8, 14.2R6, 15.1F6, 15.1R3, 15.1R4, and 16.1R1,
the restricted queue PICs without the max-queues-per-interface configuration boot up with a
maximum of eight queues per port and two operational ports (port 0 and 2). PICs with restricted
queues include Quad T3 PIC, Quad E3 PIC, 4-port SONET/SDH OC3c/STM1 PIC, and 4-Port
OC3 and 1-port OC12 PICs with SFP.
On certain older MPCS (MPC1 Q, MPC1E Q, MPC2 Q, MPC2E Q), you can include the
max-queues-per-interface statement to set the number of queues per logical interface to four or eight.
Setting max-queues-per-interface 4 sets the MPC to have four queues per logical interface and provides
twice as many logical interfaces on the MPC as setting max-queues-per-interface 8.
NOTE: For consistency, max-queues-per-interface should not be set on MPCs starting from
Junos OS 14.1X51.

Configuring the Junos OS to Support Eight Queues on IQ Interfaces for T Series and M320 Routers
Configuring Up to 16 Custom Forwarding Classes
Enabling Eight Queues on ATM Interfaces
Configuring the Maximum Number of Queues for Trio MPC/MIC Interfaces
Example: Configuring CoS on SRX5000 Devices with an MPC
Example: Enabling Eight-Queue Class of Service on Redundant Ethernet Interfaces on SRX Series Devices in
a Chassis Cluster
434
member-link-scheduler
Syntax
Hierarchy Level

[edit logical-systems logical-system-name class-of-service interfaces interface-name],
[edit routing-instances routing-instance-name class-of-service interfaces interface-name]
Release Information
Description
Determines whether scheduler parameters for aggregated interface member links are applied in a replicated
or scaled manner.
Default
By default, scheduler parameters are scaled (in “equal division mode”) among aggregated interface member
links.
Options
replicate—Scheduler parameters are copied to each level of the aggregated interface member links.
scale—Scheduler parameters are scaled based on number of member links and applied each level of the
aggregated interface member links.

view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration.

435
mode (Layer 2 Tunneling Protocol Shaping)

Syntax
mode traffic-manager-mode;
Hierarchy Level
[edit chassis fpc slot-number pic pic-number traffic-manager],

[edit chassis lcc number fpc slot-number pic pic-number traffic-manager]
[edit chassis fpc slot-number pic pic-number port port-number traffic-manager], (MX80 and MX104 routers only)
Release Information
Statement introduced at the [edit chassis fpc slot-number pic pic-number port port-number traffic-manager]
hierarchy level on MX80 and MX104 routers in Junos OS Release 17.4R2.
Description
Enable shaping on an L2TP session.
Options
traffic-manager-mode—Configure CoS traffic manager mode of operation on this interface. This option has
the following suboptions:
egress-only—Enable CoS queuing and scheduling on the egress side for the PIC that houses the interface.
This is the default mode for an Enhanced Queuing (EQ) DPC on MX Series routers.
If ingress packet drops are observed at a high rate for an IQ2 or IQ2E PIC, configure the traffic-manager
statement to work in the egress-only mode.
ingress-and-egress—Enable CoS queuing and scheduling on both the egress and ingress sides for the PIC.
This is the default mode for IQ2 and IQ2E PICs on M Series and T Series routers.
Junos OS does not support ingress-and-egress mode on label-switched interfaces (LSIs) configured
with VPLS.
For EQ DPCs, you must configure the traffic-manager statement with ingress-and-egress mode to
enable ingress CoS on the EQ DPC. EQ DPCs have 250 ms of buffering, with only egress queuing
(default mode). When ingress-and-egress is configured, the buffer is partitioned as 50 ms for the
ingress direction and 200 ms for the egress direction.
session-shaping—(M10i and M120 routers only) Configure the IQ2 PIC mode for session-aware traffic
shaping to enable L2TP session shaping.

436


ingress-shaping-overhead
437
Syntax
Hierarchy Level
[edit class-of-service interfaces interface-name ],

[edit class-of-service interfaces interface-name unit logical-unit-number],
Release Information
interface-set option added for Enhanced Queuing DPCs on MX Series routers in Junos OS Release 8.5.
interface-set option added for MIC and MPC interfaces on MX Series routers in Junos OS Release 10.2.
Support on GRE tunnel interfaces configured on physical and logical interfaces on MICs or MPCs in MX
Series routers added in Junos OS Release 13.3.
Description
Apply the specified CoS traffic control profile (traffic scheduling and shaping configuration objects) to the
output traffic at the physical interface, logical interface, or interface set.
The statement is supported on the following interfaces:
• Channelized IQ PIC interfaces
• Gigabit Ethernet IQ, Gigabit Ethernet IQ2, and IQ2E PIC interfaces
• Link services IQ (LSQ) interfaces on Multiservices and Services PICs
• Enhanced Queuing DPC, MIC, and MPC interfaces on MX Series routers
• GRE tunnel interfaces configured on physical or logical interfaces hosted on MIC or MPC line cards in
MX Series routers.
NOTE: Interface sets (sets of interfaces used to configure hierarchical CoS schedulers on
supported Ethernet interfaces) are not supported on GRE tunnel interfaces.
The shared-instance statement is supported on Gigabit Ethernet IQ2 PICs only.
Options
profile-name—Name of the traffic-control profile to be applied to this interface.
438
shared-instanceinstance-name—Name of the shared scheduler and shaper to be applied to this interface.


Configuring Hierarchical Schedulers for CoS | 13 (Enhanced Queuing DPC, MIC, and MPC interfaces
on MX Series routers)
Configuring Interface Sets (Enhanced Queuing DPC, MIC, and MPC interfaces on MX Series routers)
439
output-traffic-control-profile-remaining
Syntax
Hierarchy Level

Release Information
Support on GRE tunnel interfaces configured on physical interfaces on MICs or MPCs in MX Series routers
added in Junos OS Release 13.3.
Description
Apply the specified traffic control profile (traffic scheduling and shaping configuration objects) to the
remaining output traffic at the physical interface or interface set. The remaining traffic is transmitted by
the default interface or interface set.
This statement is supported on the following interfaces:
• IQ2E PIC interfaces on M Series and T Series routers
• Enhanced Queuing DPC, MICs, and MPC interfaces on MX Series routers
• GRE tunnel interfaces configured on physical interfaces hosted on MIC or MPC line cards in MX Series
routers.
NOTE: Interface sets (sets of interfaces used to configure hierarchical CoS schedulers on
supported Ethernet interfaces) are not supported on GRE tunnel interfaces.
You can map the TCP to the interface or interface set by using the output-traffic-control-profile-remaining
statement to explicitly configure the queues of the default interface or interface set scheduler that transmits
the remaining traffic.
Options
profile-name—Name of the traffic-control profile for remaining traffic to be applied to this interface or
interface set.

440

Configuring Remaining Common Queues on MIC and MPC Interfaces
441
overhead-accounting
Syntax
overhead-accounting {
bytes bytes;
cell-mode cell-mode-bytes cell-mode-bytes;
frame-mode frame-mode-bytes frame-mode-bytes;
}
Hierarchy Level
Release Information
Description
Configure the mode to shape downstream ATM traffic based on either frames or cells.
Default
The default is frame-mode.
Options

Configuring Static Shaping Parameters to Account for Overhead in Downstream Traffic Rates
Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates
442
pap (Dynamic PPP)

Syntax
pap;
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” ppp-options],

[edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-interface-unit” ppp-options]
Release Information
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit
“$junos-interface-unit” ppp-options] hierarchy level introduced in Junos OS Release 12.2.
Description
Specify PAP authentication in a PPP dynamic profile.


Configuring Dynamic Authentication for PPP Subscribers
Attaching Dynamic Profiles to Static PPP Subscriber Interfaces
Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface
443
peak-rate
Syntax
peak-rate rate;
Hierarchy Level
Release Information
Description
(MX Series routers) Define ATM peak cell rate on ATM MICs in cells per second by entering a decimal
number followed by the abbreviation c; where 1 cps = 384 bps.
Options
rate—ATM peak rate in cells per second.
Range: 61 cps through 353,206 cps.
Range: (MX Series with MPCs and ATM MICs with SFP) 61 cps through 1,412,829 cps
NOTE: Beginning with Junos OS Release 14.2, to configure OC12 CBR bandwidth speed per virtual
circuit (VC) on an ATM MIC with SFP (MIC-3D-8OC3-2OC12-ATM), specify up to 1,412,829
cps as the ATM peak cell rate.

show class-of-service traffic-control-profile

444
per-unit-scheduler
Syntax
per-unit-scheduler;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 13.2 on 16x10GE MPC and MPC3E line cards.
Statement introduced in Junos OS Release 13.2 on PTX Series Packet Transport Routers.
Statement introduced in Junos OS Release 13.3 on MPC4E line cards.
Statement introduced in Junos OS Release 15.1 on MPC6E line cards.
Description
For Channelized OC3 IQ, Channelized OC12 IQ, Channelized STM1 IQ, Channelized T3 IQ, Channelized
E1 IQ, E3 IQ, link services IQ interfaces (lsq-), Gigabit Ethernet IQ, Gigabit Ethernet IQ2 and IQ2-E, and
10-, 40-, and 100-Gigabit Ethernet interfaces (including the 16x10GE MPC), enable the association of
scheduler maps with logical interfaces.
CAUTION: Turning on per-unit scheduling causes the interface to reinitialize, which

means all logical interfaces (units) on the interface are deleted and recreated.
NOTE: To enable per-unit scheduling on MX80 and MX104 routers, configure the
per-unit-scheduler statement at each member physical interface level of a particular aggregated
Ethernet interface as well as at that aggregated Ethernet interface level. On other routing
platforms, it is enough if you include this statement at the aggregated Ethernet interface level.
NOTE: Per-unit scheduling is not supported on T1 interfaces configured on the Channelized

OC12 IQ PIC.
445
NOTE: On Gigabit Ethernet IQ2 and IQ2-E PICs without the per-unit-scheduler statement, the
entire PIC supports 4071 VLANs and the user can configure all the VLANs on the same port.
On Gigabit Ethernet IQ2 and IQ2-E PICs with the per-unit-scheduler statement, the entire PIC
supports 1024 – 2 * number of ports (1024 minus two times the number of ports), because each
port is allocated two default schedulers.
When including the per-unit-scheduler statement, you must also include the vlan-tagging statement or
the flexible-vlan-tagging statement (to apply scheduling to VLANs) or the encapsulation frame-relay
statement (to apply scheduling to DLCIs) at the [edit interfaces interface-name] hierarchy level.

Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs

vlan-tagging
Example: Applying Scheduling and Shaping to VLANs
Configuring Virtual LAN Queuing and Shaping on PTX Series Routers
446
pool (Address-Assignment Pools)

Syntax
pool pool-name {
active-drain;
family family {
dhcp-attributes {
[ protocol-specific attributes ]
}
host hostname {
}
network ip-prefixprefix-length>;
prefix ipv6-prefix;
range range-name {
high upper-limit;
low lower-limit;
}
}
hold-down;
link pool-name;
}
Hierarchy Level
[edit access address-assignment]
Release Information
Description
Configure the name of an address-assignment pool.
NOTE: Subordinate statement support depends on the platform. See individual statement topics
for more detailed support information.
447
Options
pool-name—Name assigned to the address-assignment pool.
active-drain—(MX Series only) Starting in Junos OS Release 17.2, configure the DHCP local server to stop
allocating addresses from this pool. When this is configured, the DHCP local server gracefully shifts
clients from this address pool to an alternative pool for which active drain is not configured. When
existing clients with an address from this pool submit a DHCPv4 request or DHCPv6 renew, they
receive a NAK, forcing them to renegotiate. The server responds with a DHCPv4 offer or DHCPv6
advertise message with an address from a different pool.
family —Configure the protocol family for the address-assignment pool.
The options for this statement are explained separately. Click the linked statement for details.
hold-down—(MX Series only) Starting in Junos OS Release 16.1, configure an address-assignment pool
that is currently in use to be unavailable for further address allocation. When a pool is in the hold-down
state, the pool is no longer used to allocate IP addresses for subscribers. Current subscribers who
previously obtained an address from the pool are not affected; they can continue to renew their leases.
As each of these users disconnects, their address is not reallocated. The pool becomes inactive when
all subscribers have disconnected and their addresses are returned to the pool.
link—(M Series, MX Series, SRX Series, T Series only) Designate a secondary address-assignment pool that
is linked to the pool being configured. When the pool being configured has no addresses available for
allocation, the secondary pool can be searched for a free address. You can configure a chain of linked
pools, but you cannot directly link more than one pool to or from any other pool. Each linked pool in
the chain serves as a backup pool for the pool immediately before it in the chain.
Values: pool-name—Name assigned to the secondary address-assignment pool.


Configuring Address-Assignment Pool Linking
Address Allocation from Linked Address Pools
Configuring DHCP Local Address Pool Rapid Drain
Attributes That Can Be Applied to DHCP Clients
448
pppoe-options (Dynamic PPPoE)

Syntax
pppoe-options {
server;
}
Hierarchy Level
Release Information
Description
Configure the underlying interface and PPPoE server mode for a dynamic PPPoE logical interface in a
dynamic profile.


Configuring Dynamic PPPoE Subscriber Interfaces
449
ppp-options (Dynamic PPP)

Syntax
ppp-options {
chap {
local-name name;
}
lcp-connection-update;
mru size;
pap;
password password;
username-include {
circuit-id;
domain-name name;
mac-address;
remote-id;
}
}
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-interface-unit”].

Release Information
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit
“$junos-interface-unit”] hierarchy level introduced in Junos OS Release 12.2.
Description
Configure PPP-specific interface properties in a dynamic profile.
450
NOTE:
PPP options can also be configured in a group profile with the ppp-options (L2TP) statement.
The following behavior determines the interaction between the PPP options configured in a
group profile and the PPP options configured in a dynamic profile:
• When PPP options are configured only in the group profile, the group profile options are
applied to the subscriber.
• When PPP options are configured in both a group profile and a dynamic profile, the dynamic
profile configuration takes complete precedence over the group profile when the dynamic
profile includes one or more of the PPP options that can be configured in the group profile.
Complete precedence means that there is no merging of options between the profiles. The
group profile is applied to the subscriber only when the dynamic profile does not include any
PPP option available in the group profile.
Options
lcp-connection-update—Enable PPP to act on a Connection-Status-Message VSA (26–218) received by
authd in either a RADIUS Access-Accept message or a CoA message. PPP conveys the contents of
the VSA in an LCP Connection-Update-Request message to the remote peer, such as a home gateway.
This action requires the following to be true:
• At least the first address family has been successfully negotiated and the session is active.
• The router LCP is in the Opened state.
Otherwise PPP takes no action on the VSA. If you do not enable the lcp-connection-update option,
PPP processes the notification from authd, but takes no action.
Default: Disabled

451

Configuring Dynamic Authentication for PPP Subscribers
Attaching Dynamic Profiles to Static PPP Subscriber Interfaces
Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface
452
priority (Schedulers)
Syntax
Hierarchy Level
Release Information
Description
Specify the packet-scheduling priority value.
Options
priority-level can be one of the following:
• low—Scheduler has low priority.
• medium-low—Scheduler has medium-low priority.
• medium-high—Scheduler has medium-high priority.
• high—Scheduler has high priority. Assigning high priority to a queue prevents the queue from being
underserved.
• strict-high—Scheduler has strictly high priority. Configure a high priority queue with unlimited transmission
bandwidth available to it. As long as it has traffic to send, the strict-high priority queue receives
precedence over low, medium-low, and medium-high priority queues, but not high priority queues. You
can configure strict-high priority on only one queue per interface.
NOTE: The strict-high priority level is the only priority level supported on ACX Series Routers.
However, multiple strict-high priority queues can be configured per interface on ACX Series
Routers.

453
Configuring Schedulers for Priority Scheduling

454
profile (Access)
Syntax
profile profile-name {
accounting {
address-change-immediate-update
accounting-stop-on-access-deny;
accounting-stop-on-failure;
ancp-speed-change-immediate-update;
coa-immediate-update;
coa-no-override service-class-attribute;
duplication;
duplication-filter;
duplication-vrf {
access-profile-name profile-name;
vrf-name vrf-name;
}
immediate-update;
order [ accounting-method ];
send-acct-status-on-config-change;
statistics (time | volume-time);
update-interval minutes;
wait-for-acct-on-ack;
}
accounting-order (radius | [accounting-order-data-list]);
authentication-order [ authentication-methods ];
client client-name {
chap-secret chap-secret;
group-profile profile-name;
ike {
allowed-proxy-pair {
remote remote-proxy-address local local-proxy-address;
}
pre-shared-key (ascii-text character-string | hexadecimal hexadecimal-digits);
ike-policy policy-name;
interface-id string-value;
}
l2tp {
aaa-access-profile profile-name;
interface-id interface-id;
lcp-renegotiation;
local-chap;
maximum-sessions number;
maximum-sessions-per-tunnel number;
455
multilink {
drop-timeout milliseconds;
fragment-threshold bytes;
}
override-result-code session-out-of-resource;
ppp-authentication (chap | pap);
ppp-profile profile-name;
service-profile profile-name(parameter)&profile-name;
sessions-limit-group limit-group-name;
shared-secret shared-secret;
}
pap-password pap-password;
ppp {
cell-overhead;
encapsulation-overhead bytes;
framed-ip-address ip-address;
framed-pool framed-pool;
interface-id interface-id;
keepalive seconds;
primary-dns primary-dns;
primary-wins primary-wins;
secondary-dns secondary-dns;
secondary-wins secondary-wins;
}
user-group-profile profile-name;
}
domain-name-server;
domain-name-server-inet;
domain-name-server-inet6;
local {
flat-file-profile profile-name;
}
preauthentication-order preauthentication-method;
provisioning-order (gx-plus | jsrc | pcrf);
456
radius {
accounting-server [ ip-address ];
attributes {
exclude {
attribute-name packet-type;
standard-attribute number {
packet-type [ access-request | accounting-off | accounting-on | accounting-start | accounting-stop ];
}
vendor-id id-number {
vendor-attribute vsa-number {
}
}
}
ignore {
dynamic-iflset-name;
framed-ip-netmask;
idle-timeout;
input-filter;
logical-system:routing-instance;
output-filter;
session-timeout;
standard-attribute number;
vendor-attribute vsa-number;
}
}
}
authentication-server [ ip-address ];
options {
accounting-session-id-format (decimal | description);
calling-station-id-delimiter delimiter-character;
calling-station-id-format {
agent-circuit-id;
agent-remote-id;
interface-description;
interface-text-description;
mac-address;
nas-identifier;
stacked-vlan;
vlan;
}
chap-challenge-in-request-authenticator;
client-accounting-algorithm (direct | round-robin);
457
client-authentication-algorithm (direct | round-robin);

coa-dynamic-variable-validation;
ethernet-port-type-virtual;
interface-description-format {
exclude-adapter;
exclude-channel;
exclude-sub-interface;
}
juniper-access-line-attributes;
nas-identifier identifier-value;
nas-port-extended-format {
adapter-width width;
ae-width width;
port-width width;
pw-width width;
slot-width width;
stacked-vlan-width width;
vlan-width width;
atm {
port-width width:
slot-width width;
vci-width width:
vpi-width width;
}
}
nas-port-id-delimiter delimiter-character;
nas-port-id-format {
agent-circuit-id;
agent-remote-id;
nas-identifier;
order {
agent-circuit-id;
agent-remote-id;
nas-identifier;
postpend-vlan-tags;
}
postpend-vlan-tags;
}
458
nas-port-type {
ethernet {
port-type;
}
}
override {
calling-station-id remote-circuit-id;
nas-ip-address tunnel-client-gateway-address;
nas-port tunnel-client-nas-port;
nas-port-type tunnel-client-nas-port-type;
}
remote-circuit-id-delimiter;
remote-circuit-id-fallback {
remote-circuit-id-format;
agent-circuit-id;
agent-remote-id;
}
revert-interval interval;
service-activation {
dynamic-profile (optional-at-login | required-at-login);
extensible-service (optional-at-login | required-at-login);
}
vlan-nas-port-stacked-format;
}
preauthentication-server ip-address;
}
radius-server server-address {
accounting-port port-number;
accounting-retry number;
accounting-timeout seconds;
dynamic-request-port
port port-number;
preauthentication-port port-number;
preauthentication-secret password;
retry attempts;
routing-instance routing-instance-name;
secret password;
max-outstanding-requests value;
source-address source-address;
timeout seconds;
}
459
service {
accounting {
statistics (time | volume-time);
update-interval minutes;
}
accounting-order (activation-protocol | local | radius);
}
session-limit-per-username number;
session-options {
client-idle-timeout minutes;
client-idle-timeout-ingress-only;
client-session-timeoutminutes;
pcc-context {
input-service-filter-name filter-name;
input-service-set-name service-set-name;
ipv6-input-service-filter-name filter-name;
ipv6-input-service-set-name service-set-name;
ipv6-output-service-filter-name filter-name;
ipv6-output-service-set-name service-set-name;
output-service-filter-name filter-name;
output-service-set-name service-set-name;
profile-name pcef-profile-name;
}
strip-user-name {
delimiter [ delimiter ];
parse-direction (left-to-right | right-to-left);
}
}
subscriber username {
delegated-pool delegated-pool-name;
framed-ip-address ipv4-address;
framed-ipv6-pool ipv6-pool-name;
framed-pool ipv4-pool-name;
password password;
target-logical-system logical-system-name <target-routing-instance (default | routing-instance-name>;
target-routing-instance (default | routing-instance-name);
}
}
Hierarchy Level
[edit access]
460
Release Information
Description
Configure a subscriber access profile that includes subscriber access, L2TP, or PPP properties.
Options
profile-name—Name of the profile.
For CHAP, the name serves as the mapping between peer identifiers and CHAP secret keys. This entity
is queried for the secret key whenever a CHAP challenge or response is received.

Configuring the PPP Authentication Protocol

Configuring Access Profiles for L2TP or PPP Parameters
Configuring L2TP Properties for a Client-Specific Profile
Configuring an L2TP Access Profile on the LNS
Configuring an L2TP LNS with Inline Service Interfaces
Configuring PPP Properties for a Client-Specific Profile
Configuring Service Accounting with JSRC
Configuring Service Accounting in Local Flat Files
AAA Service Framework Overview
Enabling Direct PCC Rule Activation by a PCRF for Subscriber Management
461
protocols
Syntax
protocols {
bgp {
... bgp-configuration ...
}
isis {
... isis-configuration ...
}
ldp {
... ldp-configuration ...
}
mpls {
... mpls -configuration ...
}
msdp {
... msdp-configuration ...
}
mstp {
... mstp-configuration ...
}
ospf {
domain-id domain-id;
domain-vpn-tag number;
route-type-community (iana | vendor);
traffic-engineering {
<advertise-unnumbered-interfaces>;
<credibility-protocol-preference>;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
shortcuts {
lsp-metric-into-summary;
}
}
... ospf-configuration ...
}
ospf3 {
domain-id domain-id;
domain-vpn-tag number;
route-type-community (iana | vendor);
traffic-engineering {
<advertise-unnumbered-interfaces>;
462
<credibility-protocol-preference>;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
shortcuts {
lsp-metric-into-summary;
}
}
... ospf3-configuration ...
}
pim {
... pim-configuration ...
}
rip {
... rip-configuration ...
}
ripng {
... ripng-configuration ...
}
rstp {
rstp-configuration;
}
rsvp{
... rsvp-configuration ...
}
vstp {
vstp configuration;
}
vpls {
vpls configuration;
}
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name],

[edit routing-instances routing-instance-name]
463
Release Information
Support for RIPng introduced in Junos OS Release 9.0.
mpls and rsvp options added in Junos OS Release 15.1.
Description
Specify the protocol for a routing instance. You can configure multiple instances of many protocol types.
Not all protocols are supported on the switches. See the switch CLI.
Options
bgp—Specify BGP as the protocol for a routing instance.
isis—Specify IS-IS as the protocol for a routing instance.
ldp—Specify LDP as the protocol for a routing instance or for a virtual router instance.
l2vpn—Specify Layer 2 VPN as the protocol for a routing instance.
mpls—Specify MPLS as the protocol for a routing instance.
msdp—Specify the Multicast Source Discovery Protocol (MSDP) for a routing instance.
mstp—Specify the Multiple Spanning Tree Protocol (MSTP) for a virtual switch routing instance.
ospf—Specify OSPF as the protocol for a routing instance.
ospf3—Specify OSPF version 3 (OSPFv3) as the protocol for a routing instance.
NOTE: OSPFv3 supports the no-forwarding, virtual-router, and vrf routing instance types only.
pim—Specify the Protocol Independent Multicast (PIM) protocol for a routing instance.
rip—Specify RIP as the protocol for a routing instance.
ripng—Specify RIP next generation (RIPng) as the protocol for a routing instance.
rstp—Specify the Rapid Spanning Tree Protocol (RSTP) for a virtual switch routing instance.
rsvp—Specify the RSVP for a routing instance.
vstp—Specify the VLAN Spanning Tree Protocol (VSTP) for a virtual switch routing instance.
vpls—Specify VPLS as the protocol for a routing instance.

464

Example: Configuring Multiple Routing Instances of OSPF

465
proxy-arp
Syntax
proxy-arp (restricted | unrestricted);
Hierarchy Level

Release Information
restricted added in Junos OS Release 10.0 for EX Series switches.
Description
For Ethernet interfaces only, configure the router or switch to respond to any ARP request, as long as the
router or switch has an active route to the ARP request’s target address.
NOTE: You must configure the IP address and the inet family for the interface when you enable
proxy ARP.
Default
Proxy ARP is not enabled. The router or switch responds to an ARP request only if the destination IP
address is its own.
Options
• none—The router or switch responds to any ARP request for a local or remote address if the router or
switch has a route to the target IP address.
• restricted—(Optional) The router or switch responds to ARP requests in which the physical networks of
the source and target are different and does not respond if the source and target IP addresses are in the
same subnet. The router or switch must also have a route to the target IP address.
• unrestricted—(Optional) The router or switch responds to any ARP request for a local or remote address
if the router or switch has a route to the target IP address.
Default: unrestricted

466

Configuring Restricted and Unrestricted Proxy ARP

Configuring Proxy ARP on Switches
Example: Configuring Proxy ARP on an EX Series Switch
Configuring Gratuitous ARP
467
qos-adjust-hierarchical
Syntax
qos-adjust-hierarchical [interface-set];
Hierarchy Level
[edit dynamic-profiles dynamic-profile-name access-cac interface $junos-interface-name]
Release Information
Statement introduced in Junos OS Release 17.2R1.
Description
Specify that multicast QoS adjustments received on the subscriber contribute to hierarchical QoS
adjustments.
Options
interface-set—(Optional) Specify that the immediate parent interface-set receive QoS adjustments.
NOTE: For any multicast-enabled interface, only directly stacked interface-set parents are
adjusted. The following scenario is not supported: multicast-enabled client interface is stacked
over a VLAN interface and the VLAN interface in turn is stacked over and interface-set.

468
queue (Global Queues)

Syntax
queue queue-number class-name;
Hierarchy Level
[edit class-of-service forwarding-classes]
Release Information
Description
Specify the output transmission queue to which to map all input from an associated forwarding class.
On M120, M320, MX Series, T Series routers and on EX Series switches, this statement enables you to
configure up to eight forwarding classes with one-to-one mapping to output queues. If you want to
configure up to 16 forwarding classes with multiple forwarding classes mapped to single output queues,
include the class statement instead of the queue statement at the [edit class-of-service forwarding-classes]
hierarchy level.
Options
class-name—Name of forwarding class.
queue-number—Output queue number.

Range: 0 through 7. For M Series routers and some T Series router PICs, 0 through 3.

Configuring a Custom Forwarding Class for Each Queue

class (Forwarding Classes)
469
radius (Access Profile)

Syntax
radius {
accounting-server [ ip-address ];
attributes {
exclude
attribute-name packet-type;
standard-attribute number {
}
vendor-attribute vsa-number {
}
}
}
ignore {
dynamic-iflset-name;
framed-ip-netmask;
idle-timeout;
input-filter;
logical-system-routing-instance;
output-filter;
session-timeout;
standard-attribute number;
vendor-attribute vsa-number;
}
}
}
authentication-server [ ip-address ];
options {
accounting-session-id-format (decimal | description);
calling-station-id-delimiter delimiter-character;
calling-station-id-format {
agent-circuit-id;
agent-remote-id;
nas-identifier;
}
chap-challenge-in-request-authenticator;
client-accounting-algorithm (direct | round-robin);
client-authentication-algorithm (direct | round-robin);
470
coa-dynamic-variable-validation;
ethernet-port-type-virtual;
interface-description-format {
exclude-adapter;
exclude-channel;
exclude-sub-interface;
}
ip-address-change-notify message;
juniper-access-line-attributes;
nas-identifier identifier-value;
nas-port-extended-format {
ae-width width;
port-width width;
slot-width width;
stacked-vlan-width width;
vlan-width width;
atm {
port-width width:
slot-width width;
vci-width width:
vpi-width width;
}
}
nas-port-id-delimiter delimiter-character;
nas-port-id-format {
agent-circuit-id;
agent-remote-id;
nas-identifier;
order {
agent-circuit-id;
agent-remote-id;
nas-identifier;
postpend-vlan-tags;
}
postpend-vlan-tags;
}
471
nas-port-type {
ethernet {
port-type;
}
}
override {
calling-station-id remote-circuit-id;
nas-ip-address tunnel-client-gateway-address;
nas-port tunnel-client-nas-port;
nas-port-type tunnel-client-nas-port-type;
}
remote-circuit-id-delimiter;
remote-circuit-id-fallback;
remote-circuit-id-format {
agent-circuit-id;
agent-remote-id;
}
revert-interval interval;
service-activation {
dynamic-profile (optional-at-login | required-at-login);
extensible-service (optional-at-login | required-at-login);
}
vlan-nas-port-stacked-format;
}
preauthentication-server ip-address;
}
Hierarchy Level
Release Information
Description
Configure the RADIUS parameters that the router uses for AAA authentication and accounting for
subscribers.
472
Options
accounting-server—(MX Series only) Specify a list of the RADIUS accounting servers used for accounting
for DHCP, L2TP, and PPP clients.
Values: ip-address—IP version 4 (IPv4) address.
authentication-server—(SRX Series only) Specify a list of the RADIUS authentication servers used to
authenticate DHCP, L2TP, and PPP clients. The servers in the list are also used as RADIUS
dynamic-request servers, from which the router accepts and processes RADIUS disconnect requests,
CoA requests, and dynamic service activations and deactivations.
Values: ip-address—IPv4 address.
preauthentication-server—(MX Series only) Starting in Junos OS Release 13.3, specify the RADIUS
preauthentication server, which is used for the LLID service.
NOTE: You cannot configure this statement if the Calling-Station-ID attribute is excluded from
RADIUS Access-Request messages by the exclude statement.
Values: ip-address—IPv4 address.

Configuring Authentication and Accounting Parameters for Subscriber Access

RADIUS Logical Line Identifier (LLID) Overview
Configuring Logical Line Identification (LLID) Preauthentication
473
radius-server
Syntax
radius-server server-address {
accounting-port port-number;
accounting-retry number;
accounting-timeout seconds;
dynamic-request-port port-number;
max-outstanding-requests value;
port port-number;
preauthentication-port port-number;
preauthentication-secret password;
retry attempts;
routing-instance routing-instance-name;
secret password;
source-address source-address;
timeout seconds;
}
Hierarchy Level
[edit access],
Release Information
max-outstanding-requests introduced in Junos OS Release 11.4.
accounting-retry and accounting-timeout introduced in Junos OS Release 14.1.
dynamic-request-port option added in Junos OS Release 14.2R1 for MX Series routers.
preauthentication-port and preauthentication-secret options added in Junos OS Release 15.1 for MX
Series routers.
accounting-port introduced in Junos OS Release 13.2X50-D10 for EX Series switches with support for
Enhanced Layer 2 software (ELS). It was introduced in Junos OS without ELS in the following releases:
Junos OS Releases 12.3R10, 14.1X53-D25, and 15.1R4 for EX Series switches.
Support for IPv6 server-address introduced in Junos OS Release 16.1.
Description
Configure RADIUS for subscriber access management, L2TP, or PPP.
474
To configure multiple RADIUS servers, include multiple radius-server statements. The servers are tried in
order and in a round-robin fashion until a valid response is received from one of the servers or until all the
configured retry limits are reached.
475
Options
server-address—IPv4 or IPv6 address of the RADIUS server.
accounting-port—(EX Series, M Series, MX Series, PTX Series, T Series only) Configure the port number
on which to contact the RADIUS accounting server. This statement was introduced in Junos OS Release
13.2X50-D10 for EX Series switches with support for Enhanced Layer 2 software (ELS). It was
introduced in Junos OS without ELS in the following releases: Junos OS Releases 12.3R10,
14.1X53-D25, and 15.1R4 for EX Series switches.
NOTE: Specifying the accounting port is optional, and port 1813 is the default. However, we
recommend that you configure it in order to avoid confusion, as some RADIUS servers might
refer to an older default.
Values: port-number—Port number on which to contact the RADIUS accounting server. Most RADIUS
servers use port 1813, as specified in RFC 2866.
Default: 1813
accounting-retry—(MX Series, T Series only) Starting in Junos OS Release 14.1, configure the number of
times the device retransmits RADIUS accounting messages when no response is received from the
server. When you do not configure this statement, the number of retry attempts is determined by the
retry statement.
NOTE: To successfully set a retry limit for the accounting servers different from the
authentication servers, you must configure both the accounting-retry and accounting-timeout
statements . If you configure only one of these statements, then the value you configure is
ignored in favor of the values configured with the retry and timeout statements.
NOTE: The maximum retry duration (the number of retries times the length of the timeout)
cannot exceed 2700 seconds. An error message is displayed if you configure a longer duration.
Values: number—Number of retry attempts.

Default: 0 (disabled)
accounting-timeout—(MX Series, T Series only) Starting in Junos OS Release 14.1, configure how long the
local device waits to receive a response from a RADIUS accounting server before retransmitting the
message. When you do not configure this statement, the length of the timeout is determined by the
timeout statement.
476
NOTE: To successfully set a timeout value for the accounting servers different from the
Values: seconds—Duration of timeout period.

Range: 0 through 1000 seconds
Default: 0 (disabled)
dynamic-request-port—(MX Series only) Starting in Junos OS Release 14.2R1, specify the port that the
router monitors for dynamic (CoA) requests from the specified RADIUS servers. You can configure a
port globally or for a specific access profile.
You must either use the default port for all RADIUS servers or configure the same nondefault port for
all RADIUS servers. This rule applies at both the global access and access profile levels.
NOTE: Any other configuration results in a commit check failure. Multiple port numbers—that
is, different port numbers for different servers—are not supported.
Values: port-number—Number of the monitored port.

Default: 3799 (as specified in RFC 5176)
max-outstanding-requests—(MX Series only) Starting in Junos OS Release 11.4, configure the maximum
number of outstanding requests for this RADIUS server. An increase in this value is immediate while
a decrease is more gradual if the current number of outstanding requests exceeds the new value.
Values: requests—Maximum number of outstanding requests for this RADIUS server.
Range: 0 through 2000 outstanding requests per server
Default: 1000 outstanding requests per server
port—(EX Series, M Series, MX Series, SRX Series, T Series only) Configure the port number on which to
contact the RADIUS server.
Values: port-number—Port number on which to contact the RADIUS server.
Default: 1812 (as specified in RFC 2865)
477
preauthentication-port—(MX Series only) Starting in Junos OS Release 15.1 for MX Series routers, configure
the port number on which to contact the RADIUS server for logical line identification (LLID)
preauthentication requests. If you do not configure a separate UDP port for preauthentication purposes,
the same UDP port that you configure for authentication messages by including the port port-number
statement is used.
Values: port-number—Port number used for preauthentication requests to contact the RADIUS server.
preauthentication-secret—(MX Series only) Starting in Junos OS Release 15.1 for MX Series routers,
configure the password to use with the RADIUS server for LLID preauthentication requests. If you do
not configure a separate UDP password for preauthentication purposes, the same password that you
configure for authentication messages by including the secret password statement is used. The secret
password used by the local router must match that used by the server.
Values: password—Password to use. To include spaces enclose the character string in quotation marks.
retry—(EX Series, M Series, MX Series, PTX Series, T Series only) Specify the number of times that the
device is allowed to attempt to contact a RADIUS authentication or accounting server. You can override
the retry limit for accounting servers with the accounting-retry statement.
NOTE: To successfully set a retry limit for the accounting servers different from the
Values: attempts—Number of times that the router is allowed to attempt to contact a RADIUS server.
Default: 3
routing-instance—(SRX Series, vSRX only) Configure the routing instance used to send RADIUS packets
to the RADIUS server.
Values: routing-instance-name—Routing instance name.
source-address—(SRX Series, vSRX only) Configure a source address for each configured RADIUS server.
Each RADIUS request sent to a RADIUS server uses the specified source address. Support for IPv6
source-address was introduced in Junos OS Release 16.1.
Values: source-address—Valid IPv4 or IPv6 address configured on one of the router or switch interfaces.
On M Series routers only, the source address can be an IPv6 address and the UDP source port is 514.
478
timeout—(SRX Series, vSRX only) Configure the amount of time that the local device waits to receive a
response from RADIUS authentication and accounting servers. You can override the timeout value
for accounting servers with the accounting-timeout statement.
NOTE: To successfully set a timeout value for the accounting servers different from the
Values: seconds—Amount of time to wait.

Range: 1 through 1000 seconds
Default: 3 seconds


Configuring the PPP Authentication Protocol
Configuring RADIUS Authentication for L2TP
Configuring RADIUS System Accounting
Configuring RADIUS-Initiated Dynamic Request Support
RADIUS Logical Line Identifier (LLID) Overview
RADIUS Attributes for LLID Preauthentication Requests
show network-access aaa statistics
clear network-access aaa statistics
479
range (Address-Assignment Pools)

Syntax
range range-name {
high upper-limit;
low lower-limit;
}
Hierarchy Level
[edit access address-assignment pool pool-name family (inet | inet6)]
Release Information
IPv6 support introduced in Junos OS Release 10.0.
Description
Configure a named range of IPv4 addresses or IPv6 prefixes, used within an address-assignment pool.
Options
high upper-limit—Upper limit of an address range or IPv6 prefix range.
low lower-limit—Lower limit of an address range or IPv6 prefix range.
prefix-length prefix-length—Assigned length of the IPv6 prefix.
range-name—Name assigned to the range of IPv4 addresses or IPv6 prefixes.

Configuring a Named Address Range for Dynamic Address Assignment

480
ranges (Dynamic VLAN)

Syntax
ranges (any | low-tag)-(any | high-tag);
Hierarchy Level
[edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name]
Release Information
Description
Configure VLAN ranges for dynamic, auto-sensed VLANs.
Options
any—The entire VLAN range.
low-tag—The lower limit of the VLAN range.
high-tag—The upper limit of the VLAN range.


481
rewrite-rules (Definition)
Syntax
rewrite-rules {
type rewrite-name {
import (rewrite-name | default);
loss-priority level code-point [ aliases ] [ bit-patterns ];
}
}
}
Hierarchy Level
Release Information
ieee-802.1ad option introduced in Junos OS Release 9.2.
Description
Specify a rewrite-rules mapping for the traffic that passes through all queues on the interface.
Options
rewrite-name—Name of a rewrite-rules mapping.
Values: dscp, dscp-ipv6, exp, ieee-802.1, ieee-802.1ad, inet-precedence, inet6-precedence


482
rewrite-rules (Interfaces)
Syntax
rewrite-rules {
dscp (rewrite-name | default) protocol (inet-both | inet-outer | mpls);
dscp-ipv6 (rewrite-name | default) protocol mpls;
exp (rewrite-name | default) protocol protocol-types;
ieee-802.1ad (rewrite-name | default) vlan-tag (outer | outer-and-inner);
inet-precedence (rewrite-name | default) protocol (inet-both | inet-outer | mpls);
}
Hierarchy Level

Release Information
Description
Associate a rewrite-rules configuration or default mapping with a specific interface.
The [edit class-of-service interfaces interface-name] hierarchy level is not supported on M Series routers.
The [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level is not supported
on ACX Series routers.
Integrated Bridging and Routing (IRB) interfaces are used to tie together Layer 2 switched and Layer 3
routed domains on MX routers. MX routers support classifiers and rewrite rules on the IRB interface at
the [edit class-of-service interfaces irb unit logical-unit-number] level of the hierarchy. All types of
classifiers and rewrite rules are allowed, including IEEE 802.1p.
NOTE: The IRB classifiers and rewrite rules are used only for routed packets; in other words, it
is for traffic that originated in the Layer 2 domain and is then routed through IRB into the Layer
3 domain, or vice versa. Only IEEE classifiers and IEEE rewrite rules are allowed for pure Layer
2 interfaces within a bridge domain.
483
On an MX Series router and on an EX Series switch, exp-push-push-push, exp-swap-push-push, and

frame-relay-de are not supported on an integrated routing and bridging (IRB) interface.
On an ACX Series router, only the outer tag is supported for dscp, inet-precedence, and ieee802.1.
On M Series routers only, if you include the control-word statement at the [edit protocols l2circuit neighbor
address interface interface-name] hierarchy level, the software cannot rewrite MPLS EXP bits.
For IQ PICs, you can configure only one IEEE 802.1 rewrite rule on a physical port. All logical ports (units)
on that physical port should apply the same IEEE 802.1 rewrite rule.
On M320 and T Series routers (except for T4000 routers with Type 5 FPCs), for a single interface, you
cannot enable a rewrite rule on a subset of forwarding classes. You must assign a rewrite rule to either
none of the forwarding classes or all of the forwarding classes. When you assign a rewrite rule to a subset
of forwarding classes, the commit does not fail, and the subset of forwarding classes works as expected.
However, the forwarding classes to which the rewrite rule is not assigned are rewritten to all zeros.
For example, if you configure a Differentiated Services code point (DSCP) rewrite rule, the bits in the
forwarding classes to which you do not assign the rewrite rule are rewritten to 000000. If you configure
an IP precedence rewrite rule, the bits in the forwarding classes to which you do not assign the rewrite
rule are rewritten to 000.
Options
rewrite-name—Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules]
hierarchy level.
default—The default mapping.


484
routing-instances (Multiple Routing Entities)

Syntax
routing-instances routing-instance-name { ... }
Hierarchy Level
[edit],
[edit logical-systems logical-system-name]
Release Information
remote-vtep-v6-list statement introduced in Junos OS Release 17.3 for MX Series routers with MPC and
MIC interfaces.
Description
Configure an additional routing entity for a router. You can create multiple instances of BGP, IS-IS, OSPF,
OSPFv3, and RIP for a router. You can also create multiple routing instances for separating routing tables,
routing policies, and interfaces for individual wholesale subscribers (retailers) in a Layer 3 wholesale
network.
Each routing instance consist of the following:
• A set of routing tables
• A set of interfaces that belong to these routing tables
• A set of routing option configurations
Each routing instance has a unique name and a corresponding IP unicast table. For example, if you configure
a routing instance with the name my-instance, its corresponding IP unicast table is my-instance.inet.0. All
routes for my-instance are installed into my-instance.inet.0.
Routes are installed into the default routing instance inet.0 by default, unless a routing instance is specified.
In Junos OS Release 9.0 and later, you can no longer specify a routing-instance name of master, default,
or bgp or include special characters within the name of a routing instance.
In Junos OS Release 9.6 and later, you can include a slash (/) in a routing-instance name only if a logical
system is not configured. That is, you cannot include the slash character in a routing-instance name if a
logical system other than the default is explicitly configured. Routing-instance names, further, are restricted
from having the form __.*__ (beginning and ending with underscores). The colon : character cannot be
used when multitopology routing (MTR) is enabled.
Default
485
Routing instances are disabled for the router.
Options
routing-instance-name——Name of the routing instance. This must be a non-reserved string of not more
than 128 characters.
remote-vtep-list—Configure static remote VXLAN tunnel endpoints.
remote-vtep-v6-list—Configure static IPv6 remote VXLAN tunnel endpoints.

Example: Configuring Interprovider Layer 3 VPN Option A

Example: Configuring Interprovider Layer 3 VPN Option B
Example: Configuring Interprovider Layer 3 VPN Option C
486
scheduler (Scheduler Map)

Syntax
scheduler scheduler-name;
Hierarchy Level
[edit class-of-service scheduler-maps map-name]
Release Information
Description
Associate a scheduler with a scheduler map.
Options
scheduler-name—Name of the scheduler configuration block.

487
scheduler-map (Interfaces and Traffic-Control Profiles)

Syntax
Hierarchy Level

[edit class-of-service interfaces interface-name unit logical-unit-number],
Release Information
Description
For Gigabit Ethernet IQ, Channelized IQ PICs, and FRF.15 and FRF.16 LSQ interfaces only, associate a
scheduler map name with an interface or with a traffic-control profile.
For channelized OC12 intelligent queuing (IQ), channelized T3 IQ, channelized E1 IQ, and Gigabit Ethernet
IQ interfaces only, you can associate a scheduler map name with a logical interface.
Options
map-name—Name of the scheduler map.

488
scheduler-maps (For Most Interface Types)

Syntax
scheduler-maps {
map-name {
}
}
Hierarchy Level
Release Information
Description
Specify a scheduler map name and associate it with the scheduler configuration and forwarding class.
Options
map-name—Name of the scheduler map.
See Configuring Schedulers .

489
schedulers (CoS)
Syntax
schedulers {
scheduler-name {
adjust-percent percentage;
buffer-size (seconds | percent percentage | remainder | temporal microseconds);
drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any | non-tcp | tcp)
drop-profile profile-name;
excess-priority [ low | medium-low | medium-high | high | none];
excess-rate (percent percentage | proportion value);
shaping-rate (percent percentage | rate);
transmit-rate (percent percentage | rate | remainder) <exact | rate-limit>;
}
}
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.1X48 for PTX Series routers.
Description
Specify the scheduler name and parameter values.
Options
scheduler-name—Name of the scheduler to be configured.

490
How Schedulers Define Output Queue Properties

Configuring a Scheduler
491
secret (RADIUS)
Syntax
secret password;
Hierarchy Level
[edit access profile profile-name radius-server server-address],

[edit access radius-disconnect client-address],
[edit access radius-server server-address]
Release Information
Description
Configure the password to use with the RADIUS server. The secret password used by the local router or
switch must match that used by the server.
Options
password—Password to use; it can include spaces if the character string is enclosed in quotation marks.


RADIUS Authentication and Accounting Server Definition
Example: Configuring CHAP Authentication with RADIUS
Configuring RADIUS Authentication for L2TP
Configuring the RADIUS Disconnect Server for L2TP
492
server (Dynamic PPPoE)

Syntax
server;
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” pppoe-options]
Release Information
Description
In a dynamic profile, configure the router to act as a PPPoE server, also known as a remote access
concentrator, when a PPPoE logical interface is dynamically created.


Subscriber Interfaces and PPPoE Overview
493
server-group
Syntax
server-group {
server-group-name {
server-ip-address;
}
}
Hierarchy Level
[edit forwarding-options dhcp-relay],

[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay],
dhcpv6],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6]
Release Information
Description
Specify the name of a group of DHCP server addresses for use by the extended DHCP relay agent. Apply
the group with the active-server-group statement globally for all interfaces or for a named group of
interfaces configured with the group statement. This mechanism enables you to apply different DHCP
relay configurations for different groups of servers, with a common configuration for the servers within a
server group.
Options
server-group-name—Name of the group of DHCP or DHCPv6 server addresses.
server-ip-address—IP address of the DHCP server belonging to this named server group. Use IPv6 addresses
when configuring DHCPv6 support. Starting in Junos OS Release 18.4R1, you can configure up to 32
server IP addresses per group for DHCPv4 servers. In earlier releases, you can configure only up to 5
server IP addresses for DHCPv4 servers. For DHCPv6 servers, you can configure only up to 32
addresses in all releases. The configuration fails commit check if you configure more than the maximum
number of server addresses.
494

Extended DHCP Relay Agent Overview

Configuring Active Server Groups to Apply a Common DHCP Relay Agent Configuration to Named Server
Groups
495
shaping-rate (Applying to an Interface)

Syntax
shaping-rate rate;
Hierarchy Level

Release Information
[edit class-of-service interfaces interface-name] hierarchy level added in Junos OS Release 7.5.
Statement introduced in Junos OS Release 13.2 on PTX Series Packet Transport Routers.
Statement introduced in Junos OS Release 17.3 on PTX10008 Routers.
Description
For logical interfaces on which you configure packet scheduling, configure traffic shaping by specifying
the amount of bandwidth to be allocated to the logical interface. Applying a shaping rate can help ensure
that higher-priority services do not starve lower-priority services.
For physical interfaces, configure traffic shaping based on the rate-limited bandwidth of the total interface
bandwidth.
Logical and physical interface traffic shaping rates are mutually exclusive. This means you can include the
shaping-rate statement at the [edit class-of-service interfaces interface-name] hierarchy level or at the
[edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level, but not at both.
NOTE: For MX Series routers and for EX Series switches, the shaping rate value for the physical
interface at the [edit class-of-service interfaces interface-name] hierarchy level must be a minimum
of 160 Kbps. If the value is less than the sum of the logical interface guaranteed rates, you cannot
apply the shaping rate to a physical interface.
For PTX Series routers, the shaping rate value for the physical interface at the [edit
class-of-service interfaces interface-name] hierarchy level must be a minimum of 1 Gbps and an
incremental granularity of 0.1 percent of the physical interface speed after that (for example,
10 Mbps increments on a 10 Gbps interface).
For T4000 routers with Type 5 FPCs, the shaping rate value for the physical interface must be
a minimum of 292 Kbps. The maximum value of shaping-rate is limited by the maximum
transmission rate of the interface.
496
Alternatively, you can configure a shaping rate for a logical interface and oversubscribe the physical
interface by including the shaping-rate statement at the [edit class-of-service traffic-control-profiles]
hierarchy level. With this configuration approach, you can independently control the delay-buffer rate, as
described in Oversubscribing Interface Bandwidth.
For FRF.15 and FRF.16 bundles on link services interfaces, only shaping rates based on percentage are
supported.
Default
If you do not include this statement at the [edit class-of-service interfaces interface-name unit
logical-unit-number] hierarchy level, the default logical interface bandwidth is the average of unused
bandwidth for the number of logical interfaces that require default bandwidth treatment. If you do not
include this statement at the [edit class-of-service interfaces interface-name] hierarchy level, the default
physical interface bandwidth is the average of unused bandwidth for the number of physical interfaces
that require default bandwidth treatment.
Options
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000 bps.
NOTE: Through Junos OS Release 13.3, the upper limit is 160,000,000,000 bps. Beginning
with Junos OS Release 14.1, the upper limit is 6,400,000,000,000 bps.
NOTE: For all MX Series and EX Series interfaces, the rate can be from 65,535
to 6,400,000,000,000 bps.
For all PTX Series interfaces, the rate can be from 1,000,000,000 to 160,000,000,000 bps in
increments of 0.1 percent of the interface speed.

497
Applying Scheduler Maps Overview

Configuring Virtual LAN Queuing and Shaping on PTX Series Routers
498
shaping-rate (Schedulers)
Syntax
shaping-rate (percent percentage | rate) <burst-size bytes>;
Hierarchy Level
Release Information
The burst-size option added for MIC and MPC interfaces on MX Series routers in Junos OS Release 11.4.
Description
Define a limit on excess bandwidth usage for a forwarding class/queue.
The transmit-rate statement at the [edit class-of-service schedulers scheduler-name] hierarchy level
configures the minimum bandwidth allocated to a queue. The transmission bandwidth can be configured
as an exact value or allowed to exceed the configured rate if additional bandwidth is available from other
queues.
Configure the shaping rate as an absolute maximum usage and not the additional usage beyond the
configured transmit rate.
Default
If you do not include this statement, the default shaping rate is 100 percent, which is the same as no
shaping at all.
Options
percent percentage—Shaping rate as a percentage of the available interface bandwidth.
499
NOTE: If you configure a shaping rate as a percent in a scheduler, the effective shaping rate is
calculated based on the following hierarchy:
1. Logical interface shaping rate, if configured
2. Physical interface shaping rate, if configured
3. Physical interface bandwidth
With SRX300, SRX320, SRX340, SRX345, SRX550m, SRX1500, and vSRX2.0 devices, you can
configure both logical interface shaping rates and physical interface shaping rates on the same
physical interface. On all other models, you can only configure one or the other on a particular
physical interface.
g (1,000,000,000).
burst-size bytes—Maximum burst size, in bytes. The burst value determines the number of rate credits
that can accrue when the queue or scheduler node is held in the inactive round robin.
Range: 0 through 1,000,000,000

Applying Scheduler Maps Overview

500
shaping-rate (Oversubscribing an Interface)

Syntax
Hierarchy Level
Release Information
Option burst-size introduced for Enhanced Queuing (EQ) DPC interfaces on MX Series routers in Junos
OS Release 9.4.
Option burst-size option introduced for MIC and MPC interfaces on MX Series routers in Junos OS Release
11.4.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size configuration is
allowed on these interfaces, but does not take effect.
Option burst-size introduced for IQ2 and IQ2E interfaces in Junos OS Release 12.3.
Statement introduced for PTX Series Packet Transport Routers in Junos OS Release 16.1. PTX Series
Packet Transport Routers do not support the burst-size option or defining the shaping-rate as a percentage.
Description
For Gigabit Ethernet IQ, Channelized IQ PIC, FRF.15 and FRF.16 LSQ interfaces, and for EQ DPC, MIC,
and MPC interfaces on MX Series routers, configure a shaping rate for a logical interface. You can also
configure an optional burst size for a logical interface on EQ DPC interfaces and on IQ2 and IQ2E PIC
interfaces. This can help to ensure that higher-priority services do not starve lower-priority services.
For physical interfaces on T4000 router interfaces on Type 5 FPCs and on PTX Series routers, configure
traffic shaping rate.
The sum of the shaping rates for all logical interfaces on the physical interface can exceed the physical
interface bandwidth. This practice is known as oversubscription of the peak information rate (PIR).
Default
The default behavior depends on various factors. For more information, see Bandwidth and Delay Buffer
Allocations by Configuration Scenario.
Options
percent percentage—For LSQ interfaces, shaping rate as a percentage of the available interface bandwidth.
501
rate—For IQ and IQ2 interfaces, and T4000 routers with Type 5 FPCs, peak shaping rate, in bits per second
(bps). You can specify a value in bits per second either as a complete decimal number or as a decimal
number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000).
Range:
• IQ and IQ2 interfaces—1000 through 6,400,000,000,000 bps
• T4000 routers with Type 5 FPCs—The shaping rate value for the physical interface must be a minimum of
292 Kbps. The maximum value of shaping-rate is limited by the maximum transmission rate of the
interface.
burst-size bytes—(Optional) Maximum burst size, in bytes.



502
shaping-rate-excess-high
Syntax
Hierarchy Level
[edit class-of-service traffic-control-profiles profile-name],

Release Information
percent option added in Junos OS Release 19.3R1.
Description
For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
high-priority excess traffic. This can help to make sure higher priority services do not starve lower priority
services.
Default
If you do not include this statement, the default shaping rate for this priority is determined by the
shaping-rate statement in the traffic control profile.
Options
percent percentage—Specify the shaping rate as a percentage of the overall shaping rate.
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000
503
Default: None
burst-size bytes—Maximum burst size, in bytes.


Per-Priority Shaping on MIC and MPC Interfaces Overview

504
shaping-rate-excess-low
Syntax
Hierarchy Level

Release Information
Description
low-priority excess traffic. This can help to make sure higher priority services do not starve lower priority
services.
Default
Options
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000
505
Default: None



506
shaping-rate-priority-high
Syntax
Hierarchy Level

Release Information
Description
high priority traffic. This can help to make sure higher priority services do not starve lower priority services.
Default
Options
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000
Default: None
507



508
shaping-rate-priority-low
Syntax
Hierarchy Level

Release Information
Description
low priority traffic. This can help to make sure higher priority services do not starve lower priority services.
Default
Options
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000
Default: None
509



510
shaping-rate-priority-medium
Syntax
Hierarchy Level

Release Information
Description
medium priority traffic. This can help to make sure higher priority services do not starve lower priority
services.
Default
Options
g (1,000,000,000).
Range: 1000 through 6,400,000,000,000
511
Default: None



512
shared-bandwidth-policer (Configuring)
Syntax
shared-bandwidth-policer;
Hierarchy Level
[edit firewall policer policer-name],

[edit firewall three-color-policer policer-name],
[edit firewall hierarchical-policer policer-name]
Release Information
Support for MX Series MPC and MIC interfaces added in Junos OS Release 12.1.
Description
Policer instances share bandwidth. This enables configuration of interface-specific policers applied on an
aggregated Ethernet bundle or an aggregated SONET bundle to match the effective bandwidth and
burst-size to user-configured values. This feature is supported on the following platforms: T Series routers,
M120, M10i, M7i (CFEB-E only), M320 (SFPC only), MX240, MX480, and MX960 with DPC, MIC, and
MPC interfaces and EX Series switches.
NOTE: This statement is not supported on T4000 Type 5 FPCs.

Policer Support for Aggregated Ethernet Interfaces Overview

513
shared-instance
Syntax
shared-instance instance-name;
Hierarchy Level
[edit class-of-service interfaces interface-name unit logical-unit-number input-traffic-control-profile],

[edit class-of-service interfaces interface-name unit logical-unit-number output-traffic-control-profile]
Release Information
Description
For Gigabit Ethernet IQ2 and IQ2E PICs only, apply a shared traffic scheduling and shaping profile to the
logical interface.
Options
instance-name—Name of the shared scheduler and shaper to be applied to this interface

Configuring Shaping on 10-Gigabit Ethernet IQ2 PICs

514
shared-scheduler
Syntax
shared-scheduler;
Hierarchy Level
Release Information
Description
For Gigabit Ethernet IQ2 PICs only, enable shared schedulers and shapers on this interface. This statement
and the per-unit-scheduler statement are mutually exclusive. Even so, you can configure one logical
interface for each shared instance. This effectively provides the functionality of per-unit scheduling.
For Gigabit Ethernet IQ2 and Ethernet Enhanced IQ2 (IQ2E) PICs on M320 routers, enable shared schedulers
on aggregated Ethernet interfaces in link protection mode.


Configuring Shaping on 10-Gigabit Ethernet IQ2 PICs
Configuring Shared Scheduling on Aggregated Ethernet Interfaces
515
simple-filter (Applying to an Interface)

Syntax
simple-filter {
input filter-name;
}
Hierarchy Level
[edit interfaces interface-name unit logical-unit-number family inet],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family inet]
Release Information
Description
Apply a simple filter to an interface. You can apply simple filters to the family inet only, and only in the
input direction.
Options
input filter-name—Name of one filter to evaluate when packets are received on the interface.

Configuring Multifield Classifiers

filter (Applying to an Interface)
516
simple-filter
Syntax
simple-filter filter-name {
term term-name {
from {
match-conditions;
}
then {
loss-priority (high | low | medium);
}
}
}
Hierarchy Level
[edit firewall family inet],

[edit logical-systems logical-system-name firewall family inet]
Release Information
Description
Configure simple filters.
Options
filter-name—Name that identifies the simple filter. The name must be a non-reserved string of not more
than 64 characters. No special characters are restricted. To include spaces in the name, enclose them
in quotation marks (“ ”).
from—Match packet fields to values. If the from option is not included, all packets are considered to match
and the actions and action modifiers in the then statement are taken.
match-conditions—One or more conditions to use to make a match.
term term-name—Define a simple-filter term. The name that identifies the term can contain letters, numbers,
and hyphens (-), and can be up to 255 characters long. To include spaces in the name, enclose them
in quotation marks (“ ”).
517
then—Actions to take on matching packets. If the then option is not included and a packet matches all the
conditions in the from statement, the packet is accepted.
NOTE: Only forwarding-class and loss-priority are valid actions in a simple filter configuration.


Simple Filter Overview
How Simple Filters Evaluate Packets
Guidelines for Configuring Simple Filters
Guidelines for Applying Simple Filters
518
site-identifier (VPLS)
Syntax
site-identifier identifier;
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls site site-name],

[edit routing-instances routing-instance-name protocols vpls site site-name]
Release Information
Description
Specify the numerical identifier for the local VPLS site.
Options
identifier—Specify the numerical identifier for the local VPLS site. The identifier must be an unsigned 16-bit
number greater than zero.

Configuring the VPLS Site Name and Site Identifier

519
stacked-interface-set (Dynamic Profiles)

Syntax
stacked-interface-set {
interface-set-name interface-set-name {
interface-set-name interface-set-name;
}
}
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 18.4R1.
Description
For MX Series routers with MPCs that support 5-level hierarchical scheduling, define an interface set over
interface set hierarchy. The child interface set (L3) contains subscriber logical interfaces, and the parent
interface set (L2) contains one or more interface sets as members.
NOTE: For both interface-sets in the stack (at L3 and L2), a CoS traffic-control-profile (TCP)
must be assigned to each.
Options
interface-set-name—Name of the interface set to be configured or one of the following Junos OS predefined
variables:
• $junos-aggregation-interface-set-name—L2 interface-set representing a logical intermediate node (DPU-C

or PON tree) in the access network.
• $junos-default-interface-set-name—An intermediate, default variable used to resolve the L3 (child)

interface-set name based on whether subscriber access is via a logical intermediate aggregation node
• $junos-interface-set-name—Predefined variable that, when used, is replaced with the interface-set

obtained from the RADIUS server when a subscriber authenticates over the interface to which the
dynamic profile is attached.
• $junos-phy-ifd-underlying-intf-set-name—A default, topology-based interface-set derived from the

predefined variable, $junos-phy-ifd-underlying-intf-set-name by appending “-underlying” to conserve
520
L2 CoS nodes. It is a variation of the $junos-phy-ifd-interface-set-name variable used as a default L2

interface-set for 4-level hierarchy or default L3 interface-set for 5-level hierarchy.


interface-set (Dynamic Profiles)
521
stacked-vlan-tagging
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers.
Description
For Gigabit Ethernet IQ interfaces, Gigabit Ethernet, 10-Gigabit Ethernet LAN/WAN PIC, and 100-Gigabit
Ethernet Type 5 PIC with CFP, enable stacked VLAN tagging for all logical interfaces on the physical
interface.
For pseudowire subscriber interfaces, enable stacked VLAN tagging for logical interfaces on the pseudowire
service.

Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview

522
term (Simple Filter)

Syntax
term term-name {
from {
match-conditions;
}
then {
loss-priority (high | low | medium);
}
}
Hierarchy Level
[edit firewall family inet simple-filter filter-name]
Release Information
Description
Define a simple filter term.
Options
from—Match packet fields to values. If the from option is not included, all packets are considered to match
and the actions and action modifiers in the then statement are taken.
match-conditions—One or more conditions to use to make a match.
term-name—Name that identifies the term. The name can contain letters, numbers, and hyphens (-), and
can be up to 255 characters long. To include spaces in the name, enclose it in quotation marks (“ ”).
then—Actions to take on matching packets. If the then option is not included and a packet matches all the
conditions in the from statement, the packet is accepted. For CoS, only the actions listed are allowed.
These statements are explained separately.

523
Multifield Classification
Simple Filter Overview
Firewall Filter Match Conditions for IPv4 Traffic
Firewall Filter Match Conditions for IPv6 Traffic
524
three-color-policer (Applying)
Syntax
three-color-policer {
(single-rate | two-rate) policer-name;
}
Hierarchy Level
[edit firewall family family-name filter filter-name term term-name then]

[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-name then]
Release Information
single-rate statement added in Junos OS Release 8.2.
Description
Apply a tricolor marking policer.
Options
single-rate—Named tricolor policer is a single-rate policer.
two-rate—Named tricolor policer is a two-rate policer.
policer-name—Name of a tricolor policer.


Firewall Filter Nonterminating Actions
Three-Color Policer Configuration Overview
525
three-color-policer (Configuring)
Syntax
three-color-policer policer-name | uid {

action {
loss-priority high then discard;
}
filter-specific;
physical-interface-policer;
shared-bandwidth-policer;
single-rate {
excess-burst-size bytes;
}
two-rate {
peak-burst-size bytes;
peak-information-rate bps;
}
}
Hierarchy Level
[edit dynamic-profiles profile-name firewall],

[edit firewall],
[edit logical-systems logical-system-name firewall]
Release Information
The action and single-rate statements added in Junos OS Release 8.2.
Support at the [edit dynamic-profiles ... firewall] hierarchy level introduced in Junos OS Release 11.4.
Description
Configure a three-color policer in static firewall filters or dynamic firewall filters in a dynamic client profile
or a dynamic service profile.
Options
526
policer-name—Name of the three-color policer. Reference this name when you apply the policer to an
interface.
uid—When you configure a policer at the [edit dynamic-profiles] hierarchy level, you must assign a variable
UID as the policer name.


Three-Color Policer Configuration Guidelines
Basic Single-Rate Three-Color Policers
Basic Two-Rate Three-Color Policers
Two-Color and Three-Color Logical Interface Policers
Two-Color and Three-Color Physical Interface Policers
Two-Color and Three-Color Policers at Layer 2
527
traffic-control-profiles
Syntax
EX Series (Except EX4600), M Series, MX Series, PTX Series, T Series
atm-service (cbr | rtvbr | nrtvbr);
excess-rate (percent percentage | proportion value );
excess-rate-high (percent percentage | proportion value);
excess-rate-low (percent percentage | proportion value);
max-burst-size cells;
overhead-accounting (frame-mode | cell-mode | frame-mode-bytes | cell-mode-bytes) <bytes
(byte-value)>;
peak-rate rate;
shaping-rate-excess-medium-high (percent percentage | rate) <burst-size bytes>;
shaping-rate-excess-medium-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-medium-low (percent percentage | rate) <burst-size bytes>;
shaping-rate-priority-strict-high (percent percentage | rate) <burst-size bytes>;
strict-priority-scheduler;
sustained-rate rate;
}
QFX Series including QFabric, OCX OCX1100, EX4600, NFX Series
guaranteed-rate (rate| percent percentage);
shaping-rate (rate| percent percentage);
}
528
ACX Series
atm-service (cbr | nrtvbr | rtvbr);
delay-buffer-rate cps;
max-burst-size max-burst-size;
peak-rate peak-rate;
sustained-rate sustained-rate;
}
Hierarchy Level
Release Information
Statement was introduced in Junos OS Release 7.6 (EX series, M series, MX series, T series, and PTX series
devices).
Statement was introduced in Junos OS Release 11.1 for the QFX Series.
Statement was introduced in Junos OS Release 12.3 for ACX series routers.
Statement was introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description
ACX Series Routers
Configure traffic-shaping profiles.
NOTE: For CoS on ACX6360-OR, see the documentation for the PTX1000.
EX Series (Except EX4600), M Series, MX Series, T Series, and PTX Series Routers
For Gigabit Ethernet IQ, Channelized IQ PICs, FRF.15 and FRF.16 LSQ interfaces, Enhanced Queuing (EQ)
DPCs, and PTX Series routers only, configure traffic shaping and scheduling profiles. For Enhanced EQ
PICs, EQ DPCs, and PTX Series routers only, you can include the excess-rate statement.
QFX Series QFabric, OCX1100, EX4600, NFX Series
Configure traffic shaping and scheduling profiles for forwarding class sets (priority groups) to implement
enhanced transmission selection (ETS) or for logical interfaces.
529
Options
profile-name—Name of the traffic-control profile. This name is also used to specify an output traffic control
profile.
The remaining statements are explained separately. See CLI Explorer or click a linked statement in the
Syntax section for details.


Understanding Scheduling on PTX Series Routers
Example: Configuring CoS Hierarchical Port Scheduling (ETS)
Example: Configuring Traffic Control Profiles (Priority Group Scheduling)
Example: Configuring Forwarding Class Sets
Assigning CoS Components to Interfaces
Understanding CoS Traffic Control Profiles
530
traffic-manager
List of Syntax
Syntax (MX Series, PTX Series) Configure Queue Monitoring on page 530
Syntax (MX Series, T Series) on page 530
Syntax (M Series) on page 531
Syntax (QFX Series) on page 531
Syntax (vSRX) on page 532
Syntax (MX Series, PTX Series) Configure Queue Monitoring
traffic-manager {
ingress-shaping-overhead number;
mode {
egress-only;
ingress-and-egress;
session-shaping;
}
enhanced-priority-mode;
no-enhanced-priority-mode;
packet-timestamp {
enable;
}
queue-threshold {
fabric-queue {
priority high/low {
threshold threshold-percentage;
}
}
wan-queue {
priority high/medium-high/medium-low/low {
}
}
}
}
Syntax (MX Series, T Series)
traffic-manager {
mode {
531
egress-only;
ingress-and-egress;
}
}
Syntax (M Series)
traffic-manager {
mode {
egress-only;
ingress-and-egress;
session-shaping;
}
}
Syntax (QFX Series)
traffic-manager {
buffer-monitor-enable;
packet-timestamp {
enable;
}
queue-threshold {
fabric-queue {
priority high/low {
}
}
wan-queue {
priority high/medium-high/medium-low/low {
}
}
}
}
532
Syntax (vSRX)
traffic-manager {
}
Hierarchy Level
[edit chassis fpc slot-number],

[edit chassis fpc slot-number pic pic-number],
[edit chassis lcc number fpc slot-number pic pic-number] (Routing Matrix)
Release Information
Description
Enable CoS queuing, scheduling, and shaping on an L2TP session.
NOTE: Committing changes to traffic-manager automatically restarts any necessary components

(PICs, DPCs, or FPCs).
533
Options
buffer-monitor-enable—QFX5000 Series only. Enable port buffer monitoring. Buffer utilization data is
collected in one-second intervals and compared with the data from the previous interval. The larger value
is kept to keep track of peak buffer occupancy for each queue or priority group.
queue-threshold—Enable monitoring of Fabric and WAN queues. When the fabric-queue statement is
configured, an SNMP trap is generated whenever the fabric power utilization exceeds the configured
threshold value.
When wan-queue is configured, an SNMP trap is generated whenever the WAN queue depth exceeds
the configured threshold value.
egress-shaping-overhead number—When traffic management (queueing and scheduling) is configured on

the egress side, the number of CoS shaping overhead bytes to add to the packets on the egress interface.
Replace number with a value from -63 through 192 bytes.
For vSRX, replace number with a value from -62 through 192 bytes.
NOTE: The L2 headers (DA/SA + VLAN tags) are automatically a part of the shaping calculation.
ingress-shaping-overhead number—When L2TP session shaping is configured, the number of CoS shaping
overhead bytes to add to the packets on the ingress side of the L2TP tunnel to determine the shaped
session packet length.
When session shaping is not configured and traffic management (queueing and scheduling) is configured
on the ingress side, the number of CoS shaping overhead bytes to add to the packets on the ingress
interface.
Replace number with a value from —63 through 192 bytes.
mode—Configure CoS traffic manager mode of operation. This option has the following suboptions:
• egress-only—Enable CoS queuing and scheduling on the egress side for the PIC that houses the interface.
This is the default mode for an Enhanced Queueing (EQ) DPC on MX Series routers.
NOTE: If ingress packet drops are observed at a high rate for an IQ2 or IQ2E PIC, configure
the traffic-manager statement to work in the egress-only mode.
• ingress-and-egress—Enable CoS queueing and scheduling on both the egress and ingress sides for the
PIC. This is the default mode for IQ2 and IQ2E PICs on M Series and T Series routers.
534
NOTE:
• For EQ DPCs, you must configure the traffic-manager statement with ingress-and-egress
mode to enable ingress CoS on the EQ DPC.
• EQ DPCs have 250 ms of buffering, with only egress queueing (default mode). When
ingress-and-egress is configured, the buffer is partitioned as 50 ms for the ingress direction
and 200 ms for the egress direction.
• session-shaping—(M Series routers only) Configure the IQ2 PIC mode for session-aware traffic shaping
to enable L2TP session shaping.
enhanced-priority-mode—Enable the enhanced priority mode. When you enable the enhanced priority
mode, the scheduler supports four additional per-priority shaping rates and two additional excess priorities
at the interface and interface set level. The four additional per-priority shaping rates are: Guaranteed
Strict-high, Guaranteed Medium-low, Excess medium-high, and Excess medium-low. The two additional
excess priorities are: Excess-rate Medium- high and Excess-rate Medium-low. This is the default mode for
PTX Series routers.
no-enhanced-priority-mode—Disable the enhanced priority mode. This is the default mode for MX Series
routers.
NOTE: The line card reboots when you enable or disable the enhanced priority mode feature.


Enabling a Timestamp for Ingress and Egress Queue Packets
535
transmit-rate (Schedulers)
Syntax
transmit-rate (rate | percent percentage | remainder) <exact | rate-limit>;
Hierarchy Level
Release Information
rate-limit option introduced in Junos OS Release 8.3. Applied to the Multiservices PICs in Junos OS Release
9.4.
Statement introduced in Junos OS Release 12.1X48 for PTX Series routers.
Statement introduced in Junos OS Release 12.2 for ACX Series routers.
Description
Specify the transmit rate or percentage for a scheduler.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent, respectively.
Options
exact—(Optional) Enforce the exact transmission rate. Under sustained congestion, a rate-controlled queue
that goes into negative credit fills up and eventually drops packets. This value should never exceed the
rate-controlled amount. For PTX Series routers, this option is allowed only on the non-strict-high (high,
medium-high, medium-low, or low) queues.
percent percentage—Percentage of transmission capacity. A percentage of zero drops all packets in the
queue unless additional bandwidth is available from other queues.
Range: 0 through 100 percent for M, MX and T Series routers and EX Series switches; 1 through 100 percent
for PTX Series routers; 0 through 200 percent for the SONET/SDH OC48/STM16 IQE PIC
536
NOTE:
• On M Series Multiservice Edge Routers, for interfaces configured on 4-port E1 and 4-port T1
PICs only, you can configure a percentage value only from 11 through 100. These two PICs
do not support transmission rates less than 11 percent.
• The configuration of the transmit-rate percent 0 exact statement at the [edit class-of-service
schedules scheduler-name] hierarchy is ineffective on T4000 routers with Type 5 FPC.
• On MIC and MPC interfaces on MX Series routers, when the transmit rate is configured as a
percentage and exact or rate-limit is enabled on a queue, the shaping rate of the parent node
is used to compute the transmit rate. If exact or rate-limit is not configured, the guaranteed
rate of the parent node is used to compute the transmit rate.
• On PTX Series routers, unconfigured interfaces are equivalent to percent 0. This means the
system offers no guaranteed rate on the interface, and the queue will always be scheduled in
the excess priority.
rate—Transmission rate, in bps. You can specify a value in bits per second either as a complete decimal
number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000).
NOTE: For all MX Series interfaces, the rate can be from 65,535 through 6,400,000,000,000 bps.
rate-limit—(Optional) Limit the transmission rate to the rate-controlled amount by applying a policing
action to the queue. Packets are hard-dropped when traffic exceeds the specified maximum transmission
rate.
NOTE: For PTX Series routers, this option is allowed only on the strict-high queue. We
recommend that you configure rate limit on strict-high queues because the other queues may
not meet their guaranteed bandwidths. The rate-limit option cannot rate limit the queue if
strict-priority scheduling is configured with the strict-priority-scheduler statement.
NOTE: The configuration of the rate-limit statement is supported on T4000 routers only with
a Type 5 FPC.
remainder—Use the remaining rate available.

537

Configuring Scheduler Transmission Rate
Understanding Scheduling on PTX Series Routers
transparent
Syntax
transparent;
Hierarchy Level
[edit class-of-service interfaces interface-name unit logical-unit-number classifiers ieee802.1 vlan-tag]
Release Information
Statement introduced in Junos OS Release 11.2
Description
Packet classification based on the transparent VLAN tag.

538
underlying-interface (demux0)
Syntax
underlying-interface underlying-interface-name;
Hierarchy Level
[edit dynamic-profiles profile-name interfaces demux0 interface-name unit unit logical-unit-number demux-options]
Release Information
Support for aggregated Ethernet introduced in Junos OS Release 9.4.
Description
Configure the underlying interface on which the demultiplexing (demux) interface is running.
CAUTION: Before you make any changes to the underlying interface for a demux0
interface, you must ensure that no subscribers are currently present on that underlying
interface. If any subscribers are present, you must remove them before you make
changes.
Options
underlying-interface-name—Either the specific name of the interface on which the DHCP discover packet
arrives or one of the following interface variables:
• $junos-underlying-interface when configuring dynamic IP demux interfaces.
• $junos-interface-ifd-name when configuring dynamic VLAN demux interfaces.
The variable is used to specify the underlying interface when a new demux interface is dynamically created.
The variable is dynamically replaced with the underlying interface that DHCP supplies when the subscriber
logs in.
NOTE: Logical demux interfaces are currently supported on Gigabit Ethernet, Fast Ethernet,
10-Gigabit Ethernet, or aggregated Ethernet interfaces.

539

Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles
For information about static underlying interfaces, see the Junos OS Network Interfaces Library for Routing
Devices
540
underlying-interface (Dynamic PPPoE)

Syntax
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” pppoe-options]
Release Information
Description
In a dynamic profile, configure the underlying interface on which the router creates the dynamic PPPoE
logical interface.
Options
interface-name—Variable used to specify the name of the underlying interface on which the PPPoE logical
interface is dynamically created. In the underlying-interface interface-name statement for dynamic PPPoE
logical interfaces, you must use the predefined variable $junos-underlying-interface in place of
interface-name. When the router creates the dynamic PPPoE interface, the $junos-underlying-interface
predefined variable is dynamically replaced with the name of the underlying interface supplied by the
network when the subscriber logs in.


541
unit
Syntax
classifiers {
type (classifier-name | default) family (mpls | all);
}
fragmentation-map map-name;
per-session-scheduler;
rewrite-rules {
exp (rewrite-name | default)protocol protocol-types;
}
shaping-rate rate;
}
Hierarchy Level
Release Information
Description
Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device.
Options
logical-unit-number—Number of the logical unit.
Range: 0 through 16,384

542


543
unit (Dynamic Demux Interface)

Syntax
demux-options {
}
family family {
address address;
demux-source {
source-address;
}
direct-connect;
filter {
input filter-name;
output filter-name;
}
rpf-check {
mode loose;
}
}
filter {
input filter-name;
output filter-name;
}
}
vlan-id number;
Hierarchy Level
[edit dynamic-profiles profile-name interfaces demux0]
Release Information
544
Description
Configure a dynamic logical interface on the physical device. You must configure a logical interface to be
able to use the physical device.
Options
logical-unit-number—Either the specific unit number of the interface or the unit number variable
($junos-interface-unit). The variable is used to specify the unit of the interface when a new demux interface
is dynamically created. The static unit number variable is dynamically replaced with the unit number that
DHCP supplies when the subscriber logs in.


545
unit (Dynamic PPPoE)

Syntax
keepalives interval seconds;
no-keepalives;
pppoe-options {
server;
}
ppp-options {
mru size;
chap {
}
initiate-ncp (ip | ipv6 | dual-stack-passive)
mru size;
pap;
}
family inet {
address address;
service {
input {
}
}
output {
}
}
}
filter {
546
input filter-name {
}
}
}
}
filter {
input filter-name;
output filter-name;
}
}
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0]
Release Information
Description
In a dynamic profile, configure a logical unit number for the dynamic PPPoE logical interface. You must
configure a logical interface to be able to use the router.
Options
logical-unit-number—Variable used to specify the unit number when the PPPoE logical interface is
dynamically created. In the unit logical-unit-number statement for dynamic PPPoE logical interfaces, you
must use the predefined variable $junos-interface-unit in place of logical-unit-number. The
$junos-interface-unit predefined variable is dynamically replaced with the unit number supplied by the
router when the subscriber logs in.

547

unnumbered-address (Dynamic PPPoE)

Syntax
Hierarchy Level
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family inet]
Release Information
Description
For dynamic PPPoE interfaces, enable the local address to be derived from the specified interface.
Configuring unnumbered Ethernet interfaces enables IP processing on the interface without assigning an
explicit IP address to the interface.
Options
interface-name—Interface from which the local address is derived. The interface name must include a
logical unit number and must have a configured address.


548
unnumbered-address (Dynamic Profiles)

Syntax
Hierarchy Level
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family family],

[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family]
Release Information
Support for the $junos-preferred-source-address and $junos-preferred-source-ipv6-address predefined
variables introduced in Junos OS Release 9.6.
Support for the $junos-loopback-interface predefined variable introduced in Junos OS Release 9.6.
Description
For Ethernet interfaces, enable the local address to be derived from the specified interface. Configuring
unnumbered Ethernet interfaces enables IP processing on the interface without assigning an explicit IP
address to the interface. To configure unnumbered address dynamically, include the
$junos-loopback-interface-address predefined variable.
You can configure unnumbered address support on Ethernet interfaces for IPv4 and IPv6 address families.
Options
interface-name—Name of the interface from which the local address is derived. The specified interface
must have a logical unit number, a configured IP address, and must not be an unnumbered interface. This
value can be a specific interface name or the $junos-loopback-interface predefined variable.
When defining the unnumbered-address statement using a static interface, keep the following in mind:
• If you choose to include the routing-instance statement at the [edit dynamic-profiles] hierarchy level,
that statement must be configured with a dynamic value by using the $junos-routing-instance predefined
variable. In addition, whatever static unnumbered interface you specify must belong to that routing
instance; otherwise, the profile instantiation fails.
• If you choose to not include the routing-instance statement at the [edit dynamic-profiles] hierarchy
level, the unnumbered-address statement uses the default routing instance. The use of the default
routing instance requires that the unnumbered interface be configured statically and that it reside in the
default routing instance.
549
NOTE: When you specify a static logical interface for the unnumbered interface in a dynamic
profile that includes the $junos-routing-instance predefined variable, you must not configure a
preferred source address, whether with the $junos-preferred-source-address predefined variable,
the $junos-preferred-source-ipv6-address predefined variable, or the preferred-source-address
statement. Configuring the preferred source address in this circumstance causes a commit failure.
When defining the unnumbered-address statement using the $junos-loopback-interface predefined

variable, keep the following in mind:
• To use the $junos-loopback-interface predefined variable, the dynamic profile must also contain the
routing-instance statement configured with the $junos-routing-instance predefined variable at the [edit
dynamic-profiles] hierarchy level.
• The applied loopback interface is based on the dynamically obtained routing instance of the subscriber.
address—(Optional) Secondary IP address of the donor interface. Configuring the preferred source address
enables you to use an IP address other than the primary IP address on some of the unnumbered Ethernet
interfaces in your network. This value can be a static IP address, the $junos-preferred-source-address
predefined variable for the inet family, or the $junos-preferred-source-ipv6-address predefined variable
for the inet6 family.
When defining the preferred-source-address value using a static IP address, keep the following in mind:
• The unnumbered interface must be statically configured.
• The IP address specified as the preferred-source-address must be configured in the specified unnumbered
interface.
When defining the preferred-source-address value using the $junos-preferred-source-address or the

$junos-preferred-source-ipv6-address predefined variables, keep the following in mind:
• You must configure the unnumbered-address statement using the $junos-loopback-interface predefined
variable.
• You must configure the routing-instance statement using the $junos-routing-instance predefined variable
at the [edit dynamic-profiles] hierarchy level.
• The preferred source address chosen is based on the dynamically applied loopback address which is in
turn derived from the dynamically obtained routing instance of the subscriber. The configured loopback
address with the closest network match to the user IP address is selected as the preferred source address.

550
unnumbered-address (Ethernet)
Syntax
Hierarchy Level
[edit interfaces interface-name unit logical-unit-number family family],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family]
Release Information
preferred-source-address option introduced in Junos OS Release 9.0.
Description
For Ethernet interfaces, enable the local address to be derived from the specified interface. Configuring
an unnumbered Ethernet interface enables IP processing on the interface without assigning an explicit IP
address to the interface.
Options
interface-name—Name of the interface from which the local address is derived. The specified interface
must have a logical unit number and a configured IP address, and must not be an unnumbered interface.
The preferred-source-address statement is explained separately.

Configuring an Unnumbered Interface

address
Junos System Basics Configuration Guide
551
user-prefix (DHCP Relay Agent)

Syntax
Hierarchy Level
[edit forwarding-options dhcp-relay authentication username-include],

[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name authentication username-include],
[edit forwarding-options dhcp-relay group group-name authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 group group-name authentication
username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name authentication
username-include],
authentication username-include],
dhcpv6 authentication username-include],
dhcpv6 group group-name authentication username-include],
group group-name authentication username-include],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay authentication username-include],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay dhcpv6 group group-name authentication
username-include],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name authentication
username-include]
Release Information
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1.
Description
552
Specify the user prefix that is concatenated with the username during the subscriber authentication or
client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support.
Options
user-prefix-string—User prefix string.


553
vlan-id (Dynamic Profiles)

Syntax
vlan-id (number | none);
Hierarchy Level
Release Information
VLAN demux interface support introduced in Junos OS Release 10.2.
Description
For VLAN demux, Fast Ethernet, Gigabit Ethernet, and Aggregated Ethernet interfaces only, bind a 802.1Q
VLAN tag ID to a logical interface.
Options
number—A valid VLAN identifier. When used in the dynamic-profiles hierarchy, specify the $junos-vlan-id
predefined variable to dynamically obtain the VLAN identifier.
none—Enable the use of untagged pseudo-wire frames on dynamic interfaces.
• For aggregated Ethernet, 4-port, 8-port, and 12-port Fast Ethernet PICs, and for management and
internal Ethernet interfaces, 1 through 1023.
• For 48-port Fast Ethernet and Gigabit Ethernet PICs, 1 through 4094.
• VLAN ID 0 is reserved for tagging the priority of frames.

Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles
554
vlan-id (VLAN ID to Be Bound to a Logical Interface)

Syntax
vlan-id number;
Hierarchy Level

Release Information
Description
For Fast Ethernet, Gigabit Ethernet, and Aggregated Ethernet interfaces only, bind a 802.1Q VLAN tag ID
to a logical interface.
Options
number—A valid VLAN identifier.
Range: For aggregated Ethernet, 4-port, 8-port, and 12-port Fast Ethernet PICs, and for management and
internal Ethernet interfaces, 1 through 1023. In Junos OS Evolved vlan-id 0 is not supported.
For 48-port Fast Ethernet and Gigabit Ethernet PICs, 1 through 4094.
VLAN ID 0 is reserved for tagging the priority of frames used in Junos OS. In Junos OS Evolved vlan-id 0
is not supported.

Enabling VLAN Tagging

555
vlan-model
Syntax
vlan-model one-to-one;
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name],

[edit routing-instances routing-instance-name]
Release Information
Description
Define the network VLAN model.
Options
one-to-one—Specify that any received, dual-tagged VLAN packet triggers the provisioning process in a
Layer 2 Wholesale network. Using this option, the router learns VLAN tags for each individual client. The
router learns both the outer tag and inner tag of the incoming packets, when the instance-role statement
is defined as access, or the outer VLAN tag only, when the instance-role statement is defined as nni.

Configuring Separate Access Routing Instances for Layer 2 Wholesale Service Retailers
Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers
556
vlan-ranges
Syntax
vlan-ranges {
authentication {
username-include {
circuit-type;
circuit-id;
interface-name;
mac-address;
option-18;
option-37;
remote-id;
vlan-tags;
}
}
accept (any | dhcp-v4 | inet);
access-profilevlan-dynamic-profile-name;
}
override;
}
Hierarchy Level
[edit interfaces interface-name auto-configure]
Release Information
Description
Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
557

routing–control—To add this statement to the configuration.
Configuring Interfaces to Support Both Single and Stacked VLANs
558
vlan-tag
Syntax
vlan-tag (outer | outer-and-inner);
Hierarchy Level
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules ieee-802.1 (rewrite-name |

default)]
Release Information
Description
Apply this IEEE-802.1 rewrite rule to the outer VLAN tag or, if available, both outer and inner VLAN tags.
Default
If you do not include this statement, the rewrite rule applies to the outer VLAN tag only.
Options
outer—Apply the rewrite rule to the outer VLAN tag only.
outer-and-inner—Apply the rewrite rule to both the outer and inner VLAN tags.

Applying IEEE 802.1p Rewrite Rules to Dual VLAN Tags

559
vlan-tags
Syntax
Hierarchy Level
Release Information
VLAN demux interface support introduced in Junos OS Release 10.2.
Description
For Gigabit Ethernet IQ and IQE interfaces only, binds TPIDs and 802.1Q VLAN tag IDs to a logical interface.
You must include the stacked-vlan-tagging statement at the [edit interfaces interface-name] hierarchy
level.
NOTE: The inner-range vid1–vid2 option is supported on IQE PICs only.
Options
inner [tpid].vlan-id—A TPID (optional) and a valid VLAN identifier in the format tpid.vlan-id. When used in
the dynamic-profiles hierarchy, specify the $junos-vlan-id predefined variable to dynamically obtain the
VLAN ID.
NOTE: On the network-to-network (NNI) or egress interfaces of provider edge (PE) routers, you
cannot configure the inner-range tpid. vid1—vid2 option with the vlan-tags statement for
ISP-facing interfaces.
Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
outer [tpid].vlan-id—A TPID (optional) and a valid VLAN identifier in the format tpid.vlan-id. When used in
the dynamic-profiles hierarchy, specify the $junos-stacked-vlan-id predefined variable.
Range: For VLAN ID, 1 through 511 for normal interfaces, and 512 through 4094 for VLAN CCC interfaces.
VLAN ID 0 is reserved for tagging the priority of frames.

560

Configuring Dual VLAN Tags
vlan-tags-outer
Syntax
vlan-tags-outer vlan-tag;
Hierarchy Level
[edit interfaces interface-set interface-set-name interface interface-name]
Release Information
Description
The S-VLAN outer tag that belongs to a set of interfaces used to configure hierarchical CoS schedulers.

Class of Service User Guide (Routers and EX9200 Switches)

561
vlan-tags (Stacked VLAN Tags)

Syntax
vlan-tags inner tpid.vlan-id inner-list value inner-range vid1—vid2 outer tpid.vlan-id;
Hierarchy Level

Release Information
Description
Bind TPIDs and 802.1Q VLAN tag IDs to a logical interface. TPID fields are used to identify the frame as
an IEEE 802.1Q-tagged frame.
Options
inner tpid.vlan-id—A TPID and a valid VLAN identifier. TPID is a 16-bit field set to a value of 0x8100 in
order to identify the frame as an IEEE 802.1Q-tagged frame.
Range: (most routers) For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
For PTX Series, VLAN ID 0 is not supported.
inner-list value— List or a set of VLAN identifiers.
NOTE: This is supported on MX Series routers with Trio-based FPCs.
inner-range tpid. vid1–vid2—Specify a TPID and a range of VLAN IDs where vid1 is the start of the range
and vid2 is the end of the range.
NOTE: On the network-to-network (NNI) or egress interfaces of provider edge (PE) routers, you
cannot configure the inner-range tpid. vid1—vid2 option with the vlan-tags statement for
ISP-facing interfaces.
Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
outer tpid.vlan-id—A TPID and a valid VLAN identifier.

562
Range: (most routers) For VLAN ID, 1 through 511 for normal interfaces, and 512 through 4094 for VLAN
CCC interfaces. VLAN ID 0 is reserved for tagging the priority of frames. For PTX Series, VLAN ID 0 is not
supported.
NOTE: Configuring inner-range with the entire vlan-id range consumes system resources and
is not a best practice. The inner-range must be used only when a subset of VLAN IDs of inner
tag (not the entire range) needs to be associated with a logical interface. If you specify the entire
range (1 through 4094), it has the same result as not specifying a range; however, it consumes
Packet Forwarding Engine resources such as VLAN lookup table entries, and so on.
The following examples illustrate this further:

unit number {
vlan-tags outer vid inner-range 1-4094;
}

vlan-tagging;
unit number {
vlan-id vid;
}

Configuring Dual VLAN Tags

Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers
563
CHAPTER 11
Operational Commands
IN THIS CHAPTER
show class-of-service adjustment-control-profile | 567
show class-of-service classifier | 569
show class-of-service interface | 572
show class-of-service scheduler-map | 612
show class-of-service scheduler-hierarchy interface | 616
show class-of-service scheduler-hierarchy interface-set | 619
show interfaces | 621
show interfaces (PPPoE) | 728
show interfaces demux0 (Demux Interfaces) | 741
show subscribers | 816

564
show access-cac interface-set

Syntax

<interface-set-name | detail>
Release Information
Command introduced in Junos OS Release 17.2 for the MX Series.
Description
Display interface-set adjustment information.
Options
none—List all interface-set entries with the total aggregate adjustment value for each interface-set.
interface-set-name—Restrict the output to a specific interface-set.
detail—List all multicast groups, with adjustment rates, that provide an update on the specified interface-set.

view
List of Sample Output

show access-cac interface-set on page 565
show access-cac interface-set (detail) on page 565
Output Fields
Table 31 on page 564 describes the output fields for the show show access-cac interface-set command.
Output fields are listed in the approximate order in which they appear.
Table 31: show class-of-service interface-set Output Fields
Field Name Field Description
Access cac Then name of the interface set.

interface-set
565
Table 31: show class-of-service interface-set Output Fields (continued)
Total current The total current adjustment on the interface set, in bps, equal to the sum of the measured
adjustment on rates on all configured multicast channels.
interface-set
Mcast channels The list of all configured multicast channels.
Configured rate The shaping rate configured for each multicast channel.
Measured rate The current data rate for each multicast channel. This rate for a multicast channel adjusts the
shaping rate of the interface set by an equal amount.
Sample Output
user@host> show access-cac interface-set
Access cac interface-sets

Access cac interface-set: ge-5/0/0-1
show access-cac interface-set (detail)

user@host> show access-cac interface-set detail
Access cac interface-sets

Total current adjustment on interface-set: 4080908
Mcast channels:
0.0.0.0 , 225.0.0.1 Configured rate: 4000000 Measured rate: 560268
:: , ff8e::e100:1 Configured rate: 4000000 Measured rate: 2400080

Total current adjustment on interface-set: 500222379
Mcast channels:
566

:: , ff8e::e100:1 Configured rate: 4000000 Measured rate: 0
567
show class-of-service adjustment-control-profile

Syntax

<profile-name>
Release Information
Command introduced in Junos OS Release 13.1 for MX Series Routers.
Description
For MPC/MIC interfaces only, display the adjustment control profiles.
Options
none—Display all profiles.
profile-name—(Optional) Display information about a single profile.

view
Verifying the CoS Adjustment Control Profile Configuration

show class-of-service adjustment-control-profile on page 568
Output Fields
Table 32 on page 567 describes the output fields for the show class-of-service adjustment-control-profile
command. Output fields are listed in the approximate order in which they appear.
Table 32: show class-of-service adjustment-control-profile Output Fields
Name Name of the adjusting application. Possible values:
• RADIUS-CoA—RADIUS CoA application.

• ANCP—ANCP application.
• PPPoE IA tags—PPPoE IA tag application.
• DHCP tags—DHCP application.
568
Table 32: show class-of-service adjustment-control-profile Output Fields (continued)
Priority Priority of the adjusting application. Possible values are 1 through 10; 1 is the highest priority.
The lower the priority value, the higher the priority
Algorithm Algorithm the adjusting application uses to make adjustments.
• adjust-never—Never perform rate adjustments.

• adjust-always—Adjust the shaping rate unconditionally.
• adjust-less—Adjust the shaping rate if it is less than the configured value.
• adjust-less-or equal—Adjust the shaping rate if it is less than or equal to the configured value.
• adjust-greater—Adjust the shaping rate if it is greater than the configured value.
• adjust-greater-or-equal—Adjust the shaping rate if it is greater than or equal to the configured
value.
Sample Output
user@host> show class-of-service adjustment-control-profile
user@host> show class-of-service adjustment-control-profile acp1

name: ANCP, priority: 1, algorithm: less
name: RADIUS CoA, priority: 1, algorithm: always
name: PPPoE IA tags, priority: 2, algorithm: less
name: DHCP tags, priority: 2, algorithm: less
569
show class-of-service classifier

Syntax
show class-of-service classifier

<name name>
<type dscp | type dscp-ipv6 | type exp | type ieee-802.1 | type inet-precedence>
Release Information
Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description
For each class-of-service (CoS) classifier, display the mapping of code point value to forwarding class and
loss priority.
Options
none—Display all classifiers.
name name—(Optional) Display named classifier.
type dscp—(Optional) Display all classifiers of the Differentiated Services code point (DSCP) type.
type dscp-ipv6—(Optional) Display all classifiers of the DSCP for IPv6 type.
type exp—(Optional) Display all classifiers of the MPLS experimental (EXP) type.
type ieee-802.1—(Optional) Display all classifiers of the ieee-802.1 type.
type inet-precedence—(Optional) Display all classifiers of the inet-precedence type.

view

show class-of-service classifier type ieee-802.1 on page 570
show class-of-service classifier type ieee-802.1 (QFX Series) on page 571
Output Fields
Table 33 on page 570 describes the output fields for the show class-of-service classifier command. Output
fields are listed in the approximate order in which they appear.
570
Table 33: show class-of-service classifier Output Fields
Classifier Name of the classifier.
Code point type Type of the classifier: exp (not on EX Series switch), dscp, dscp-ipv6 (not on EX
Series switch), ieee-802.1, or inet-precedence.
Index Internal index of the classifier.
Code point Code point value used for classification
Forwarding class Classification of a packet affecting the forwarding, scheduling, and marking
policies applied as the packet transits the router.
Loss priority Loss priority value used for classification. For most platforms, the value is high
or low. For some platforms, the value is high, medium-high, medium-low, or
low.
Sample Output
show class-of-service classifier type ieee-802.1
user@host> show class-of-service classifier type ieee-802.1
Classifier: ieee802.1-default, Code point type: ieee-802.1, Index: 3

Code Point Forwarding Class Loss priority
000 best-effort low
001 best-effort high
010 expedited-forwarding low
011 expedited-forwarding high
100 assured-forwarding low
101 assured-forwarding medium-high
110 network-control low
111 network-control high
Classifier: users-ieee802.1, Code point type: ieee-802.1

Code point Forwarding class Loss priority
100 expedited-forwarding low
571
show class-of-service classifier type ieee-802.1 (QFX Series)

user@switch> show class-of-service classifier type ieee-802.1
Classifier: ieee8021p-default, Code point type: ieee-802.1, Index: 11

000 best-effort low
001 best-effort low
010 best-effort low
011 fcoe low
100 no-loss low
101 best-effort low
Classifier: ieee8021p-untrust, Code point type: ieee-802.1, Index: 16

000 best-effort low
001 best-effort low
010 best-effort low
011 best-effort low
100 best-effort low
101 best-effort low
110 best-effort low
111 best-effort low
Classifier: ieee-mcast, Code point type: ieee-802.1, Index: 46

000 mcast low
001 mcast low
010 mcast low
011 mcast low
100 mcast low
101 mcast low
110 mcast low
111 mcast low
572
show class-of-service interface

Syntax
show class-of-service interface

<comprehensive | detail> <interface-name>
Release Information
Forwarding class map information added in Junos OS Release 9.4.
Command introduced in Junos OS Release 12.1 for the PTX Series Packet Transport routers.
Command introduced in Junos OS Release 12.2 for the ACX Series Universal Metro routers.
Options detail and comprehensive introduced in Junos OS Release 11.4.
Command introduced in Junos OS Release 15.1R3 on MX Series routers for enhanced subscriber
management.
Description
Display the logical and physical interface associations for the classifier, rewrite rules, and scheduler map
objects.
NOTE: On routing platforms with dual Routing Engines, running this command on the backup
Routing Engine, with or without any of the available options, is not supported and produces the
following error message:
error: the class-of-service subsystem is not running
Options
none—Display CoS associations for all physical and logical interfaces.
comprehensive—(M Series, MX Series, and T Series routers) (Optional) Display comprehensive

quality-of-service (QoS) information about all physical and logical interfaces.
detail—(M Series, MX Series, and T Series routers) (Optional) Display QoS and CoS information based on
the interface.
If the interface interface-name is a physical interface, the output includes:

573
• Brief QoS information about the physical interface
• Brief QoS information about the logical interface
• CoS information about the physical interface
• Brief information about filters or policers of the logical interface
• Brief CoS information about the logical interface
If the interface interface-name is a logical interface, the output includes:
• Brief QoS information about the logical interface
• Information about filters or policers for the logical interface
• CoS information about the logical interface
interface-name—(Optional) Display class-of-service (CoS) associations for the specified interface.
none—Display CoS associations for all physical and logical interfaces.
NOTE: ACX5000 routers do not support classification on logical interfaces and therefore do
not show CoS associations for logical interfaces with this command.

view
Verifying and Managing Junos OS Enhanced Subscriber Management

show class-of-service interface (Physical) on page 589
show class-of-service interface (Logical) on page 589
show class-of-service interface (Gigabit Ethernet) on page 589
show class-of-service interface (ANCP) on page 590
show class-of-service interface (PPPoE Interface) on page 590
show class-of-service interface (DHCP Interface) on page 590
show class-of-service interface (T4000 Routers with Type 5 FPCs) on page 591
show class-of-service interface detail on page 591
show class-of-service interface comprehensive on page 592
show class-of-service interface (ACX Series Routers) on page 607
574
show class-of-service interface (PPPoE Subscriber Interface for Enhanced Subscriber

Management) on page 610
Output Fields
Table 34 on page 574 describes the output fields for the show class-of-service interface command. Output
fields are listed in the approximate order in which they appear.
Table 34: show class-of-service interface Output Fields
Physical interface Name of a physical interface.
Index Index of this interface or the internal index of this object.
(Enhanced subscriber management for MX Series routers) Index values for dynamic CoS traffic
control profiles and dynamic scheduler maps are larger for enhanced subscriber management
than they are for legacy subscriber management.
Dedicated Queues Status of dedicated queues configured on an interface. Supported only on Trio MPC/MIC
interfaces on MX Series routers.
(Enhanced subscriber management for MX-Series routers) This field is not displayed for
enhanced subscriber management.
Maximum usable Number of queues you can configure on the interface.

queues
Maximum usable Maximum number of queues you can use.

queues
Total non-default Number of queues created in addition to the default queues. Supported only on Trio MPC/MIC
queues created interfaces on MX Series routers.
(Enhanced subscriber management for MX Series routers) This field is not displayed for
enhanced subscriber management.
Rewrite Input IEEE (QFX3500 switches only) IEEE 802.1p code point (priority) rewrite value. Incoming traffic from
Code-point the Fibre Channel (FC) SAN is classified into the forwarding class specified in the native FC
interface (NP_Port) fixed classifier and uses the priority specified as the IEEE 802.1p rewrite
value.
Shaping rate Maximum transmission rate on the physical interface. You can configure the shaping rate on
the physical interface, or on the logical interface, but not on both. Therefore, the Shaping rate
field is displayed for either the physical interface or the logical interface.
575
Table 34: show class-of-service interface Output Fields (continued)
Scheduler map Name of the output scheduler map associated with this interface.
(Enhanced subscriber management for MX Series routers) The name of the dynamic scheduler
map object is associated with a generated UID (for example, SMAP-1_UID1002) instead of
with a subscriber interface.
Scheduler map (QFX Series only) Name of the output fabric scheduler map associated with a QFabric system
forwarding class sets Interconnect device interface.
Input shaping rate For Gigabit Ethernet IQ2 PICs, maximum transmission rate on the input interface.
Input scheduler map For Gigabit Ethernet IQ2 PICs, name of the input scheduler map associated with this interface.
Chassis scheduler Name of the scheduler map associated with the packet forwarding component queues.
map
Rewrite Name and type of the rewrite rules associated with this interface.
Traffic-control-profile Name of the associated traffic control profile.
(Enhanced subscriber management for MX Series routers) The name of the dynamic traffic
control profile object is associated with a generated UID (for example,
TC_PROF_100_199_SERIES_UID1006) instead of with a subscriber interface.
Classifier Name and type of classifiers associated with this interface.
Forwarding-class-map Name of the forwarding map associated with this interface.
Congestion-notification (QFX Series and EX4600 switches only) Congestion notification state, enabled or disabled.
Logical interface Name of a logical interface.
Object Category of an object: Classifier, Fragmentation-map (for LSQ interfaces only), Scheduler-map,
Rewrite, Translation Table (for IQE PICs only), or traffic-class-map (for T4000 routers with
Type 5 FPCs).
Name Name of an object.
Type Type of an object: dscp, dscp-ipv6, exp, ieee-802.1, ip, inet-precedence, or ieee-802.1ad (for
traffic class map on T4000 routers with Type 5 FPCs)..
Link-level type Encapsulation on the physical interface.

576
MTU MTU size on the physical interface.
Speed Speed at which the interface is running.
Loopback Whether loopback is enabled and the type of loopback.
Source filtering Whether source filtering is enabled or disabled.
Flow control Whether flow control is enabled or disabled.
Auto-negotiation (Gigabit Ethernet interfaces) Whether autonegotiation is enabled or disabled.
Remote-fault (Gigabit Ethernet interfaces) Remote fault status.
• Online—Autonegotiation is manually configured as online.

• Offline—Autonegotiation is manually configured as offline.
Device flags The Device flags field provides information about the physical device and displays one or
more of the following values:
• Down—Device has been administratively disabled.

• Hear-Own-Xmit—Device receives its own transmissions.
• Link-Layer-Down—The link-layer protocol has failed to connect with the remote endpoint.
• Loopback—Device is in physical loopback.
• Loop-Detected—The link layer has received frames that it sent, thereby detecting a physical
loopback.
• No-Carrier—On media that support carrier recognition, no carrier is currently detected.
• No-Multicast—Device does not support multicast traffic.
• Present—Device is physically present and recognized.
• Promiscuous—Device is in promiscuous mode and recognizes frames addressed to all physical
addresses on the media.
• Quench—Transmission on the device is quenched because the output buffer is overflowing.
• Recv-All-Multicasts—Device is in multicast promiscuous mode and therefore provides no
multicast filtering.
• Running—Device is active and enabled.
577
Interface flags The Interface flags field provides information about the physical interface and displays one
or more of the following values:
• Admin-Test—Interface is in test mode and some sanity checking, such as loop detection, is
disabled.
• Disabled—Interface is administratively disabled.
• Down—A hardware failure has occurred.
• Hardware-Down—Interface is nonfunctional or incorrectly connected.
• Link-Layer-Down—Interface keepalives have indicated that the link is incomplete.
• No-Multicast—Interface does not support multicast traffic.
• No-receive No-transmit—Passive monitor mode is configured on the interface.
• Point-To-Point—Interface is point-to-point.
• Pop all MPLS labels from packets of depth—MPLS labels are removed as packets arrive on
an interface that has the pop-all-labels statement configured. The depth value can be one
of the following:
• 1—Takes effect for incoming packets with one label only.
• 2—Takes effect for incoming packets with two labels only.
• [ 1 2 ]—Takes effect for incoming packets with either one or two labels.
• Promiscuous—Interface is in promiscuous mode and recognizes frames addressed to all
physical addresses.
• Recv-All-Multicasts—Interface is in multicast promiscuous mode and provides no multicast
filtering.
• SNMP-Traps—SNMP trap notifications are enabled.
• Up—Interface is enabled and operational.
578
Flags The Logical interface flags field provides information about the logical interface and displays
one or more of the following values:
• ACFC Encapsulation—Address control field Compression (ACFC) encapsulation is enabled

(negotiated successfully with a peer).
• Device-down—Device has been administratively disabled.
• Disabled—Interface is administratively disabled.
• Down—A hardware failure has occurred.
• Clear-DF-Bit—GRE tunnel or IPsec tunnel is configured to clear the Don't Fragment (DF)
bit.
• Hardware-Down—Interface protocol initialization failed to complete successfully.
• PFC—Protocol field compression is enabled for the PPP session.
• Point-To-Point—Interface is point-to-point.
• SNMP-Traps—SNMP trap notifications are enabled.
• Up—Interface is enabled and operational.
Encapsulation Encapsulation on the logical interface.
Admin Administrative state of the interface (Up or Down)
Link Status of physical link (Up or Down).
Proto Protocol configured on the interface.
Input Filter Names of any firewall filters to be evaluated when packets are received on the interface,
including any filters attached through activation of dynamic service.
Output Filter Names of any firewall filters to be evaluated when packets are transmitted on the interface,
including any filters attached through activation of dynamic service.
579
Link flags Provides information about the physical link and displays one or more of the following values:
• ACFC—Address control field compression is configured. The Point-to-Point Protocol (PPP)

session negotiates the ACFC option.
• Give-Up—Link protocol does not continue connection attempts after repeated failures.
• Loose-LCP—PPP does not use the Link Control Protocol (LCP) to indicate whether the link
protocol is operational.
• Loose-LMI—Frame Relay does not use the Local Management Interface (LMI) to indicate
whether the link protocol is operational.
• Loose-NCP—PPP does not use the Network Control Protocol (NCP) to indicate whether
the device is operational.
• Keepalives—Link protocol keepalives are enabled.
• No-Keepalives—Link protocol keepalives are disabled.
• PFC—Protocol field compression is configured. The PPP session negotiates the PFC option.
Hold-times Current interface hold-time up and hold-time down, in milliseconds.
CoS queues Number of CoS queues configured.
Last flapped Date, time, and how long ago the interface went from down to up. The format is Last flapped:
year-month-day hour:minute:second:timezone (hour:minute:second ago). For example, Last
flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last cleared Number and rate of bytes and packets received and transmitted on the physical interface.
• Input bytes—Number of bytes received on the interface.

• Output bytes—Number of bytes transmitted on the interface.
• Input packets—Number of packets received on the interface.
• Output packets—Number of packets transmitted on the interface.
Exclude Overhead Exclude the counting of overhead bytes from aggregate queue statistics.
Bytes
• Disabled—Default configuration. Includes the counting of overhead bytes in aggregate
queue statistics.
• Enabled—Excludes the counting of overhead bytes from aggregate queue statistics for just
the physical interface.
• Enabled for hierarchy—Excludes the counting of overhead bytes from aggregate queue
statistics for the physical interface as well as all child interfaces, including logical interfaces
and interface sets.
IPv6 transit statistics Number of IPv6 transit bytes and packets received and transmitted on the logical interface if
IPv6 statistics tracking is enabled.
580
Input errors Input errors on the interface. The labels are explained in the following list:
• Errors—Sum of the incoming frame aborts and FCS errors.

• Drops—Number of packets dropped by the input queue of the I/O Manager ASIC. If the
interface is saturated, this number increments once for every packet that is dropped by the
ASIC's RED mechanism.
• Framing errors—Number of packets received with an invalid frame checksum (FCS).
• Runts—Number of frames received that are smaller than the runt threshold.
• Giants—Number of frames received that are larger than the giant threshold.
• Bucket Drops—Drops resulting from the traffic load exceeding the interface transmit or
receive leaky bucket configuration.
• Policed discards—Number of frames that the incoming packet match code discarded because
they were not recognized or not of interest. Usually, this field reports protocols that Junos
OS does not handle.
• L3 incompletes—Number of incoming packets discarded because they failed Layer 3 (usually
IPv4) sanity checks of the header. For example, a frame with less than 20 bytes of available
IP header is discarded. Layer 3 incomplete errors can be ignored by configuring the
ignore-l3-incompletes statement.
• L2 channel errors—Number of times the software did not find a valid logical interface for
an incoming frame.
• L2 mismatch timeouts—Number of malformed or short packets that caused the incoming
packet handler to discard the frame as unreadable.
• HS link CRC errors—Number of errors on the high-speed links between the ASICs responsible
for handling the router interfaces.
• HS link FIFO overflows—Number of FIFO overflows on the high-speed links between the
ASICs responsible for handling the router interfaces.
581
Output errors Output errors on the interface. The labels are explained in the following list:
• Carrier transitions—Number of times the interface has gone from down to up. This number
does not normally increment quickly, increasing only when the cable is unplugged, the
far-end system is powered down and up, or another problem occurs. If the number of carrier
transitions increments quickly (perhaps once every 10 seconds), the cable, the far-end
system, or the PIC is malfunctioning.
• Errors—Sum of the outgoing frame aborts and FCS errors.
• Drops—Number of packets dropped by the output queue of the I/O Manager ASIC. If the
interface is saturated, this number increments once for every packet that is dropped by the
ASIC's RED mechanism.
NOTE: Due to accounting space limitations on certain Type 3 FPCs (which are supported
in M320 and T640 routers), the Drops field does not always use the correct value for queue 6
or queue 7 for interfaces on 10-port 1-Gigabit Ethernet PICs.
• Aged packets—Number of packets that remained in shared packet SDRAM so long that the
system automatically purged them. The value in this field should never increment. If it does,
it is most likely a software bug or possibly malfunctioning hardware.
• HS link FIFO underflows—Number of FIFO underflows on the high-speed links between
the ASICs responsible for handling the router interfaces.
• MTU errors—Number of packets whose size exceeds the MTU of the interface.
Egress queues Total number of egress Maximum usable queues on the specified interface.
Queue counters CoS queue number and its associated user-configured forwarding class name.
• Queued packets—Number of queued packets.

• Transmitted packets—Number of transmitted packets.
• Dropped packets—Number of packets dropped by the ASIC's RED mechanism.
NOTE: Due to accounting space limitations on certain Type 3 FPCs (which are supported
in M320 and T640 routers), the Dropped packets field does not always display the correct
value for queue 6 or queue 7 for interfaces on 10-port 1-Gigabit Ethernet PICs.
SONET alarms (SONET) SONET media-specific alarms and defects that prevent the interface from passing
packets. When a defect persists for a certain period, it is promoted to an alarm. Based on the
SONET defects
router configuration, an alarm can ring the red or yellow alarm bell on the router or light the
red or yellow alarm LED on the craft interface. See these fields for possible alarms and defects:
SONET PHY, SONET section, SONET line, and SONET path.
582
SONET PHY Counts of specific SONET errors with detailed information.
• Seconds—Number of seconds the defect has been active.

• Count—Number of times that the defect has gone from inactive to active.
• State—State of the error. A state other than OK indicates a problem.
The SONET PHY field has the following subfields:
• PLL Lock—Phase-locked loop

• PHY Light—Loss of optical signal
SONET section Counts of specific SONET errors with detailed information.

The SONET section field has the following subfields:
• BIP-B1—Bit interleaved parity for SONET section overhead

• SEF—Severely errored framing
• LOS—Loss of signal
• LOF—Loss of frame
• ES-S—Errored seconds (section)
• SES-S—Severely errored seconds (section)
• SEFS-S—Severely errored framing seconds (section)
583
SONET line Active alarms and defects, plus counts of specific SONET errors with detailed information.

The SONET line field has the following subfields:
• BIP-B2—Bit interleaved parity for SONET line overhead

• REI-L—Remote error indication (near-end line)
• RDI-L—Remote defect indication (near-end line)
• AIS-L—Alarm indication signal (near-end line)
• BERR-SF—Bit error rate fault (signal failure)
• BERR-SD—Bit error rate defect (signal degradation)
• ES-L—Errored seconds (near-end line)
• SES-L—Severely errored seconds (near-end line)
• UAS-L—Unavailable seconds (near-end line)
• ES-LFE—Errored seconds (far-end line)
• SES-LFE—Severely errored seconds (far-end line)
• UAS-LFE—Unavailable seconds (far-end line)
584
SONET path Active alarms and defects, plus counts of specific SONET errors with detailed information.

The SONET path field has the following subfields:

• REI-P—Remote error indication
• LOP-P—Loss of pointer (path)
• AIS-P—Path alarm indication signal
• RDI-P—Path remote defect indication
• UNEQ-P—Path unequipped
• PLM-P—Path payload (signal) label mismatch
• ES-P—Errored seconds (near-end STS path)
• SES-P—Severely errored seconds (near-end STS path)
• UAS-P—Unavailable seconds (near-end STS path)
• ES-PFE—Errored seconds (far-end STS path)
• SES-PFE—Severely errored seconds (far-end STS path)
• UAS-PFE—Unavailable seconds (far-end STS path)
Received SONET Values of the received and transmitted SONET overhead:

overhead
• C2—Signal label. Allocated to identify the construction and content of the STS-level SPE
Transmitted SONET and for PDI-P.
overhead • F1—Section user channel byte. This byte is set aside for the purposes of users.
• K1 and K2—These bytes are allocated for APS signaling for the protection of the multiplex
section.
• J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N signal. Used to
transmit a 1-byte fixed-length string or a 16-byte message so that a receiving terminal in a
section can verify its continued connection to the intended transmitter.
• S1—Synchronization status. The S1 byte is located in the first STS-1 number of an STS-N
signal.
• Z3 and Z4—Allocated for future use.
585
Received path trace SONET/SDH interfaces allow path trace bytes to be sent inband across the SONET/SDH link.
Juniper Networks and other router manufacturers use these bytes to help diagnose
Transmitted path
misconfigurations and network errors by setting the transmitted path trace message so that
trace
it contains the system hostname and name of the physical interface. The received path trace
value is the message received from the router at the other end of the fiber. The transmitted
path trace value is the message that this router transmits.
HDLC configuration Information about the HDLC configuration.
• Policing bucket—Configured state of the receiving policer.

• Shaping bucket—Configured state of the transmitting shaper.
• Giant threshold—Giant threshold programmed into the hardware.
• Runt threshold—Runt threshold programmed into the hardware.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine:
Engine configuration
• Destination slot—FPC slot number.
• PLP byte—Packet Level Protocol byte.
CoS information Information about the CoS queue for the physical interface.
• CoS transmit queue—Queue number and its associated user-configured forwarding class
name.
• Bandwidth %—Percentage of bandwidth allocated to the queue.
• Bandwidth bps—Bandwidth allocated to the queue (in bps).
• Buffer %—Percentage of buffer space allocated to the queue.
• Buffer usec—Amount of buffer space allocated to the queue, in microseconds. This value
is nonzero only if the buffer size is configured in terms of time.
• Priority—Queue priority: low or high.
• Limit—Displayed if rate limiting is configured for the queue. Possible values are none and
exact. If exact is configured, the queue transmits only up to the configured bandwidth, even
if excess bandwidth is available. If none is configured, the queue transmits beyond the
configured bandwidth if bandwidth is available.
Forwarding classes Total number of forwarding classes supported on the specified interface.
Egress queues Total number of egress Maximum usable queues on the specified interface.
Queue Queue number.
Forwarding classes Forwarding class name.

586
Queued Packets Number of packets queued to this queue.
Queued Bytes Number of bytes queued to this queue. The byte counts vary by PIC type.
Transmitted Packets Number of packets transmitted by this queue. When fragmentation occurs on the egress
interface, the first set of packet counters shows the postfragmentation values. The second
set of packet counters (displayed under the Packet Forwarding Engine Chassis Queues field)
shows the prefragmentation values.
Transmitted Bytes Number of bytes transmitted by this queue. The byte counts vary by PIC type.
Tail-dropped packets Number of packets dropped because of tail drop.
RED-dropped Number of packets dropped because of random early detection (RED).

packets
• (M Series and T Series routers only) On M320 and M120 routers and the T Series routers,
the total number of dropped packets is displayed. On all other M Series routers, the output
classifies dropped packets into the following categories:
• Low, non-TCP—Number of low-loss priority non-TCP packets dropped because of RED.
• Low, TCP—Number of low-loss priority TCP packets dropped because of RED.
• High, non-TCP—Number of high-loss priority non-TCP packets dropped because of RED.
• High, TCP—Number of high-loss priority TCP packets dropped because of RED.
• (MX Series routers with enhanced DPCs, and T Series routers with enhanced FPCs only)
The output classifies dropped packets into the following categories:
• Low—Number of low-loss priority packets dropped because of RED.
• Medium-low—Number of medium-low loss priority packets dropped because of RED.
• Medium-high—Number of medium-high loss priority packets dropped because of RED.
• High—Number of high-loss priority packets dropped because of RED.
NOTE: Due to accounting space limitations on certain Type 3 FPCs (which are supported in
M320 and T640 routers), this field does not always display the correct value for queue 6 or
queue 7 for interfaces on 10-port 1-Gigabit Ethernet PICs.
587
RED-dropped bytes Number of bytes dropped because of RED. The byte counts vary by PIC type.
only the total number of dropped bytes is displayed. On all other M Series routers, the
output classifies dropped bytes into the following categories:
• Low, non-TCP—Number of low-loss priority non-TCP bytes dropped because of RED.
• Low, TCP—Number of low-loss priority TCP bytes dropped because of RED.
• High, non-TCP—Number of high-loss priority non-TCP bytes dropped because of RED.
• High, TCP—Number of high-loss priority TCP bytes dropped because of RED.
Transmit rate Configured transmit rate of the scheduler. The rate is a percentage of the total interface
bandwidth.
Rate Limit Rate limiting configuration of the queue. Possible values are :
• None—No rate limit.

• exact—Queue transmits at the configured rate.
Buffer size Delay buffer size in the queue.
Priority Scheduling priority configured as low or high.
Excess Priority Priority of the excess bandwidth traffic on a scheduler: low, medium-low, medium-high, high,
or none.
Drop profiles Display the assignment of drop profiles.
• Loss priority—Packet loss priority for drop profile assignment.

• Protocol—Transport protocol for drop profile assignment.
• Index—Index of the indicated object. Objects that have indexes in this output include
schedulers and drop profiles.
• Name—Name of the drop profile.
• Type—Type of the drop profile: discrete or interpolated.
• Fill Level—Percentage fullness of a queue.
• Drop probability—Drop probability at this fill level.
Excess Priority Priority of the excess bandwidth traffic on a scheduler.

588
Drop profiles Display the assignment of drop profiles.
• Loss priority—Packet loss priority for drop profile assignment.

• Protocol—Transport protocol for drop profile assignment.
• Index—Index of the indicated object. Objects that have indexes in this output include
schedulers and drop profiles.
• Name—Name of the drop profile.
• Type—Type of the drop profile: discrete or interpolated.
• Fill Level—Percentage fullness of a queue.
• Drop probability—Drop probability at this fill level.
Adjustment Display the assignment of shaping-rate adjustments on a scheduler node or queue.

information
• Adjusting application—Application that is performing the shaping-rate adjustment.
• The adjusting application can appear as ancp LS-0, which is the Junos OS Access Node
Control Profile process (ancpd) that performs shaping-rate adjustments on schedule nodes.
• The adjusting application can appear as DHCP, which adjusts the shaping-rate and
overhead-accounting class-of-service attributes based on DSL Forum VSA conveyed in
DHCP option 82, suboption 9 (Vendor Specific Information). The shaping rate is based
on the actual-data-rate-downstream attribute. The overhead accounting value is based
on the access-loop-encapsulation attribute and specifies whether the access loop uses
Ethernet (frame mode) or ATM (cell mode).
• The adjusting application can also appear as pppoe, which adjusts the shaping-rate and
overhead-accounting class-of-service attributes on dynamic subscriber interfaces in a
broadband access network based on access line parameters in Point-to-Point Protocol
over Ethernet (PPPoE) Tags [TR-101]. This feature is supported on MPC/MIC interfaces
on MX Series routers. The shaping rate is based on the actual-data-rate-downstream
attribute. The overhead accounting value is based on the access-loop-encapsulation
attribute and specifies whether the access loop uses Ethernet (frame mode) or ATM (cell
mode).
• Adjustment type—Type of adjustment: absolute or delta.

• Configured shaping rate—Shaping rate configured for the scheduler node or queue.
• Adjustment value—Value of adjusted shaping rate.
• Adjustment target—Level of shaping-rate adjustment performed: node or queue.
• Adjustment overhead-accounting mode—Configured shaping mode: frame or cell.
• Adjustment overhead bytes—Number of bytes that the ANCP agent adds to or subtracts
from the actual downstream frame overhead before reporting the adjusted values to CoS.
• Adjustment target—Level of shaping-rate adjustment performed: node or queue.
• Adjustment multicast index—
589
Sample Output
show class-of-service interface (Physical)
user@host> show class-of-service interface so-0/2/3
Physical interface: so-0/2/3, Index: 135

Maximum usable queues: 8, Queues in use: 4
Total non—default queues created: 4
Scheduler map: <default>, Index: 2032638653
Logical interface: fe-0/0/1.0, Index: 68, Dedicated Queues: no

Shaping rate: 32000
Scheduler-map <default> 27
Rewrite exp-default exp 21
Classifier exp-default exp 5
Forwarding—class—map exp-default exp 5
show class-of-service interface (Logical)

user@host> show class-of-service interface so-0/2/3.0
Logical interface: so-0/2/3.0, Index: 68, Dedicated Queues: no

Shaping rate: 32000
Scheduler-map <default> 27
Rewrite exp-default exp 21
Forwarding—class—map exp-default exp 5
show class-of-service interface (Gigabit Ethernet)

user@host> show class-of-service interface ge-6/2/0
Physical interface: ge-6/2/0, Index: 175

Input scheduler map: <default>, Index: 3
Chassis scheduler map: <default-chassis>, Index: 4
590
show class-of-service interface (ANCP)

user@host> show class-of-service interface pp0.1073741842
Logical interface: pp0.1073741842, Index: 341

Traffic-control-profile TCP-CVLAN Output 12408
Classifier dscp-ipv6-compatibility dscp-ipv6 9
Adjusting application: ancp LS-0

Adjustment type: absolute
Configured shaping rate: 4000000
Adjustment value: 11228000
Adjustment overhead-accounting mode: Frame Mode
Adjustment overhead bytes: 50
Adjustment target: node
show class-of-service interface (PPPoE Interface)


Traffic-control-profile tcp-pppoe.o.pp0.1 Output 2726446535
Adjusting application: PPPoE

Adjustment overhead-accounting mode: cell
show class-of-service interface (DHCP Interface)

user@host> show class-of-service interface demux0.1

Traffic-control-profile tcp-dhcp.o.demux0.1 Output 2726446535
Adjusting application: DHCP

591

Adjustment overhead-accounting mode: cell
show class-of-service interface (T4000 Routers with Type 5 FPCs)

user@host> show class-of-service interface xe-4/0/0
Physical interface: xe-4/0/0, Index: 153

Shaping rate: 5000000000 bps
Logical interface: xe-4/0/0.0, Index: 77

Object Name Type
Index
Classifier ipprec-compatibility ip
13
show class-of-service interface detail

user@host> show class-of-service interface ge-0/3/0 detail

Link-level type: Ethernet, MTU: 1518, Speed: 1000mbps, Loopback: Disabled, Source
filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote
fault: Online

Scheduler map: interface-schedular-map, Index: 58414
Input shaping rate: 10000 bps
Input scheduler map: schedular-map, Index: 15103
Chassis scheduler map: <default-chassis>, Index: 4
Logical interface ge-0/3/0.0

592
inet
mpls
Interface Admin Link Proto Input Filter Output Filter
ge-0/3/0.0 up up inet
mpls
Interface Admin Link Proto Input Policer Output Policer
mpls
Logical interface: ge-0/3/0.0, Index: 68

Rewrite exp-default exp (mpls-any) 33

inet

show class-of-service interface comprehensive

user@host> show class-of-service interface ge-0/3/0 comprehensive

Link-level type: Ethernet, MTU: 1518, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow
control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online
Schedulers : 256
Current address: 00:14:f6:f4:b4:5d, Hardware address: 00:14:f6:f4:b4:5d
593

Statistics last cleared: Never Exclude Overhead Bytes: Disabled
Traffic statistics:
IPv6 total statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Ingress traffic statistics at Packet Forwarding Engine:
Drop bytes : 0 0 bps
Drop packets: 0 0 pps
Label-switched interface (LSI) traffic statistics:
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3
incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,
Resource errors: 0
Output errors:
Ingress queues: 4 supported, 5 in use
0 af3 0 0 0
1 af2 0 0 0
2 ef2 0 0 0
3 ef1 0 0 0
0 af3 0 0 0
1 af2 0 0 0
2 ef2 0 0 0
3 ef1 0 0 0
Total octets 0 0
Total packets 0 0
594
Unicast packets 0 0
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
Filter statistics:
Input DA rejects 0
Input SA rejects 0
Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault:
OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Destination slot: 0
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority
Limit
% bps % usec
2 ef2 39 19500 0 120 high
none
Direction : Input
Limit
% bps % usec
0 af3 30 3000 45 0 low
none
595

Queue: 0, Forwarding classes: af3
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : Not Available
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queue: 2, Forwarding classes: ef2
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
596

Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
RL-dropped packets : 0 0 pps
RL-dropped bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
597
Bytes : 0 0 bps
Packet Forwarding Engine Chassis Queues:

Queues: 4 supported, 5 in use
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
RED-dropped packets : Not Available
RED-dropped bytes : Not Available
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 12754752 376 bps
Transmitted:
598

Bytes : 12754752 376 bps

Scheduler map: interface-schedular-map, Index: 58414
Scheduler: ef2, Forwarding class: ef2, Index: 39155

Transmit rate: 39 percent, Rate Limit: none, Buffer size: 120 us, Buffer Limit:
none, Priority: high
Drop profiles:
Low any 1 < default-drop-profile>
Medium low any 1 < default-drop-profile>
Medium high any 1 < default-drop-profile>
High any 1 < default-drop-profile>
Drop profile: < default-drop-profile>, Type: discrete, Index: 1
Fill level Drop probability
100 100
100 100
100 100
100 100
Input shaping rate: 10000 bps
Input scheduler map: schedular-map
Scheduler map: schedular-map, Index: 15103
Scheduler: af3, Forwarding class: af3, Index: 35058

Transmit rate: 30 percent, Rate Limit: none, Buffer size: 45 percent, Buffer
Limit: none, Priority: low
Drop profiles:
599

Low any 40582 green
High any 18928 yellow
Drop profile: green, Type: discrete, Index: 40582
50 0
100 100
100 100
100 100
Drop profile: yellow, Type: discrete, Index: 18928
50 0
100 100
Chassis scheduler map: < default-drop-profile>
Scheduler map: < default-drop-profile>, Index: 4
Scheduler: < default-drop-profile>, Forwarding class: af3, Index: 25

Excess Priority: low
Drop profiles:
100 100
100 100
100 100
100 100
600
Scheduler: < default-drop-profile>, Forwarding class: af2, Index: 25

Drop profiles:
100 100
100 100
100 100
100 100
Scheduler: < default-drop-profile>, Forwarding class: ef2, Index: 25

Drop profiles:
100 100
100 100
100 100
601

100 100
Scheduler: < default-drop-profile>, Forwarding class: ef1, Index: 25

Drop profiles:
Drop profile: , Type: discrete, Index: 1
100 100
100 100
100 100
100 100
Forwarding class ID Queue Restricted queue Fabric
priority Policing priority
af3 0 0 0 low
normal
af2 1 1 1 low
normal
ef2 2 2 2 high
normal
ef1 3 3 3 high
normal
af1 4 4 0 low
normal
Traffic statistics:
Input bytes : 0
Output bytes : 0
602
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Flags: Sendbcast-pkt-to-re
Input Filters: filter-in-ge-0/3/0.0-i,
Policer: Input: p1-ge-0/3/0.0-inet-i
Protocol mpls, MTU: 1488, Maximum labels: 3, Generation: 173, Route table: 0
Flags: Is-Primary
Output Filters: exp-filter,,,,,
Forwarding class ID Queue Restricted queue Fabric priority Policing priority

SPU priority
best-effort 0 0 0 low normal
low
Aggregate Forwarding-class statistics per forwarding-class

Aggregate Forwarding-class statistics:
Forwarding-class statistics:
Forwarding-class best-effort statistics:

Input unicast bytes: 0
Output unicast bytes: 0
Input unicast packets: 0
Output unicast packets: 0
Input multicast bytes: 0

Output multicast bytes: 0
Input multicast packets: 0
Output multicast packets: 0
Forwarding-class expedited-forwarding statistics:

603


IPv4 protocol forwarding-class statistics:





IPv6 protocol forwarding-class statistics:



604



Logical interface ge-0/3/0.0 (Index 68) (SNMP ifIndex 152)

Input packets : 0
Output packets: 0

ge-0/3/0.0 up up inet filter-in-ge-0/3/0.0-i
mpls exp-filter
ge-0/3/0.0 up up
inet p1-ge-0/3/0.0-inet-i
mpls
Filter: filter-in-ge-0/3/0.0-i
Counters:
Name Bytes Packets
count-filter-in-ge-0/3/0.0-i 0 0
Filter: exp-filter
Counters:
Name Bytes Packets
count-exp-seven-match 0 0
count-exp-zero-match 0 0
Policers:
Name Packets
p1-ge-0/3/0.0-inet-i 0

605

Rewrite exp-default exp (mpls-any) 33
Rewrite rule: exp-default, Code point type: exp, Index: 33

Forwarding class Loss priority Code point
af3 low 000
af3 high 001
af2 low 010
af2 high 011
ef2 low 100
ef2 high 101
ef1 low 110
ef1 high 111
Classifier: exp-default, Code point type: exp, Index: 10

000 af3 low
001 af3 high
010 af2 low
011 af2 high
100 ef2 low
101 ef2 high
110 ef1 low
111 ef1 high
Classifier: ipprec-compatibility, Code point type: inet-precedence, Index: 13

000 af3 low
001 af3 high
010 af3 low
011 af3 high
100 af3 low
101 af3 high
110 ef1 low
111 ef1 high
af3 0 0 0 low
normal
af2 1 1 1 low
606
normal
ef2 2 2 2 high
normal
ef1 3 3 3 high
normal
af1 4 4 0 low
normal
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:

Input packets : 0
Output packets: 0

ge-0/3/0.1 up up mpls
ge-0/3/0.1 up up
mpls

607
Classifier: ipprec-compatibility, Code point type: inet-precedence, Index: 13

000 af3 low
001 af3 high
010 af3 low
011 af3 high
100 af3 low
101 af3 high
110 ef1 low
111 ef1 high
af3 0 0 0 low
normal
af2 1 1 1 low
normal
ef2 2 2 2 high
normal
ef1 3 3 3 high
normal
af1 4 4 0 low
normal
show class-of-service interface (ACX Series Routers)

user@host-g11# show class-of-service interface
Physical interface: at-0/0/0, Index: 130

Logical interface: at-0/0/0.0, Index: 69
Physical interface: at-0/0/1, Index: 133


608

Rewrite dscp-default dscp 31
Classifier d1 dscp 11331
Classifier ci ieee8021p 583

Rewrite custom-exp exp (mpls-any) 46413


Rewrite ri ieee8021p (outer) 35392
Classifier ci ieee8021p 583

609

Rewrite custom-exp2 exp (mpls-any) 53581




Classifier d1 dscp 11331


610


[edit]
user@host-g11#
show class-of-service interface (PPPoE Subscriber Interface for Enhanced Subscriber Management)

Traffic-control-profile TC_PROF_100_199_SERIES_UID1006 Output 4294967312
Scheduler-map SMAP-1_UID1002 Output 4294967327
Rewrite-Output ieee-rewrite ieee8021p 60432
Rewrite-Output rule1 ip 50463
Adjusting application: PPPoE IA tags

611
Adjusting application: ucac

Adjustment type: delta
612
show class-of-service scheduler-map

Syntax

<name>
Release Information
Command introduced in Junos OS Release 15.1R3 on MX Series routers for enhanced subscriber
management.
Description
Display the mapping of schedulers to forwarding classes and a summary of scheduler parameters for each
entry.
Options
none—Display all scheduler maps.
name—(Optional) Display a summary of scheduler parameters for each forwarding class to which the named
scheduler is assigned.

view

show class-of-service scheduler-map on page 614
show class-of-service scheduler-map (QFX Series) on page 615
Output Fields
Table 35 on page 613 describes the output fields for the show class-of-service scheduler-map command.
613
Table 35: show class-of-service scheduler-map Output Fields
Scheduler map Name of the scheduler map.
(Enhanced subscriber management for MX Series routers) The name of the dynamic scheduler
map object is associated with a generated UID (for example, SMAP-1_UID1002) instead of
with a subscriber interface.
Index Index of the indicated object. Objects having indexes in this output include scheduler maps,
schedulers, and drop profiles.
(Enhanced subscriber management for MX Series routers) Index values for dynamic CoS traffic
control profiles are larger for enhanced subscriber management than they are for legacy
subscriber management.
Scheduler Name of the scheduler.
Forwarding class Classification of a packet affecting the forwarding, scheduling, and marking policies applied
as the packet transits the router.
Transmit rate Configured transmit rate of the scheduler (in bps). The rate is a percentage of the total interface
bandwidth, or the keyword remainder, which indicates that the scheduler receives the remaining
bandwidth of the interface.
Rate Limit Rate limiting configuration of the queue. Possible values are none, meaning no rate limiting,
and exact, meaning the queue only transmits at the configured rate.
Maximum buffer Amount of transmit delay (in milliseconds) or the buffer size of the queue. The buffer size is
delay shown as a percentage of the total interface buffer allocation, or by the keyword remainder
to indicate that the buffer is sized according to what remains after other scheduler buffer
allocations.
Priority Scheduling priority: low or high.
Excess priority Priority of excess bandwidth: low, medium-low, medium-high, high, or none.
Explicit Congestion (QFX Series, OCX Series, and EX4600 switches only) Explicit congestion notification (ECN)
Notification state:
• Disable—ECN is disabled on the specified scheduler

• Enable—ECN is enabled on the specified scheduler
ECN is disabled by default.
Adjust minimum Minimum shaping rate for an adjusted queue, in bps.

614
Table 35: show class-of-service scheduler-map Output Fields (continued)
Adjust percent Bandwidth adjustment applied to a queue, in percent.
Drop profiles Table displaying the assignment of drop profiles by name and index to a given loss priority
and protocol pair.
Loss priority Packet loss priority for drop profile assignment.
Protocol Transport protocol for drop profile assignment.
Name Name of the drop profile.
Sample Output
Scheduler map: dd-scheduler-map, Index: 84
Scheduler: aa-scheduler, Index: 8721, Forwarding class: aa-forwarding-class

Transmit rate: 30 percent, Rate Limit: none, Maximum buffer delay: 39 ms,
Priority: high
Drop profiles:
Low non-TCP 8724 aa-drop-profile
Low TCP 9874 bb-drop-profile
High non-TCP 8833 cc-drop-profile
High TCP 8484 dd-drop-profile
Scheduler: bb-scheduler, Forwarding class: aa-forwarding-class

Transmit rate: 40 percent, Rate limit: none, Maximum buffer delay: 68 ms,
Priority: high
Drop profiles:
Low non-TCP 8724 aa-drop-profile
Low TCP 9874 bb-drop-profile
High non-TCP 8833 cc-drop-profile
High TCP 8484 dd-drop-profile
615
show class-of-service scheduler-map (QFX Series)

user@switch# show class-of-service scheduler-map
Scheduler map: be-map, Index: 12240
Scheduler:be-sched, Forwarding class: best-effort, Index: 115

Transmit rate: 30 percent, Rate Limit: none, Buffer size: remainder,
Buffer Limit: none, Priority: low
Excess Priority: unspecified, Explicit Congestion Notification: disable
Drop profiles:
Low any 3312 lan-dp
Medium-high any 2714 be-dp1
High any 3178 be-dp2
616
show class-of-service scheduler-hierarchy interface

Syntax
show class-of-service scheduler-hierarchy interface interface-name <detail>
Release Information
Support for up to four hierarchy levels added in Junos OS Release 16.1.
NOTE: Before Junos OS R19.2, the shaping rate would incorrectly display as 90% of the
guaranteed rate.
Description
For MPC/MIC interfaces only, display the scheduler hierarchy as well as the shaping rate, guaranteed rate,
priorities, and queue weight information for each forwarding class at each hierarchy level.
Options
detail—(Optional) Display scheduler hierarchies based on the interface set.
interface-name—Display information about a specific interface.

view

show class-of-service scheduler-hierarchy interface on page 617
Output Fields
Table 36 on page 616 describes the output fields for the show class-of-service scheduler-hierarchy interface
command. Output fields are listed in the approximate order in which they appear.
Table 36: show class-of-service scheduler-hierarchy interface Output Fields
interface Interface name

617
Table 36: show class-of-service scheduler-hierarchy interface Output Fields (continued)
resource Traffic resource associated with the logical interface
shaping-rate Shaping rate in bits per second
guaranteed rate Guaranteed rate in bits per second
guaranteed priority Queue priority in the guaranteed region (high, low, or none)
excess priority Queue priority in the excess region (high, low, or none)
queue weight Queue weight for excess CoS weighted round-robin
excess weight Interface unit per priority weights for excess weighted round-robin
Sample Output
show class-of-service scheduler-hierarchy interface
user@host> show class-of-service scheduler-hierarchy interface xe-1/0/0
--------------------------------------------------------------------------------
Interface/ shaping guaranteed guaranteed/ queue excess
resource name rate rate excess weight weight
kbits kbits priority high/low
--------------------------------------------------------------------------------
xe-1/0/0 12000
<<< L1
xe-1/0/0 RTP 12000 0 1 1
best-effort 12000 0 Low Low 950

network-control 12000 0 Low Low 50
ifset1 12000 0 500 500
<<< L2
ifset1 RTP 12000 0 1 1
be1 720 0 Low Low 250
nc1 12000 0 Low Low 250
demux0.96 3000 0 1 1
<<< L3
demux0.96 RTP 3000 0 500 500
618
be1 1000 0 Low Low 250

nc1 3000 0 Low Low 250
pp0.81 2000 0 1 1
<<< L4
be1 1000 0 Low Low 250
nc1 2000 0 Low Low 250
619
show class-of-service scheduler-hierarchy interface-set

Syntax
show class-of-service scheduler-hierarchy interface-set interface-set-name <detail>
Release Information
Description
For MPC/MIC interface sets only, display the scheduler hierarchy.
Options
detail—(Optional) Display scheduler hierarchies based on the interface-set.
interface-set-name—Display information about a specific interface-set.

view

show class-of-service scheduler-hierarchy interface-set on page 620
Output Fields
Table 37 on page 619 describes the output fields for the show class-of-service scheduler-hierarchy
interface-set command. Output fields are listed in the approximate order in which they appear.
Table 37: show class-of-service scheduler-hierarchy interface-set Output Fields
interface Type of interface
resource Traffic resource associated with the logical interface
shaping-rate Actual shaping rate in bits per second
guaranteed rate Actual guaranteed rate in bits per second
guaranteed priority Actual queue priority in the guaranteed region (high, low, or none)
620
Table 37: show class-of-service scheduler-hierarchy interface-set Output Fields (continued)
excess priority Actual queue priority in the excess region (high, low, or none)
queue weight Actual queue weight for excess CoS weighted round-robin
excess weight Actual interface-set per priority weights for excess weighted round-robin
Sample Output
show class-of-service scheduler-hierarchy interface-set
user@host> show class-of-service scheduler-hierarchy interface-set ifset
--------------------------------------------------------------------------------
Interface/ shaping guarnteed guaranteed/ queue excess
resource name rate rate excess weight weight
kbits kbits priority high/low
--------------------------------------------------------------------------------
ge-1/0/0 100000
ge-1/0/0 RTP 100000 0 1 1
be 100000 1000 Low Low 1
da 9000 2000 Medium High 1
vi 100000 3000 Medium None 626
vo 100000 4000 High High 373
gt 100000 0 High High 1
ge-1/0/0.20 50000 40000 750 750
be 50000 1000 Low Low 1
da 9000 2000 Medium High 1
vi 50000 3000 Medium None 626
vo 50000 4000 High High 373
gt 50000 Disabled High High 1
621
show interfaces
List of Syntax
Syntax (Gigabit Ethernet) on page 621
Syntax (10 Gigabit Ethernet) on page 621
Syntax (SRX Series Devices and (vSRX and vSRX 3.0 platforms)) on page 621
Syntax (Gigabit Ethernet)
show interfaces ge-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>
Syntax (10 Gigabit Ethernet)
show interfaces xe-fpc/pic/port

<descriptions>
<media>
<statistics>
Syntax (SRX Series Devices and (vSRX and vSRX 3.0 platforms))
show interfaces (
<interface-name>
<controller interface-name>|
<descriptions interface-name>|
<destination-class (all | destination-class-name logical-interface-name)>|
<diagnostics optics interface-name>|
<far-end-interval interface-fpc/pic/port>|
<filters interface-name>|
<flow-statistics interface-name>|
<interval interface-name>|
<load-balancing (detail | interface-name)>|
<mac-database mac-address mac-address>|
<mc-ae id identifier unit number revertive-info>|
<media interface-name>|
<policers interface-name>|
622
<queue both-ingress-egress egress forwarding-class forwarding-class ingress l2-statistics>|

<redundancy (detail | interface-name)>|
<routing brief detail summary interface-name>|
<routing-instance (all | instance-name)>|
<snmp-index snmp-index>|
<source-class (all | destination-class-name logical-interface-name)>|
<statistics interface-name>|
<switch-port switch-port number>|
<transport pm (all | optics | otn) (all | current | currentday | interval | previousday) (all | interface-name)>|
<zone interface-name>
)
Release Information
Command introduced before Junos OS Release 7.4 for Gigabit interfaces.
Command introduced in Junos OS Release 8.0 for 10 Gigabit interfaces.
Command modified in Junos OS Release 9.5 for SRX Series devices.
Command introduced in Junos OS Release 18.1 for Gigabit interfaces.
Command modified in Junos OS Release 19.3R1 for MX Series Routers.
Starting in Junos OS Release 19.3R1, Output fields Ifindex and speed is modified in the show interfaces
interface name extensive command, on all MX Series routers.
• The default behavior of WAN-PHY interface remains the same.The new precise-bandwidth option
reflects the new speed (9.294-Gbps) configured on the supported line cards.
• The WAN-PHY framing mode is supported only on MPC5E and MPC6E line cards.
Starting in Junos OS Release 19.3R1, class of service (CoS) features can be configured on the physical
interface with speed rates of 1-Gbps, 10-Gbps, 40-Gbps, and 100-Gbps to provide better bandwidth for
processing traffic during congestion using variant speeds.
Description
Display status information about the specified Gigabit Ethernet interface.
(M320, M120, MX Series, and T Series routers only) Display status information about the specified
10-Gigabit Ethernet interface.
Display the IPv6 interface traffic statistics about the specified Gigabit Ethernet interface for MX series
routers. The input and output bytes (bps) and packets (pps) rates are not displayed for IFD and local traffic.
Display status information and statistics about interfaces on SRX Series, vSRX, and vSRX 3.0 platforms
running Junos OS.
623
NOTE: On SRX Series appliances, on configuring identical IPs on a single interface, you will not
see a warning message; instead, you will see a syslog message.
Starting in Junos OS Release 18.4R1, Output fields Next-hop and vpls-status is displayed in the show
interfaces interface name detail command, only for Layer 2 protocols on MX480 routers.
Options
For Gigabit interfaces:
ge-fpc/pic/port—Display standard information about the specified Gigabit Ethernet interface.
NOTE: Interfaces with different speeds are named uniformly with ge-0/0/x for backward
compatibility. Use the show interfaces command to view the interface speeds.
brief | detail | extensive | terse—(Optional) Display the specified level of output.
descriptions—(Optional) Display interface description strings.
media—(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index—(Optional) Display information for the specified SNMP index of the interface.
statistics—(Optional) Display static interface statistics.
For 10 Gigabit interfaces:
xe-fpc/pic/port—Display standard information about the specified 10-Gigabit Ethernet interface.
For SRX interfaces:
• interface-name—(Optional) Display standard information about the specified interface. Following is a

list of typical interface names. Replace pim with the PIM slot and port with the port number.
624
• at- pim/0/port—ATM-over-ADSL or ATM-over-SHDSL interface.
• ce1-pim/0/ port—Channelized E1 interface.
• cl-0/0/8—3G wireless modem interface for SRX320 devices.
• ct1-pim/0/port—Channelized T1 interface.
• dl0—Dialer Interface for initiating ISDN and USB modem connections.
• e1-pim/0/port—E1 interface.
• fe-pim/0/port—Fast Ethernet interface.
• ge-pim/0/port—Gigabit Ethernet interface.
• se-pim/0/port—Serial interface.
• t1-pim/0/port—T1 (also called DS1) interface.
• wx-slot/0/0—WAN acceleration interface, for the WXC Integrated Services Module (ISM 200).
• interface-name—(Optional) Display standard information about the specified interface. Following is

a list of typical interface names. Replace pim with the PIM slot and port with the port number.
• at- pim/0/port—ATM-over-ADSL or ATM-over-SHDSL interface.
• ce1-pim/0/ port—Channelized E1 interface.
• cl-0/0/8—3G wireless modem interface for SRX320 devices.
• ct1-pim/0/port—Channelized T1 interface.
• dl0—Dialer Interface for initiating ISDN and USB modem connections.
• fe-pim/0/port—Fast Ethernet interface.
• ge-pim/0/port—Gigabit Ethernet interface.
• se-pim/0/port—Serial interface.
• wx-slot/0/0—WAN acceleration interface, for the WXC Integrated Services Module (ISM 200).
Additional Information
In a logical system, this command displays information only about the logical interfaces and not about the
physical interfaces.
625

view
Release Description
18.4R1 Starting in Junos OS Release 18.4R1, Output fields Next-hop and vpls-status is displayed
in the show interfaces interface name detail command, only for Layer 2 protocols on MX480
routers.
Understanding Layer 2 Interfaces on Security Devices

Verifying and Managing Agent Circuit Identifier-Based Dynamic VLAN Configuration
Verifying and Managing Configurations for Dynamic VLANs Based on Access-Line Identifiers

show interfaces (Gigabit Ethernet) on page 674
show interfaces (Gigabit Ethernet on MX Series Routers) on page 675
show interfaces (link degrade status) on page 676
show interfaces extensive (Gigabit Ethernet on MX Series Routers showing interface transmit statistics
configuration) on page 677
show interfaces brief (Gigabit Ethernet) on page 678
show interfaces detail (Gigabit Ethernet) on page 678
show interfaces extensive (Gigabit Ethernet IQ2) on page 680
show interfaces (Gigabit Ethernet Unnumbered Interface) on page 684
show interfaces (ACI Interface Set Configured) on page 684
show interfaces (ALI Interface Set) on page 685
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2) on page 685
show interfaces extensive (10-Gigabit Ethernet, WAN PHY Mode) on page 688
show interfaces extensive (10-Gigabit Ethernet, DWDM OTN PIC) on page 691
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode) on page 694
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Transmit-Only) on page 695
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Receive-Only) on page 696
Sample Output SRX Gigabit Ethernet on page 698
Sample Output SRX Gigabit Ethernet on page 698
show interfaces (Gigabit Ethernet for vSRX and vSRX 3.0) on page 699
show interfaces detail (Gigabit Ethernet) on page 700
show interfaces statistics st0.0 detail on page 702
626
show interfaces extensive (Gigabit Ethernet) on page 703

show interfaces terse on page 706
show interfaces terse (vSRX and vSRX 3.0) on page 707
show interfaces controller (Channelized E1 IQ with Logical E1) on page 708
show interfaces controller (Channelized E1 IQ with Logical DS0) on page 708
show interfaces descriptions on page 708
show interfaces destination-class all on page 709
show interfaces diagnostics optics on page 709
show interfaces far-end-interval coc12-5/2/0 on page 710
show interfaces far-end-interval coc1-5/2/1:1 on page 711
show interfaces filters on page 711
show interfaces flow-statistics (Gigabit Ethernet) on page 712
show interfaces interval (Channelized OC12) on page 713
show interfaces interval (E3) on page 714
show interfaces interval (SONET/SDH) (SRX devices) on page 714
show interfaces load-balancing (SRX devices) on page 715
show interfaces load-balancing detail (SRX devices) on page 715
show interfaces mac-database (All MAC Addresses on a Port SRX devices) on page 715
show interfaces mac-database (All MAC Addresses on a Service SRX devices) on page 716
show interfaces mac-database mac-address on page 717
show interfaces mc-ae (SRX devices) on page 717
show interfaces media (SONET/SDH) on page 717
show interfaces policers (SRX devices) on page 718
show interfaces policers interface-name (SRX devices) on page 719
show interfaces queue (SRX devices) on page 719
show interfaces redundancy (SRX devices) on page 720
show interfaces redundancy (Aggregated Ethernet SRX devices) on page 720
show interfaces redundancy detail (SRX devices) on page 721
show interfaces routing brief (SRX devices) on page 721
show interfaces routing detail (SRX devices) on page 722
show interfaces routing-instance all (SRX devices) on page 722
show interfaces snmp-index (SRX devices) on page 723
show interfaces source-class all (SRX devices) on page 723
show interfaces statistics (Fast Ethernet SRX devices) on page 724
show interfaces switch-port (SRX devices) on page 725
show interfaces transport pm (SRX devices) on page 725
show security zones (SRX devices) on page 727
Output Fields
Table 38 on page 627 describes the output fields for the show interfaces (Gigabit Ethernet) command.
Output fields are listed in the approximate order in which they appear. For Gigabit Ethernet IQ and IQE
PICs, the traffic and MAC statistics vary by interface type. For more information, see Table 39 on page 665.
627
Table 38: show interfaces (Gigabit Ethernet) Output Fields
Field Name Field Description Level of Output
Physical Interface
Physical interface Name of the physical interface. All levels
Enabled State of the interface. Possible values are described in the “Enabled Field” All levels
section under Common Output Fields Description.
Interface index Index number of the physical interface, which reflects its initialization detail extensive none
sequence.
SNMP ifIndex SNMP index number for the physical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Link-level type Encapsulation being used on the physical interface. All levels
MTU Maximum transmission unit size on the physical interface. All levels
Speed Speed at which the interface is running. All levels
Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of All levels
loopback: Local or Remote.
Source filtering Source filtering status: Enabled or Disabled. All levels
LAN-PHY mode 10-Gigabit Ethernet interface operating in Local Area Network Physical All levels
Layer Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide
area links to use existing Ethernet applications.
WAN-PHY mode 10-Gigabit Ethernet interface operating in Wide Area Network Physical All levels
Layer Device (WAN PHY) mode. WAN PHY allows 10-Gigabit Ethernet
wide area links to use fiber-optic cables and other devices intended for
SONET/SDH.
Unidirectional Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled All levels
or Disabled for parent interface; Rx-only or Tx-only for child interfaces.
Flow control Flow control status: Enabled or Disabled. All levels
Auto-negotiation (Gigabit Ethernet interfaces) Autonegotiation status: Enabled or Disabled. All levels
628
Table 38: show interfaces (Gigabit Ethernet) Output Fields (continued)
Remote-fault (Gigabit Ethernet interfaces) Remote fault status: All levels

Device flags Information about the physical device. Possible values are described in All levels
the “Device Flags” section under Common Output Fields Description.
Interface flags Information about the interface. Possible values are described in the All levels
“Interface Flags” section under Common Output Fields Description.
Link flags Information about the link. Possible values are described in the “Links All levels
Flags” section under Common Output Fields Description.
Wavelength (10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM] All levels

interfaces) Displays the configured wavelength, in nanometers (nm).
Frequency (10-Gigabit Ethernet DWDM interfaces only) Displays the frequency All levels
associated with the configured wavelength, in terahertz (THz).
CoS queues Number of CoS queues configured. detail extensive none
Schedulers (Gigabit Ethernet intelligent queuing 2 [IQ2] interfaces only) Number of extensive
CoS schedulers configured.
Hold-times Current interface hold-time up and hold-time down, in milliseconds (ms). detail extensive
Current address Configured MAC address. detail extensive none
Hardware address Hardware MAC address. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The detail extensive none
format is Last flapped: year-month-day hour:minute:second:timezone
(hour:minute:second ago). For example, Last flapped: 2002-04-26 10:52:40
PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). The value None
in this field also includes the Layer 2 overhead bytes for ingress traffic on
Ethernet interfaces if you enable accounting of Layer 2 overhead at the
PIC level or the logical interface level.
629
Output Rate Output rate in bps and pps. The value in this field also includes the Layer None
2 overhead bytes for egress traffic on Ethernet interfaces if you enable
accounting of Layer 2 overhead at the PIC level or the logical interface
level.
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Egress account Layer 2 overhead in bytes that is accounted in the interface statistics for detail extensive
overhead egress traffic.
Ingress account Layer 2 overhead in bytes that is accounted in the interface statistics for detail extensive
overhead ingress traffic.
Traffic statistics Number and rate of bytes and packets received and transmitted on the detail extensive
physical interface.
• Input bytes—Number of bytes received on the interface. The value in

this field also includes the Layer 2 overhead bytes for ingress traffic on
Ethernet interfaces if you enable accounting of Layer 2 overhead at
the PIC level or the logical interface level.
• Output bytes—Number of bytes transmitted on the interface. The value
in this field also includes the Layer 2 overhead bytes for egress traffic
on Ethernet interfaces if you enable accounting of Layer 2 overhead at
the PIC level or the logical interface level.
Gigabit Ethernet and 10-Gigabit Ethernet IQ PICs count the overhead
and CRC bytes.
For Gigabit Ethernet IQ PICs, the input byte counts vary by interface type.
For more information, see Table 31 under the show interfaces command.
630
Input errors Input errors on the interface. The following paragraphs explain the extensive
counters whose meaning might not be obvious:

• Drops—Number of packets dropped by the input queue of the I/O
Manager ASIC. If the interface is saturated, this number increments
once for every packet that is dropped by the ASIC's RED mechanism.
• Framing errors—Number of packets received with an invalid frame
checksum (FCS).
• Runts—Number of frames received that are smaller than the runt
threshold.
• Policed discards—Number of frames that the incoming packet match
code discarded because they were not recognized or not of interest.
Usually, this field reports protocols that Junos OS does not handle.
• L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example,
a frame with less than 20 bytes of available IP header is discarded. L3
incomplete errors can be ignored by configuring the
ignore-l3-incompletes statement.
• L2 channel errors—Number of times the software did not find a valid
logical interface for an incoming frame.
• L2 mismatch timeouts—Number of malformed or short packets that
caused the incoming packet handler to discard the frame as unreadable.
• FIFO errors—Number of FIFO errors in the receive direction that are
reported by the ASIC on the PIC. If this value is ever nonzero, the PIC
is probably malfunctioning.
• Resource errors—Sum of transmit drops.
631
Output errors Output errors on the interface. The following paragraphs explain the extensive
• Carrier transitions—Number of times the interface has gone from down

to up. This number does not normally increment quickly, increasing
only when the cable is unplugged, the far-end system is powered down
and then up, or another problem occurs. If the number of carrier
transitions increments quickly (perhaps once every 10 seconds), the
cable, the far-end system, or the PIC or PIM is malfunctioning.
• Drops—Number of packets dropped by the output queue of the I/O
NOTE: Due to accounting space limitations on certain Type 3 FPCs

(which are supported in M320 and T640 routers), the Drops field
does not always use the correct value for queue 6 or queue 7 for
interfaces on 10-port 1-Gigabit Ethernet PICs.
• Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC

supports only full-duplex operation, so for Gigabit Ethernet PICs, this
number must always be 0. If it is nonzero, there is a software bug.
• Aged packets—Number of packets that remained in shared packet
SDRAM so long that the system automatically purged them. The value
in this field must never increment. If it does, it is most likely a software
bug or possibly malfunctioning hardware.
• FIFO errors—Number of FIFO errors in the send direction as reported
by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
• HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the router interfaces.
• MTU errors—Number of packets whose size exceeded the MTU of the
interface.
632
Egress queues Total number of egress queues supported on the specified interface. detail extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE
R, DPCE 20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a
discrepancy in the output of the show interfaces command because
incoming packets might be counted in the Egress queues section of the
output. This problem occurs on non-enhanced DPCs because the egress
queue statistics are polled from IMQ (Inbound Message Queuing) block
of the I-chip. The IMQ block does not differentiate between ingress and
egress WAN traffic; as a result, the combined statistics are displayed in
the egress queue counters on the Routing Engine. In a simple VPLS
scenario, if there is no MAC entry in DMAC table (by sending unidirectional
traffic), traffic is flooded and the input traffic is accounted in IMQ. For
bidirectional traffic (MAC entry in DMAC table), if the outgoing interface
is on the same I-chip then both ingress and egress statistics are counted
in a combined way. If the outgoing interface is on a different I-chip or
FPC, then only egress statistics are accounted in IMQ. This behavior is
expected with non-enhanced DPCs
Queue counters CoS queue number and its associated user-configured forwarding class detail extensive
(Egress) name.

• Dropped packets—Number of packets dropped by the ASIC's RED
mechanism.
NOTE: Due to accounting space limitations on certain Type 3 FPCs

(which are supported in M320 and T640 routers), the Dropped packets
field does not always display the correct value for queue 6 or queue 7
for interfaces on 10-port 1-Gigabit Ethernet PICs.
Ingress queues Total number of ingress queues supported on the specified interface. extensive
Displayed on IQ2 interfaces.
Queue counters CoS queue number and its associated user-configured forwarding class extensive
(Ingress) name. Displayed on IQ2 interfaces.

mechanism.
633
Active alarms and Ethernet-specific defects that can prevent the interface from passing detail extensive none
Active defects packets. When a defect persists for a certain amount of time, it is
promoted to an alarm. Based on the router configuration, an alarm can
ring the red or yellow alarm bell on the router, or turn on the red or yellow
alarm LED on the craft interface. These fields can contain the value None
or Link.
• None—There are no active defects or alarms.

• Link—Interface has lost its link state, which usually means that the cable
is unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
Interface transmit (On MX Series devices) Status of the interface-transmit-statistics detail extensive
statistics configuration: Enabled or Disabled.
• Enabled—When the interface-transmit-statistics statement is included

in the configuration. If this is configured, the interface statistics show
the actual transmitted load on the interface.
• Disabled—When the interface-transmit-statistics statement is not
included in the configuration. If this is not configured, the interface
statistics show the offered load on the interface.
OTN FEC statistics The forward error correction (FEC) counters provide the following detail extensive
statistics:
• Corrected Errors—Count of corrected errors in the last second.

• Corrected Error Ratio—Corrected error ratio in the last 25 seconds. For
example, 1e-7 is 1 error per 10 million bits.
PCS statistics (10-Gigabit Ethernet interfaces) Displays Physical Coding Sublayer (PCS) detail extensive
fault conditions from the WAN PHY or the LAN PHY device.
• Bit errors—Number of seconds during which at least one bit error rate
(BER) occurred while the PCS receiver is operating in normal mode.
• Errored blocks—Number of seconds when at least one errored block
occurred while the PCS receiver is operating in normal mode.
634
Link Degrade Shows the link degrade status of the physical link and the estimated bit detail extensive
error rates (BERs). This field is available only for the PICs supporting the
physical link monitoring feature.
• Link Monitoring—Indicates if physical link degrade monitoring is enabled

on the interface.
• Enable—Indicates that link degrade monitoring has been enabled
(using the link-degrade-monitor statement) on the interface.
• Disable—Indicates that link degrade monitoring has not been enabled
on the interface. If link degrade monitoring has not been enabled,
the output does not show any related information, such as BER values
and thresholds.
• Link Degrade Set Threshold—The BER threshold value at which the

link is considered degraded and a corrective action is triggered.
• Link Degrade Clear Threshold—The BER threshold value at which the
degraded link is considered recovered and the corrective action applied
to the interface is reverted.
• Estimated BER—The estimated bit error rate.
• Link-degrade event—Shows link degrade event information.
• Seconds—Time (in seconds) elapsed after a link degrade event
occurred.
• Count—The number of link degrade events recorded.
• State—Shows the link degrade status (example: Defect Active).
635
MAC statistics extensive

636
Receive and Transmit statistics reported by the PIC's MAC subsystem,

including the following:
• Total octets and total packets—Total number of octets and packets.

For Gigabit Ethernet IQ PICs, the received octets count varies by
interface type. For more information, see Table 31 under the show
interfaces command.
• Unicast packets, Broadcast packets, and Multicast packets—Number

of unicast, broadcast, and multicast packets.
• CRC/Align errors—Total number of packets received that had a length
(excluding framing bits, but including FCS octets) of between 64 and
1518 octets, inclusive, and had either a bad FCS with an integral number
of octets (FCS Error) or a bad FCS with a nonintegral number of octets
(Alignment Error).
• FIFO error—Number of FIFO errors that are reported by the ASIC on
the PIC. If this value is ever nonzero, the PIC or a cable is probably
malfunctioning.
• MAC control frames—Number of MAC control frames.
• MAC pause frames—Number of MAC control frames with pause
operational code.
• Oversized frames—There are two possible conditions regarding the
number of oversized frames:
• Packet length exceeds interface MTU, or

• Packet length exceeds MRU
• Jabber frames—Number of frames that were longer than 1518 octets
(excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. This definition of jabber is different
from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section
10.3.1.4 (10BASE2). These documents define jabber as the condition
in which any packet exceeds 20 ms. The allowed range to detect jabber
is from 20 ms to 150 ms.
• Fragment frames—Total number of packets that were less than 64
octets in length (excluding framing bits, but including FCS octets) and
had either an FCS error or an alignment error. Fragment frames normally
increment because both runts (which are normal occurrences caused
by collisions) and noise hits are counted.
• VLAN tagged frames—Number of frames that are VLAN tagged. The
system uses the TPID of 0x8100 in the frame to determine whether a
frame is tagged or not.
637
NOTE: The 20-port Gigabit Ethernet MIC (MIC-3D-20GE-SFP) does

not have hardware counters for VLAN frames. Therefore, the VLAN
tagged frames field displays 0 when the show interfaces command is
executed on a 20-port Gigabit Ethernet MIC. In other words, the number
of VLAN tagged frames cannot be determined for the 20-port Gigabit
Ethernet MIC.
• Code violations—Number of times an event caused the PHY to indicate

“Data reception error” or “invalid data symbol error.”
OTN Received APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 extensive
Overhead Bytes Payload Type: 0x08
OTN Transmitted APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00 extensive
Overhead Bytes Payload Type: 0x08
638
Filter statistics Receive and Transmit statistics reported by the PIC's MAC address filter extensive
subsystem. The filtering is done by the content-addressable memory
(CAM) on the PIC. The filter examines a packet's source and destination
MAC addresses to determine whether the packet may enter the system
or be rejected.
• Input packet count—Number of packets received from the MAC

hardware that the filter processed.
• Input packet rejects—Number of packets that the filter rejected because
of either the source MAC address or the destination MAC address.
• Input DA rejects—Number of packets that the filter rejected because
the destination MAC address of the packet is not on the accept list. It
is normal for this value to increment. When it increments very quickly
and no traffic is entering the router from the far-end system, either
there is a bad ARP entry on the far-end system, or multicast routing is
not on and the far-end system is sending many multicast packets to the
local router (which the router is rejecting).
• Input SA rejects—Number of packets that the filter rejected because
the source MAC address of the packet is not on the accept list. The
value in this field must increment only if source MAC address filtering
has been enabled. If filtering is enabled, if the value increments quickly,
and if the system is not receiving traffic that it should from the far-end
system, it means that the user-configured source MAC addresses for
this interface are incorrect.
• Output packet count—Number of packets that the filter has given to
the MAC hardware.
• Output packet pad count—Number of packets the filter padded to the
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some
very small IP packets can also require padding. If this value increments
rapidly, either the system is trying to find an ARP entry for a far-end
system that does not exist or it is misconfigured.
• Output packet error count—Number of packets with an indicated error
that the filter was given to transmit. These packets are usually aged
packets or are the result of a bandwidth problem on the FPC hardware.
On a normal system, the value of this field must not increment.
• CAM destination filters, CAM source filters—Number of entries in the
CAM dedicated to destination and source MAC address filters. There
can only be up to 64 source entries. If source filtering is disabled, which
is the default, the values for these fields must be 0.
639
PMA PHY (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error extensive
information:

• Count—Number of times that the defect has gone from inactive to
active.
• State—State of the error. Any state other than OK indicates a problem.
Subfields are:
• PHY Lock—Phase-locked loop

• PHY Light—Loss of optical signal
WIS section (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error extensive
information:

active.
Subfields are:

• LOL—Loss of light
640
WIS line (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and extensive
defects, plus counts of specific SONET errors with detailed information:

active.
Subfields are:

641
WIS path (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and extensive
defects, plus counts of specific SONET errors with detailed information:

active.
Subfields are:

• PLM-P—Path payload (signal) label mismatch
642
Autonegotiation Information about link autonegotiation. extensive

information
• Negotiation status:
• Incomplete—Ethernet interface has the speed or link mode
configured.
• No autonegotiation—Remote Ethernet interface has the speed or
link mode configured, or does not perform autonegotiation.
• Complete—Ethernet interface is connected to a device that performs
autonegotiation and the autonegotiation process is successful.
• Link partner status—OK when Ethernet interface is connected to a

device that performs autonegotiation and the autonegotiation process
is successful.
• Link partner—Information from the remote Ethernet device:
• Link mode—Depending on the capability of the link partner, either
Full-duplex or Half-duplex.
• Flow control—Types of flow control supported by the link partner.
For Gigabit Ethernet interfaces, types are Symmetric (link partner
supports PAUSE on receive and transmit), Asymmetric (link partner
supports PAUSE on transmit), Symmetric/Asymmetric (link partner
supports PAUSE on receive and transmit or only PAUSE on transmit),
and None (link partner does not support flow control).
• Remote fault—Remote fault information from the link partner—Failure
indicates a receive link error. OK indicates that the link partner is
receiving. Negotiation error indicates a negotiation error. Offline
indicates that the link partner is going offline.
• Local resolution—Information from the local Ethernet device:

• Flow control—Types of flow control supported by the local device.
For Gigabit Ethernet interfaces, advertised capabilities are
Symmetric/Asymmetric (local device supports PAUSE on receive
and transmit or only PAUSE on receive) and None (local device does
not support flow control). Depending on the result of the negotiation
with the link partner, local resolution flow control type will display
Symmetric (local device supports PAUSE on receive and transmit),
Asymmetric (local device supports PAUSE on receive), and None
(local device does not support flow control).
• Remote fault—Remote fault information. Link OK (no error detected
on receive), Offline (local interface is offline), and Link Failure (link
error detected on receive).
643
Received path trace, (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces extensive
Transmitted path allow path trace bytes to be sent inband across the SONET/SDH link.
trace Juniper Networks and other router manufacturers use these bytes to help
diagnose misconfigurations and network errors by setting the transmitted
path trace message so that it contains the system hostname and name of
the physical interface. The received path trace value is the message
received from the router at the other end of the fiber. The transmitted
path trace value is the message that this router transmits.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
CoS information Information about the CoS queue for the physical interface. extensive
• CoS transmit queue—Queue number and its associated user-configured

forwarding class name.
• Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is configured
in terms of time.
• Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface, which reflects its initialization detail extensive none
sequence.
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
644
Flags Information about the logical interface. Possible values are described in All levels
the “Logical Interface Flags” section under Common Output Fields
Description.
VLAN-Tag Rewrite profile applied to incoming or outgoing frames on the outer (Out) brief detail extensive
VLAN tag or for both the outer and inner (In) VLAN tags. none
• push—An outer VLAN tag is pushed in front of the existing VLAN tag.
• pop—The outer VLAN tag of the incoming frame is removed.
• swap—The outer VLAN tag of the incoming frame is overwritten with
the user-specified VLAN tag information.
• push-push—Two VLAN tags are pushed in from the incoming frame.
• swap-push—The outer VLAN tag of the incoming frame is replaced by
a user-specified VLAN tag value. A user-specified outer VLAN tag is
pushed in front. The outer tag becomes an inner tag in the final frame.
• swap-swap—Both the inner and the outer VLAN tags of the incoming
frame are replaced by the user-specified VLAN tag value.
• pop-swap—The outer VLAN tag of the incoming frame is removed, and
the inner VLAN tag of the incoming frame is replaced by the
user-specified VLAN tag value. The inner tag becomes the outer tag in
the final frame.
• pop-pop—Both the outer and inner VLAN tags of the incoming frame
are removed.
Demux IP demultiplexing (demux) value that appears if this interface is used as detail extensive none
the demux underlying interface. The output is one of the following:
• Source Family Inet

• Destination Family Inet
Encapsulation Encapsulation on the logical interface. All levels

645
ACI VLAN Information displayed for agent circuit identifier (ACI) interface set brief detail extensive
configured with the agent-circuit-id autoconfiguration stanza. none
Dynamic Profile—Name of the dynamic profile that defines the ACI

interface set.
If configured, the ACI interface set enables the underlying Ethernet

interface to create dynamic VLAN subscriber interfaces based on ACI
information.
NOTE: The ACI VLAN field is replaced with the Line Identity field when
an ALI interface set is configured with the line-identity autoconfiguration
stanza.
Line Identity Information displayed for access-line-identifier (ALI) interface sets detail
configured with the line-identity autoconfiguration stanza.
• Dynamic Profile—Name of the dynamic profile that defines the ALI

interface set.
• Trusted option used to create the ALI interface set: Circuit-id,
Remote-id, or Accept-no-ids. More than one option can be configured.
If configured, the ALI interface set enables the underlying Ethernet

interface to create dynamic VLAN subscriber interfaces based on ALI
information.
NOTE: The Line Identity field is replaced with the ACI VLAN field when
an ACI interface set is configured with the agent-circuit-id
autoconfiguration stanza.
Protocol Protocol family. Possible values are described in the “Protocol Field” detail extensive none
MTU Maximum transmission unit size on the logical interface. detail extensive none
Neighbor Discovery NDP statistics for protocol inet6 under logical interface statistics. All levels
Protocol
(NDP)Queue • Max nh cache—Maximum interface neighbor discovery nexthop cache
size.
Statistics
• New hold nh limit—Maximum number of new unresolved nexthops.
• Curr nh cnt—Current number of resolved nexthops in the NDP queue.
• Curr new hold cnt—Current number of unresolved nexthops in the NDP
queue.
• NH drop cnt—Number of NDP requests not serviced.
646
Dynamic Profile Name of the dynamic profile that was used to create this interface detail extensive none
configured with a Point-to-Point Protocol over Ethernet (PPPoE) family.
Service Name Table Name of the service name table for the interface configured with a PPPoE detail extensive none
family.
Max Sessions Maximum number of PPPoE logical interfaces that can be activated on detail extensive none
the underlying interface.
Duplicate State of PPPoE duplicate protection: On or Off. When duplicate protection detail extensive none
Protection is configured for the underlying interface, a dynamic PPPoE logical
interface cannot be activated when an existing active logical interface is
present for the same PPPoE client.
Direct Connect State of the configuration to ignore DSL Forum VSAs: On or Off. When detail extensive none
configured, the router ignores any of these VSAs received from a directly
connected CPE device on the interface.
AC Name Name of the access concentrator. detail extensive none
Maximum labels Maximum number of MPLS labels configured for the MPLS protocol family detail extensive none
on the logical interface.
specified interface set.
• Input bytes, Output bytes—Number of bytes received and transmitted

on the interface set. The value in this field also includes the Layer 2
overhead bytes for ingress or egress traffic on Ethernet interfaces if
you enable accounting of Layer 2 overhead at the PIC level or the logical
interface level.
• Input packets, Output packets—Number of packets received and
transmitted on the interface set.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on extensive
statistics the logical interface if IPv6 statistics tracking is enabled.
Local statistics Number and rate of bytes and packets destined to the router. extensive
647
Transit statistics Number and rate of bytes and packets transiting the switch. extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the

logical interface egress statistics might not accurately reflect the traffic
on the wire when output shaping is applied. Traffic management output
shaping might drop packets after they are tallied by the Output bytes and
Output packets interface counters. However, correct values display for
both of these egress statistics when per-unit scheduling is enabled for
the Gigabit Ethernet IQ2 physical interface, or when a single logical
interface is actively using a shared scheduler.
Route Table Route table in which the logical interface address is located. For example, detail extensive none
0 refers to the routing table inet.0.
Flags Information about protocol family flags. Possible values are described in detail extensive
the “Family Flags” section under Common Output Fields Description.
Donor interface (Unnumbered Ethernet) Interface from which an unnumbered Ethernet detail extensive none
interface borrows an IPv4 address.
Preferred source (Unnumbered Ethernet) Secondary IPv4 address of the donor loopback detail extensive none
address interface that acts as the preferred source address for the unnumbered
Ethernet interface.
Input Filters Names of any input filters applied to this interface. If you specify a detail extensive
precedence value for any filter in a dynamic profile, filter precedence
values appear in parentheses next to all interfaces.
Output Filters Names of any output filters applied to this interface. If you specify a detail extensive
precedence value for any filter in a dynamic profile, filter precedence
values appear in parentheses next to all interfaces.
Mac-Validate Number of MAC address validation failures for packets and bytes. This detail extensive none
Failures field is displayed when MAC address validation is enabled for the logical
interface.
Addresses, Flags Information about the address flags. Possible values are described in the detail extensive none
“Addresses Flags” section under Common Output Fields Description.
648
protocol-family Protocol family configured on the logical interface. If the protocol is inet, brief
the IP address of the interface is also displayed.
Flags Information about the address flag. Possible values are described in the detail extensive none
“Addresses Flags” section under Common Output Fields Description.
Destination IP address of the remote side of the connection. detail extensive none
Local IP address of the logical interface. detail extensive none
Broadcast Broadcast address of the logical interface. detail extensive none
The following table describes the output fields for the show interfaces (10–Gigabit Ethernet) command.
Field Name Field Description Level of

Output
Interface index Index number of the physical interface, which reflects its initialization sequence. detail
extensive none
SNMP ifIndex SNMP index number for the physical interface. detail
extensive none
Generation Unique number for use by Juniper Networks technical support only. detail
extensive
Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback: All levels
Local or Remote.
649
LAN-PHY mode 10-Gigabit Ethernet interface operating in Local Area Network Physical Layer All levels
Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide area links
to use existing Ethernet applications.
WAN-PHY mode 10-Gigabit Ethernet interface operating in Wide Area Network Physical Layer All levels
Device (WAN PHY) mode. WAN PHY allows 10-Gigabit Ethernet wide area
links to use fiber-optic cables and other devices intended for SONET/SDH.
Unidirectional Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled or All levels
Disabled for parent interface; Rx-only or Tx-only for child interfaces.

Device flags Information about the physical device. Possible values are described in the All levels
“Device Flags” section under Common Output Fields Description.
Interface flags Information about the interface. Possible values are described in the “Interface All levels
Link flags Information about the link. Possible values are described in the “Links Flags” All levels
Wavelength (10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM] All levels

interfaces) Displays the configured wavelength, in nanometers (nm).
Frequency (10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated All levels
with the configured wavelength, in terahertz (THz).
CoS queues Number of CoS queues configured. detail

extensive none
Schedulers (Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces only) Number of CoS extensive
schedulers configured.
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail

extensive
650
Current address Configured MAC address. detail

extensive none
Hardware Hardware MAC address. detail

address extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The format detail
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second extensive none
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). The value in None specified
this field also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or the
logical interface level.
Output Rate Output rate in bps and pps. The value in this field also includes the Layer 2 None specified
overhead bytes for egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
Statistics last Time when the statistics for the interface were last set to zero. detail
cleared extensive
Egress account Layer 2 overhead in bytes that is accounted in the interface statistics for egress detail
overhead traffic. extensive
Ingress account Layer 2 overhead in bytes that is accounted in the interface statistics for ingress detail
overhead traffic. extensive
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail
interface. extensive
• Input bytes—Number of bytes received on the interface. The value in this

field also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or
the logical interface level.
• Output bytes—Number of bytes transmitted on the interface. The value in
this field also includes the Layer 2 overhead bytes for egress traffic on
Ethernet interfaces if you enable accounting of Layer 2 overhead at the PIC
level or the logical interface level.
651
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:

• Drops—Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
• Framing errors—Number of packets received with an invalid frame checksum
(FCS).
• Runts—Number of frames received that are smaller than the runt threshold.
• Policed discards—Number of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
• L3 incompletes—Number of incoming packets discarded because they failed
Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with
less than 20 bytes of available IP header is discarded. L3 incomplete errors
can be ignored by configuring the ignore-l3-incompletes statement.
• L2 channel errors—Number of times the software did not find a valid logical
interface for an incoming frame.
• L2 mismatch timeouts—Number of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
• FIFO errors—Number of FIFO errors in the receive direction that are reported
malfunctioning.
652
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
• Carrier transitions—Number of times the interface has gone from down to

up. This number does not normally increment quickly, increasing only when
the cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments
quickly (perhaps once every 10 seconds), the cable, the far-end system, or
the PIC or PIM is malfunctioning.
• Drops—Number of packets dropped by the output queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
• Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC supports
only full-duplex operation, so for Gigabit Ethernet PICs, this number should
always remain 0. If it is nonzero, there is a software bug.
• Aged packets—Number of packets that remained in shared packet SDRAM
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or possibly
malfunctioning hardware.
• FIFO errors—Number of FIFO errors in the send direction as reported by the
ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
• HS link CRC errors—Number of errors on the high-speed links between the
ASICs responsible for handling the router interfaces.
interface.
653
Egress queues Total number of egress queues supported on the specified interface. detail
extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE R,
DPCE 20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a
discrepancy in the output of the show interfaces command because incoming
packets might be counted in the Egress queues section of the output. This
problem occurs on non-enhanced DPCs because the egress queue statistics
are polled from IMQ (Inbound Message Queuing) block of the I-chip. The IMQ
block does not differentiate between ingress and egress WAN traffic; as a
result, the combined statistics are displayed in the egress queue counters on
the Routing Engine. In a simple VPLS scenorio, if there is no MAC entry in
DMAC table (by sending unidirectional traffic), traffic is flooded and the input
traffic is accounted in IMQ. For bidirectional traffic (MAC entry in DMAC table),
if the outgoing interface is on the same I-chip then both ingress and egress
statistics are counted in a combined way. If the outgoing interface is on a
different I-chip or FPC, then only egress statistics are accounted in IMQ. This
behavior is expected with non-enhanced DPCs
Queue counters CoS queue number and its associated user-configured forwarding class name. detail
(Egress) extensive
Ingress queues Total number of ingress queues supported on the specified interface. Displayed extensive
on IQ2 interfaces.
Queue counters CoS queue number and its associated user-configured forwarding class name. extensive
(Ingress) Displayed on IQ2 interfaces.

Active alarms and Ethernet-specific defects that can prevent the interface from passing packets. detail
Active defects When a defect persists for a certain amount of time, it is promoted to an alarm. extensive none
Based on the routing device configuration, an alarm can ring the red or yellow
alarm bell on the routing device, or turn on the red or yellow alarm LED on the
craft interface. These fields can contain the value None or Link.

• Link—Interface has lost its link state, which usually means that the cable is
unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
OTN alarms Active OTN alarms identified on the interface. detail

extensive
654
OTN defects OTN defects received on the interface. detail

extensive
OTN FEC Mode The FECmode configured on the interface. detail

extensive
• efec—Enhanced forward error correction (EFEC) is configured to defect and
correct bit errors.
• gfec—G.709 Forward error correction (GFEC) mode is configured to detect
and correct bit errors.
• none—FEC mode is not configured.
OTN Rate OTN mode. detail

extensive
• fixed-stuff-bytes—Fixed stuff bytes 11.0957 Gbps.
• no-fixed-stuff-bytes—No fixed stuff bytes 11.0491 Gbps.
• pass-through—Enable OTN passthrough mode.
• no-pass-through—Do not enable OTN passthrough mode.
OTN Line Status of the line loopback, if configured for the DWDM OTN PIC. Its value detail
Loopback can be: enabled or disabled. extensive
OTN FEC The forward error correction (FEC) counters for the DWDM OTN PIC. detail
statistics extensive
• Corrected Errors—The count of corrected errors in the last second.
• Corrected Error Ratio—The corrected error ratio in the last 25 seconds. For
example, 1e-7 is 1 error per 10 million bits.
OTN FEC alarms OTN FEC excessive or degraded error alarms triggered on the interface. detail
extensive
• FEC Degrade—OTU FEC Degrade defect.
• FEC Excessive—OTU FEC Excessive Error defect.
OTN OC OTN OC defects triggered on the interface. detail

extensive
• LOS—OC Loss of Signal defect.
• LOF—OC Loss of Frame defect.
• LOM—OC Loss of Multiframe defect.
• Wavelength Lock—OC Wavelength Lock defect.
655
OTN OTU OTN OTU defects detected on the interface detail

extensive
• AIS—OTN AIS alarm.
• BDI—OTN OTU BDI alarm.
• IAE—OTN OTU IAE alarm.
• TTIM—OTN OTU TTIM alarm.
• SF—OTN ODU bit error rate fault alarm.
• SD—OTN ODU bit error rate defect alarm.
• TCA-ES—OTN ODU ES threshold alarm.
• TCA-SES—OTN ODU SES threshold alarm.
• TCA-UAS—OTN ODU UAS threshold alarm.
• TCA-BBE—OTN ODU BBE threshold alarm.
• BIP—OTN ODU BIP threshold alarm.
• BBE—OTN OTU BBE threshold alarm.
• ES—OTN OTU ES threshold alarm.
• SES—OTN OTU SES threshold alarm.
• UAS—OTN OTU UAS threshold alarm.
Received DAPI Destination Access Port Interface (DAPI) from which the packets were received. detail
extensive
Received SAPI Source Access Port Interface (SAPI) from which the packets were received. detail
extensive
Transmitted DAPI Destination Access Port Interface (DAPI) to which the packets were transmitted. detail
extensive
Transmitted SAPI Source Access Port Interface (SAPI) to which the packets were transmitted. detail
extensive
PCS statistics (10-Gigabit Ethernet interfaces) Displays Physical Coding Sublayer (PCS) fault detail
conditions from the WAN PHY or the LAN PHY device. extensive
• Bit errors—The number of seconds during which at least one bit error rate
(BER) occurred while the PCS receiver is operating in normal mode.
• Errored blocks—The number of seconds when at least one errored block
occurred while the PCS receiver is operating in normal mode.
656
MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem, including extensive
the following:
• Total octets and total packets—Total number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
• Unicast packets, Broadcast packets, and Multicast packets—Number of
unicast, broadcast, and multicast packets.
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets (Alignment
Error).
• FIFO error—Number of FIFO errors that are reported by the ASIC on the
PIC. If this value is ever nonzero, the PIC or a cable is probably malfunctioning.
• MAC pause frames—Number of MAC control frames with pause operational
code.
• Oversized frames—Number of frames that exceed 1518 octets.
(excluding framing bits, but including FCS octets), and had either an FCS error
or an alignment error. This definition of jabber is different from the definition
in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2).
These documents define jabber as the condition in which any packet exceeds
20 ms. The allowed range to detect jabber is from 20 ms to 150 ms.
• Fragment frames—Total number of packets that were less than 64 octets in
length (excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. Fragment frames normally increment because
both runts (which are normal occurrences caused by collisions) and noise
hits are counted.
• VLAN tagged frames—Number of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is tagged
or not.
• Code violations—Number of times an event caused the PHY to indicate “Data
reception error” or “invalid data symbol error.”
OTN Received APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 Payload extensive
Overhead Bytes Type: 0x08
OTN Transmitted APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00 Payload extensive
Overhead Bytes Type: 0x08
657
subsystem. The filtering is done by the content-addressable memory (CAM) on
the PIC. The filter examines a packet's source and destination MAC addresses
to determine whether the packet should enter the system or be rejected.
• Input packet count—Number of packets received from the MAC hardware

that the filter processed.
• Input packet rejects—Number of packets that the filter rejected because of
either the source MAC address or the destination MAC address.
• Input DA rejects—Number of packets that the filter rejected because the
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic
is entering the routing device from the far-end system, either there is a bad
ARP entry on the far-end system, or multicast routing is not on and the
far-end system is sending many multicast packets to the local routing device
(which the routing device is rejecting).
• Input SA rejects—Number of packets that the filter rejected because the
source MAC address of the packet is not on the accept list. The value in this
field should increment only if source MAC address filtering has been enabled.
If filtering is enabled, if the value increments quickly, and if the system is not
receiving traffic that it should from the far-end system, it means that the
user-configured source MAC addresses for this interface are incorrect.
• Output packet count—Number of packets that the filter has given to the
MAC hardware.
hardware. Usually, padding is done only on small ARP packets, but some very
small IP packets can also require padding. If this value increments rapidly,
either the system is trying to find an ARP entry for a far-end system that
does not exist or it is misconfigured.
• Output packet error count—Number of packets with an indicated error that
the filter was given to transmit. These packets are usually aged packets or
are the result of a bandwidth problem on the FPC hardware. On a normal
system, the value of this field should not increment.
• CAM destination filters, CAM source filters—Number of entries in the CAM
dedicated to destination and source MAC address filters. There can only be
up to 64 source entries. If source filtering is disabled, which is the default,
the values for these fields should be 0.
PMA PHY (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information: extensive

658
WIS section (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information: extensive

Subfields are:

• LOL—Loss of light
WIS line (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects, extensive
plus counts of specific SONET errors with detailed information.

• State—State of the error. State other than OK indicates a problem.
Subfields are:

659
WIS path (10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects, extensive
plus counts of specific SONET errors with detailed information.

Subfields are:

• PLM-P—Path payload label mismatch
660

information
• Incomplete—Ethernet interface has the speed or link mode configured.
• No autonegotiation—Remote Ethernet interface has the speed or link
mode configured, or does not perform autonegotiation.
• Link partner status—OK when Ethernet interface is connected to a device

that performs autonegotiation and the autonegotiation process is successful.
• Link partner:
• Link mode—Depending on the capability of the attached Ethernet device,
either Full-duplex or Half-duplex.
• Flow control—Types of flow control supported by the remote Ethernet
device. For Fast Ethernet interfaces, the type is None. For Gigabit Ethernet
interfaces, types are Symmetric (link partner supports PAUSE on receive
and transmit), Asymmetric (link partner supports PAUSE on transmit), and
Symmetric/Asymmetric (link partner supports both PAUSE on receive and
transmit or only PAUSE receive).
• Remote fault—Remote fault information from the link partner—Failure
indicates a receive link error. OK indicates that the link partner is receiving.
Negotiation error indicates a negotiation error. Offline indicates that the
link partner is going offline.
• Local resolution—Information from the link partner:

• Flow control—Types of flow control supported by the remote Ethernet
device. For Gigabit Ethernet interfaces, types are Symmetric (link partner
supports PAUSE on receive and transmit), Asymmetric (link partner
supports PAUSE on transmit), and Symmetric/Asymmetric (link partner
supports both PAUSE on receive and transmit or only PAUSE receive).
• Remote fault—Remote fault information. Link OK (no error detected on
receive), Offline (local interface is offline), and Link Failure (link error
detected on receive).
Received path (10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces allow extensive
trace, path trace bytes to be sent inband across the SONET/SDH link. Juniper
Transmitted path Networks and other router manufacturers use these bytes to help diagnose
trace misconfigurations and network errors by setting the transmitted path trace
message so that it contains the system hostname and name of the physical
interface. The received path trace value is the message received from the
routing device at the other end of the fiber. The transmitted path trace value
is the message that this routing device transmits.
661
Packet Information about the configuration of the Packet Forwarding Engine: extensive
Forwarding
Engine • Destination slot—FPC slot number.
configuration

• Buffer usec—Amount of buffer space allocated to the queue, in microseconds.
This value is nonzero only if the buffer size is configured in terms of time.
• Limit—Displayed if rate limiting is configured for the queue. Possible values
are none and exact. If exact is configured, the queue transmits only up to
the configured bandwidth, even if excess bandwidth is available. If none is
configured, the queue transmits beyond the configured bandwidth if
bandwidth is available.
Logical Interface
Index Index number of the logical interface, which reflects its initialization sequence. detail
extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail
extensive none
extensive
Flags Information about the logical interface. Possible values are described in the All levels
“Logical Interface Flags” section under Common Output Fields Description.
662
VLAN-Tag Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN brief detail
tag or for both the outer and inner (In) VLAN tags. extensive none
• pop—The outer VLAN tag of the incoming frame is removed.
• swap—The outer VLAN tag of the incoming frame is overwritten with the
user specified VLAN tag information.
• push-push—Two VLAN tags are pushed in from the incoming frame.
• swap-push—The outer VLAN tag of the incoming frame is replaced by a
user-specified VLAN tag value. A user-specified outer VLAN tag is pushed
in front. The outer tag becomes an inner tag in the final frame.
• swap-swap—Both the inner and the outer VLAN tags of the incoming frame
are replaced by the user specified VLAN tag value.
• pop-swap—The outer VLAN tag of the incoming frame is removed, and the
inner VLAN tag of the incoming frame is replaced by the user-specified VLAN
tag value. The inner tag becomes the outer tag in the final frame.
• pop-pop—Both the outer and inner VLAN tags of the incoming frame are
removed.
Demux: IP demultiplexing (demux) value that appears if this interface is used as the detail
demux underlying interface. The output is one of the following: extensive none
• Source Family Inet

• Destination Family Inet
Protocol Protocol family. Possible values are described in the “Protocol Field” section detail
under Common Output Fields Description. extensive none
MTU Maximum transmission unit size on the logical interface. detail

extensive none
Maximum labels Maximum number of MPLS labels configured for the MPLS protocol family on detail
the logical interface. extensive none
663
Traffic statistics Number and rate of bytes and packets received and transmitted on the specified detail
interface set. extensive
• Input bytes, Output bytes—Number of bytes received and transmitted on

the interface set. The value in this field also includes the Layer 2 overhead
bytes for ingress or egress traffic on Ethernet interfaces if you enable
accounting of Layer 2 overhead at the PIC level or the logical interface level.
• Input packets, Output packets—Number of packets received and transmitted
on the interface set.
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on the extensive
statistics logical interface if IPv6 statistics tracking is enabled.
Local statistics Number and rate of bytes and packets destined to the routing device. extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical
interface egress statistics might not accurately reflect the traffic on the wire
when output shaping is applied. Traffic management output shaping might drop
packets after they are tallied by the Output bytes and Output packets interface
counters. However, correct values display for both of these egress statistics
when per-unit scheduling is enabled for the Gigabit Ethernet IQ2 physical
interface, or when a single logical interface is actively using a shared scheduler.
extensive
Route Table Route table in which the logical interface address is located. For example, 0 detail
refers to the routing table inet.0. extensive none
Flags Information about protocol family flags. Possible values are described in the detail
“Family Flags” section under Common Output Fields Description. extensive
Donor interface (Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface detail
borrows an IPv4 address. extensive none
Preferred source (Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface detail
address that acts as the preferred source address for the unnumbered Ethernet interface. extensive none
Input Filters Names of any input filters applied to this interface. If you specify a precedence detail
value for any filter in a dynamic profile, filter precedence values appear in extensive
parenthesis next to all interfaces.
664
Output Filters Names of any output filters applied to this interface. If you specify a precedence detail
value for any filter in a dynamic profile, filter precedence values appear in extensive
parenthesis next to all interfaces.
Mac-Validate Number of MAC address validation failures for packets and bytes. This field is detail
Failures displayed when MAC address validation is enabled for the logical interface. extensive none
Addresses, Flags Information about the address flags. Possible values are described in the detail
“Addresses Flags” section under Common Output Fields Description. extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, the brief
IP address of the interface is also displayed.
Flags Information about address flag (possible values are described in the “Addresses detail
Flags” section under Common Output Fields Description. extensive none
Destination IP address of the remote side of the connection. detail

extensive none
Local IP address of the logical interface. detail

extensive none
Broadcast Broadcast address of the logical interlace. detail

extensive none
extensive
For Gigabit Ethernet IQ PICs, traffic and MAC statistics output varies. The following table describes the
traffic and MAC statistics for two sample interfaces, each of which is sending traffic in packets of 500
bytes (including 478 bytes for the Layer 3 packet, 18 bytes for the Layer 2 VLAN traffic header, and 4
bytes for cyclic redundancy check [CRC] information). The ge-0/3/0 interface is the inbound physical
interface, and the ge-0/0/0 interface is the outbound physical interface. On both interfaces, traffic is
carried on logical unit .50 (VLAN 50).
665
Table 39: Gigabit and 10 Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Byte and Octet Counts

Interface Type Sample Command Include Comments
Inbound physical interface show interfaces ge-0/3/0 Traffic statistics: The additional 4 bytes are
extensive for the CRC.
Input bytes: 496 bytes per
packet, representing the
Layer 2 packet
MAC statistics:
Received octets: 500 bytes

per packet, representing
the Layer 2 packet + 4
bytes
Inbound logical interface show interfaces Traffic statistics:

ge-0/3/0.50 extensive
Layer 3 packet
Outbound physical show interfaces ge-0/0/0 Traffic statistics: For input bytes, the
interface extensive additional 12 bytes include
6 bytes for the destination
MAC address plus 4 bytes
Layer 3 packet + 12 bytes
for VLAN plus 2 bytes for
MAC statistics: the Ethernet type.
Received octets: 478 bytes

per packet, representing
the Layer 3 packet
Outbound logical interface show interfaces Traffic statistics:

ge-0/0/0.50 extensive
Layer 3 packet
Table 40 on page 666 lists the output fields for the show interfaces command. Output fields are listed in
the approximate order in which they appear.
666
Table 40: show interfaces Output Fields
Physical Interface
Enabled State of the interface. All levels
Interface index Index number of the physical interface, which reflects its initialization detail extensive none
sequence.
Link mode Link mode: Full-duplex or Half-duplex.
BPDU error Bridge protocol data unit (BPDU) error: Detected or None
Loopback Loopback status: Enabled or Disabled. If loopback is enabled, type of All levels
loopback: Local or Remote.

Device flags Information about the physical device. All levels
Interface flags Information about the interface. All levels
Link flags Information about the physical link. All levels

667
Table 40: show interfaces Output Fields (continued)
CoS queues Number of CoS queues configured. detail extensive none
Current address Configured MAC address. detail extensive none
Last flapped Date, time, and how long ago the interface went from down to up. The detail extensive none
format is Last flapped: year-month-day hour:minute:second:timezone
PDT (04:33:20 ago).
Input Rate Input rate in bits per second (bps) and packets per second (pps). None
Output Rate Output rate in bps and pps. None
Active alarms and Ethernet-specific defects that can prevent the interface from passing detail extensive none
Active defects packets. When a defect persists for a certain amount of time, it is
promoted to an alarm. These fields can contain the value None or Link.

• Link—Interface has lost its link state, which usually means that the cable
is unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
cleared
physical interface.

668
Input errors Input errors on the interface. extensive

checksum (FCS).
threshold.
Usually, this field reports protocols that Junos OS does not handle.
• L3 incompletes—Number of incoming packets discarded because they
failed Layer 3 (usually IPv4) sanity checks of the header. For example,
a frame with less than 20 bytes of available IP header is discarded. L3
incomplete errors can be ignored by configuring the
ignore-l3-incompletes .
• L2 channel errors—Number of times the software did not find a valid
logical interface for an incoming frame.
• L2 mismatch timeouts—Number of malformed or short packets that
caused the incoming packet handler to discard the frame as unreadable.
• FIFO errors—Number of FIFO errors in the receive direction that are
reported by the ASIC on the PIC. If this value is ever nonzero, the PIC
is probably malfunctioning.
669
Output errors Output errors on the interface. extensive

• Collisions—Number of Ethernet collisions. The Gigabit Ethernet PIC
supports only full-duplex operation; therefore, for Gigabit Ethernet
PICs, this number must always remain 0. If it is nonzero, there is a
software bug.
• Aged packets—Number of packets that remained in shared packet
SDRAM so long that the system automatically purged them. The value
in this field must never increment. If it does, it is most likely a software
bug or possibly malfunctioning hardware.
• FIFO errors—Number of FIFO errors in the send direction as reported
malfunctioning.
• HS link CRC errors—Number of errors on the high-speed links between
the ASICs responsible for handling the interfaces.
interface.
Ingress queues Total number of ingress queues supported on the specified interface. extensive
Queue counters and CoS queue number and its associated user-configured forwarding class detail extensive
queue number name.

mechanism.
670
MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem, extensive
including the following:
• Total octets and total packets—Total number of octets and packets.

• Unicast packets, Broadcast packets, and Multicast packets—Number
of unicast, broadcast, and multicast packets.
(excluding framing bits, but including FCS octets) of between 64 and
1518 octets, inclusive, and had either a bad FCS with an integral number
of octets (FCS Error) or a bad FCS with a nonintegral number of octets
(Alignment Error).
• FIFO error—Number of FIFO errors that are reported by the ASIC on
the PIC. If this value is ever nonzero, the PIC or a cable is probably
malfunctioning.
• MAC pause frames—Number of MAC control frames with pause
operational code.
• Oversized frames—There are two possible conditions regarding the
number of oversized frames:
• Packet length exceeds 1518 octets, or

• Packet length exceeds MRU
(excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. This definition of jabber is different
from the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section
10.3.1.4 (10BASE2). These documents define jabber as the condition
in which any packet exceeds 20 ms. The allowed range to detect jabber
is from 20 ms to 150 ms.
• Fragment frames—Total number of packets that were less than 64
octets in length (excluding framing bits, but including FCS octets) and
had either an FCS error or an alignment error. Fragment frames normally
increment because both runts (which are normal occurrences caused
by collisions) and noise hits are counted.
• VLAN tagged frames—Number of frames that are VLAN tagged. The
system uses the TPID of 0x8100 in the frame to determine whether a
frame is tagged or not.
• Code violations—Number of times an event caused the PHY to indicate
“Data reception error” or “invalid data symbol error.”
671
subsystem. The filtering is done by the content-addressable memory
(CAM) on the PIC. The filter examines a packet's source and destination
MAC addresses to determine whether the packet should enter the system
or be rejected.
• Input packet count—Number of packets received from the MAC

hardware that the filter processed.
• Input packet rejects—Number of packets that the filter rejected because
of either the source MAC address or the destination MAC address.
• Input DA rejects—Number of packets that the filter rejected because
the destination MAC address of the packet is not on the accept list. It
is normal for this value to increment. When it increments very quickly
and no traffic is entering the device from the far-end system, either
there is a bad ARP entry on the far-end system, or multicast routing is
not on and the far-end system is sending many multicast packets to the
local device (which the router is rejecting).
• Input SA rejects—Number of packets that the filter rejected because
the source MAC address of the packet is not on the accept list. The
value in this field should increment only if source MAC address filtering
has been enabled. If filtering is enabled, if the value increments quickly,
and if the system is not receiving traffic that it should from the far-end
system, it means that the user-configured source MAC addresses for
this interface are incorrect.
• Output packet count—Number of packets that the filter has given to
the MAC hardware.
hardware. Usually, padding is done only on small ARP packets, but some
very small IP packets can also require padding. If this value increments
rapidly, either the system is trying to find an ARP entry for a far-end
system that does not exist or it is misconfigured.
• Output packet error count—Number of packets with an indicated error
that the filter was given to transmit. These packets are usually aged
packets or are the result of a bandwidth problem on the FPC hardware.
On a normal system, the value of this field should not increment.
• CAM destination filters, CAM source filters—Number of entries in the
CAM dedicated to destination and source MAC address filters. There
can only be up to 64 source entries. If source filtering is disabled, which
is the default, the values for these fields must be 0.
672

information
• Incomplete—Ethernet interface has the speed or link mode
configured.
• No autonegotiation—Remote Ethernet interface has the speed or
link mode configured, or does not perform autonegotiation.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive

• Buffer usec—Amount of buffer space allocated to the queue, in
microseconds. This value is nonzero only if the buffer size is configured
in terms of time.
• Limit—Displayed if rate limiting is configured for the queue. Possible
values are none and exact. If exact is configured, the queue transmits
only up to the configured bandwidth, even if excess bandwidth is
available. If none is configured, the queue transmits beyond the
Interface transmit Status of the interface-transmit-statistics configuration: Enabled or detail extensive

statistics Disabled.
Queue counters CoS queue number and its associated user-configured forwarding class detail extensive
(Egress) name.

mechanism.
673
Logical Interface
Index Index number of the logical interface, which reflects its initialization detail extensive none
sequence.
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Flags Information about the logical interface. All levels

on the interface set. The value in this field also includes the Layer 2
overhead bytes for ingress or egress traffic on Ethernet interfaces if
you enable accounting of Layer 2 overhead at the PIC level or the logical
interface level.
Local statistics Number and rate of bytes and packets destined to the device. extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the

logical interface egress statistics might not accurately reflect the traffic
on the wire when output shaping is applied. Traffic management output
shaping might drop packets after they are tallied by the Output bytes and
Output packets interface counters. However, correct values display for
both of these egress statistics when per-unit scheduling is enabled for
the Gigabit Ethernet IQ2 physical interface, or when a single logical
interface is actively using a shared scheduler.
Security Security zones that interface belongs to. extensive
Flow Input statistics Statistics on packets received by flow module. extensive

674
Flow Output Statistics on packets sent by flow module. extensive

statistics
Flow error statistics Statistics on errors in the flow module. extensive

(Packets dropped
due to)
Protocol Protocol family. detail extensive none
MTU Maximum transmission unit size on the logical interface. detail extensive none
Route Table Route table in which the logical interface address is located. For example, detail extensive none
Flags Information about protocol family flags. . detail extensive
Addresses, Flags Information about the address flags.. detail extensive none
Broadcast Broadcast address of the logical interface. detail extensive none
Sample Output Gigabit Ethernet

show interfaces (Gigabit Ethernet)
user@host> show interfaces ge-3/0/2

Link-level type: 52, MTU: 1522, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled
Remote fault: Online
675

Current address: 00:00:5e:00:53:7c, Hardware address: 00:00:5e:00:53:7c
Ingress rate at Packet Forwarding Engine : 0 bps (0 pps)
Ingress drop rate at Packet Forwarding Engine : 0 bps (0 pps)

Flags: SNMP-Traps 0x4000
VLAN-Tag [ 0x8100.512 0x8100.513 ] In(pop-swap 0x8100.530) Out(swap-push
0x8100.512 0x8100.513)
Encapsulation: VLAN-CCC
Egress account overhead: 100
Ingress account overhead: 90
Input packets : 0
Output packets: 0
Protocol ccc, MTU: 1522
Flags: Is-Primary
show interfaces (Gigabit Ethernet on MX Series Routers)


Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, MAC-REWRITE Error: None,
Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Link flags : None
Schedulers : 0
Current address: 00:00:5e:00:53:c0, Hardware address: 00:00:5e:00:53:76
Last flapped : 2008-09-05 16:44:30 PDT (3d 01:04 ago)
676

Flags: Up SNMP-Traps 0x4004000 Encapsulation: ENET2
Input packets : 10232
Protocol inet, MTU: 1500
Addresses, Flags: Is-Preferred Is-Primary
Destination: 203.0.113/24, Local: 203.0.113.1, Broadcast: 203.0.113.255
Protocol inet6, MTU: 1500
Max nh cache: 4, New hold nh limit: 100000, Curr nh cnt: 4, Curr new hold cnt:
4, NH drop cnt: 0
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 2001:db8:/32, Local: 2001:db8::5
Addresses, Flags: Is-Preferred
Destination: 2001:db8:1::/32, Local: 2001:db8:223:9cff:fe9f:3e78
Protocol multiservice, MTU: Unlimited
Flags: Is-Primary
show interfaces (link degrade status)

user@host> show interfaces et-3/0/0
Physical interface: et-3/0/0, Enabled, Physical link is Down

Link-level type: Ethernet, MTU: 1514, MRU: 0, Speed: 100Gbps, BPDU Error: None,
Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled
Device flags : Present Running Down
Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
Link flags : None
Current address: 54:e0:32:23:9d:38, Hardware address: 54:e0:32:23:9d:38
Active alarms : LINK
Active defects : LINK
PCS statistics Seconds
Bit errors 0
Errored blocks 0
Link Degrade* :
Link Monitoring : Enable
677
Link Degrade Set Threshold: : 1E-7

Link Degrade Clear Threshold: : 1E-12
Estimated BER : 1E-7
Link-degrade event : Seconds Count State
782 1 Defect Active
show interfaces extensive (Gigabit Ethernet on MX Series Routers showing interface transmit statistics
configuration)
user@host> show interfaces ge-2/1/2 extensive | match "output|interface"

Output bytes : 240614363944 772721536 bps
Direction : Output
Interface transmit statistics: Enabled
Output bytes : 195560312716 522726272 bps
user@host> show interfaces ge-5/2/0.0 statistics detail
Traffic statistics:
Input bytes : 271524
Input packets: 3664
Input bytes : 0
Input packets: 0
Local statistics:
Input packets: 3664
678

Transit statistics:
show interfaces brief (Gigabit Ethernet)

user@host> show interfaces ge-3/0/2 brief

Link flags : None

VLAN-Tag [ 0x8100.512 0x8100.513 ] In(pop-swap 0x8100.530) Out(swap-push
0x8100.512 0x8100.513)
ccc

show interfaces detail (Gigabit Ethernet)

user@host> show interfaces ge-3/0/2 detail

679

Link flags : None
Current address: 00:00:5e:00:53:7c, Hardware address: 00:00:5e:00:53:7c
Traffic statistics:
0 best-effort 0 0 0
0 best-effort 0 0 0
VLAN-Tag [0x8100.512 0x8100.513 ] In(pop-swap 0x8100.530)
Out(swap-push 0x8100.512 0x8100.513)
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
680
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Protocol ccc, MTU: 1522, Generation: 149, Route table: 0
Flags: Is-Primary

(Generation 139)
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
show interfaces extensive (Gigabit Ethernet IQ2)

user@host> show interfaces ge-7/1/3 extensive

Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled,
681
Link flags : None

Schedulers : 256
Current address: 00:00:5e:00:53:74, Hardware address: 00:00:5e:00:53:74
Last flapped : 2007-11-07 21:31:41 PST (02:03:33 ago)
Traffic statistics:
Input bytes : 38910844056 7952 bps
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input bytes : 38910799145 7952 bps
Input errors:
Output errors:
0 best-effort 418390823 418390823 0
0 best-effort 1031 1031 0
3 network-cont 77872 77872 0
682
Total octets 38910844056 7174605

Unicast packets 408021893366 1026
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0 OTN Received Overhead Bytes:
APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58
Payload Type: 0x08
OTN Transmitted Overhead Bytes:
Payload Type: 0x08
Filter statistics:
Input DA rejects 479
Input SA rejects 0
Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric,
Remote fault: OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Destination slot: 7
CoS information:
Direction : Output
% bps % usec

683
Direction : Input
% bps % usec
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input packets: 9429
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input packets: 9429
Transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Input Filters: F1-ge-3/0/1.0-in, F3-ge-3/0/1.0-in
Output Filters: F2-ge-3/0/1.0-out (53)
Destination: 203.0.113/24, Local: 203.0.113.2, Broadcast: 203.0.113.255,
Generation: 196
684
Protocol multiservice, MTU: Unlimited, Generation: 170, Route table: 0

Flags: Is-Primary
Policer: Input: __default_arp_policer__
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical interface egress statistics
displayed in the show interfaces command output might not accurately reflect the traffic on the wire
when output shaping is applied. Traffic management output shaping might drop packets after they are
tallied by the interface counters. For detailed information, see the description of the logical interface
Transit statistics fields in Table 38 on page 627.
show interfaces (Gigabit Ethernet Unnumbered Interface)


Link flags : None
Current address: 00:00:5e:00:53:f8, Hardware address: 00:00:5e:00:53:f8

Input packets : 0
Output packets: 6
Flags: Unnumbered
show interfaces (ACI Interface Set Configured)

user@host> show interfaces ge-1/0/0.4001
685

Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.4001 ] Encapsulation: PPP-over-
Ethernet
ACI VLAN:
Dynamic Profile: aci-vlan-set-profile
PPPoE:
Dynamic Profile: aci-vlan-pppoe-profile,
Service Name Table: None,
Max Sessions: 32000, Max Sessions VSA Ignore: Off,
Duplicate Protection: On, Short Cycle Protection: Off,
Direct Connect: Off,
AC Name: nbc
Input packets : 9
Output packets: 8
show interfaces (ALI Interface Set)

user@host> show interfaces ge-1/0/0.10
Flags: Up SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.10 ] Encapsulation: ENET2
Line Identity:
Dynamic Profile: ali-set-profile
Circuit-id Remote-id Accept-no-ids
PPPoE:
Dynamic Profile: ali-vlan-pppoe-profile,
AC Name: nbc
Input packets : 9
Output packets: 8
Sample Output Gigabit Ethernet

show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2)
user@host> show interfaces xe-5/0/0 extensive
686
Physical interface: xe-5/0/0, Enabled, Physical link is Up

Link-level type: Ethernet, MTU: 1518, LAN-PHY mode, Speed: 10Gbps, Loopback:
None, Source filtering: Enabled,
Flow control: Enabled
Link flags : None
Schedulers : 1024
Current address: 00:00:5e:00:53:f6, Hardware address: 00:00:5e:00:53:f6
Last flapped : Never
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3
incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Output errors:
FIFO errors: 0, HS link CRC errors: 0,
MTU errors: 0, Resource errors: 0
0 best-effort 81049992 81049992 0
687

0 best-effort 0 0 0
PCS statistics Seconds
Bit errors 0
Errored blocks 0
Total octets 6970332384 0
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
Filter statistics:
Input DA rejects 0
Input SA rejects 0
Destination slot: 5
CoS information:
Direction : Output
% bps % usec
Direction : Input
688
% bps % usec
Logical interface xe-5/0/0.0 (Index 71) (SNMP ifIndex 95) (Generation 195)
Traffic statistics:
Input bytes : 0
Output bytes : 46
Input packets: 0
Output packets: 1
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 46
Input packets: 0
Output packets: 1
Transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Generation: 265
Flags: None
show interfaces extensive (10-Gigabit Ethernet, WAN PHY Mode)

689

Link-level type: Ethernet, MTU: 1514, Speed: 9.294GbpsGbps, Loopback: Disabled
WAN-PHY mode
Source filtering: Disabled, Flow control: Enabled Speed Configuration: Auto
Interface flags: SNMP-Traps 16384
Link flags : None
CoS queues : 4 supported
Current address: 00:00:5e:00:53:9d, Hardware address: 00:00:5e:00:53:9d
Traffic statistics:
Input errors:
HS Link CRC errors: 0, HS Link FIFO overflows: 0,
Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0,
Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0,
Resource errors: 0
0 best-effort 0 0 0
Active alarms : LOL, LOS, LBL
Active defects: LOL, LOS, LBL, SEF, AIS-L, AIS-P
PCS statistics Seconds Count
Bit errors 0 0
Errored blocks 0 0
Total octets 0 0
Total packets 0 0
Unicast packets 0 0
690
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
Filter statistics:
Input DA rejects 0
Input SA rejects 0
PMA PHY: Seconds Count State
PLL lock 0 0 OK
PHY light 63159 1 Light Missing
WIS section:
BIP-B1 0 0
SEF 434430 434438 Defect Active
LOS 434430 1 Defect Active
LOF 434430 1 Defect Active
ES-S 434430
SES-S 434430
SEFS-S 434430
WIS line:
BIP-B2 0 0
REI-L 0 0
RDI-L 0 0 OK
AIS-L 434430 1 Defect Active
BERR-SF 0 0 OK
BERR-SD 0 0 OK
ES-L 434430
SES-L 434430
UAS-L 434420
ES-LFE 0
SES-LFE 0
UAS-LFE 0
WIS path:
BIP-B3 0 0
REI-P 0 0
691
LOP-P 0 0 OK
AIS-P 434430 1 Defect Active
RDI-P 0 0 OK
UNEQ-P 0 0 OK
PLM-P 0 0 OK
ES-P 434430
SES-P 434430
UAS-P 434420
ES-PFE 0
SES-PFE 0
UAS-PFE 0
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace: orissa so-1/0/0
6f 72 69 73 73 61 20 73 6f 2d 31 2f 30 2f 30 00 orissa so-1/0/0.
Destination slot: 1
CoS information:
% bps % bytes
show interfaces extensive (10-Gigabit Ethernet, DWDM OTN PIC)

user@host> show interfaces ge-7/0/0 extensive
Physical interface: ge-7/0/0, Enabled, Physical link is Down

Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
Flow control: Enabled
Link flags : None
Wavelength : 1550.12 nm, Frequency: 193.40 THz
Traffic statistics:
692

Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Output errors:
0 best-effort 0 0 0
3 network-cont
0 best-effort
3 network-control
Total octets 0 0
Total packets 0 0
Unicast packets 0 0
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
Total octets 0 0
Total packets 0 0
693
Unicast packets 0 0
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
OTN alarms : None
OTN defects : None
OTN FEC Mode : GFEC
OTN Rate : Fixed Stuff Bytes 11.0957Gbps
OTN Line Loopback : Enabled
OTN FEC statistics :
Corrected Errors 0
Corrected Error Ratio ( 0 sec average) 0e-0
OTN FEC alarms: Seconds Count State
FEC Degrade 0 0 OK
FEC Excessive 0 0 OK
OTN OC: Seconds Count State
LOS 2 1 OK
LOF 67164 2 Defect Active
LOM 67164 71 Defect Active
Wavelength Lock 0 0 OK
OTN OTU:
AIS 0 0 OK
BDI 65919 4814 Defect Active
IAE 67158 1 Defect Active
TTIM 7 1 OK
SF 67164 2 Defect Active
SD 67164 3 Defect Active
TCA-ES 0 0 OK
TCA-SES 0 0 OK
TCA-UAS 80 40 OK
TCA-BBE 0 0 OK
BIP 0 0 OK
BBE 0 0 OK
ES 0 0 OK
SES 0 0 OK
UAS 587 0 OK
694
Received DAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Received SAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted DAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted SAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
OTN Received Overhead Bytes:
APS/PCC0: 0x02, APS/PCC1: 0x42, APS/PCC2: 0xa2, APS/PCC3: 0x48
Payload Type: 0x03
OTN Transmitted Overhead Bytes:
Payload Type: 0x03
Filter statistics:
Input DA rejects 0
Input SA rejects 0
Destination slot: 7
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 9500000000 95 0 low
none
3 network-control 5 500000000 5 0 low
none
...
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode)

Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, Unidirectional:
Enabled,
695
Loopback: None, Source filtering: Disabled, Flow control: Enabled

...
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Transmit-Only)
user@host> show interfaces xe-7/0/0–tx extensive
Physical interface: xe-7/0/0-tx, Enabled, Physical link is Up

Tx-Only
Link flags : None
Traffic statistics:
Output bytes : 322891152287160 9627472888 bps
...
Filter statistics:
...
Logical interface xe-7/0/0-tx.0 (Index 73) (SNMP ifIndex 138) (Generation 139)
Traffic statistics:
Input bytes : 0
Output bytes : 322891152287160
Input packets: 0
696
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Output bytes : 322891152287160 9627472888 bps
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Generation: 141
Flags: None
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Receive-Only)
user@host> show interfaces xe-7/0/0–rx extensive
Physical interface: xe-7/0/0-rx, Enabled, Physical link is Up

Rx-Only
Link flags : None
Traffic statistics:
697
Input bytes : 322857456303482 9627496104 bps

...
Filter statistics:
Input DA rejects 0
...
Logical interface xe-7/0/0-rx.0 (Index 72) (SNMP ifIndex 120) (Generation 138)
Traffic statistics:
Input bytes : 322857456303482
Output bytes : 0
Input packets: 328775413751
Output packets: 0
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 322857456303482 9627496104 bps
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
698
Generation: 139
Flags: None
Sample Output
Sample Output SRX Gigabit Ethernet

Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, Speed: 1000mbps,
BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
Link flags : None
Last flapped : 2015-05-12 08:36:59 UTC (1w1d 22:42 ago)

Flags: Device-Down SNMP-Traps 0x0 Encapsulation: ENET2
Input packets : 0
Output packets: 0
Security: Zone: public
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Sample Output SRX Gigabit Ethernet

699

Link flags : None

Input packets : 0
Output packets: 0
show interfaces (Gigabit Ethernet for vSRX and vSRX 3.0)


Link-level type: Ethernet, MTU: 1518, LAN-PHY mode, Link-mode: Half-duplex,
Speed: 1000mbps, BPDU Error: None, Loop Detect PDU Error: None, Ethernet-Switching
Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering:
Disabled, Flow control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online
Current address: 00:50:56:93:ef:25, Hardware address: 00:50:56:93:ef:25
Last flapped : 2019-03-29 01:57:45 UTC (00:00:41 ago)
700

show interfaces detail (Gigabit Ethernet)

user@host> show interfaces ge-0/0/1 detail

BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering:
Disabled,
Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online
Link flags : None
Traffic statistics:
0 best-effort 0 0 0
0 best-effort
3 network-control
701
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Flow Statistics :
Flow Input statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Multicast packets : 0
Bytes permitted by policy : 0
Connections established : 0
Flow Output statistics:
Flow error statistics (Packets dropped due to):
Address spoofing: 0
Authentication failed: 0
Incoming NAT errors: 0
Invalid zone received packet: 0
Multiple user authentications: 0
Multiple incoming NAT: 0
No parent for a gate: 0
No one interested in self packets: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No SA for incoming SPI: 0
No tunnel found: 0
No session for a gate: 0
No zone or NULL zone binding 0
702
Policy denied: 0
Security association not active: 0
TCP sequence number out of window: 0
Syn-attack protection: 0
User authentication errors: 0
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255, Generation:
150
show interfaces statistics st0.0 detail

user@host> show interfaces statistics st0.0 detail
Logical interface st0.0 (Index 71) (SNMP ifIndex 609) (Generation 136)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: Secure-Tunnel
Traffic statistics:
Input bytes : 528152756774
Input packets: 11481581669
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Security: Zone: untrust
Allowed host-inbound traffic : any-service bfd bgp dvmrp igmp ldp msdp nhrp
ospf ospf3 pgm pim rip ripng router-discovery rsvp
sap vrrp
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
703

Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 2000280
No tunnel found: 0
Policy denied: 0
Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0,
NH drop cnt: 0
Generation: 155, Route table: 0
show interfaces extensive (Gigabit Ethernet)

user@host> show interfaces ge-0/0/1.0 extensive

704
Link flags : None

Traffic statistics:
Input errors:
Output errors:
0 best-effort 0 0 0
0 best-effort
3 network-control
Total octets 0 0
Total packets 0 0
Unicast packets 0 0
FIFO errors 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
705

Code violations 0
Filter statistics:
Input DA rejects 0
Input SA rejects 0
Negotiation status: Incomplete
Destination slot: 0
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 950000000 95 0 low
none
3 network-control 5 50000000 5 0 low
none
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
706
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Generation: 150
show interfaces terse

user@host> show interfaces terse
707
Interface Admin Link Proto Local Remote

ge-0/0/0 up up
ge-0/0/0.0 up up inet 10.209.4.61/18
gr-0/0/0 up up
ip-0/0/0 up up
st0 up up
st0.1 up ready inet
ls-0/0/0 up up
lt-0/0/0 up up
mt-0/0/0 up up
pd-0/0/0 up up
pe-0/0/0 up up
e3-1/0/0 up up
t3-2/0/0 up up
e1-3/0/0 up up
se-4/0/0 up down
t1-5/0/0 up up
br-6/0/0 up up
dc-6/0/0 up up
dc-6/0/0.32767 up up
bc-6/0/0:1 down up
bc-6/0/0:1.0 up down
dl0 up up
dl0.0 up up inet
dsc up up
gre up up
ipip up up
lo0 up up
lo0.16385 up up inet 10.0.0.1 --> 0/0
10.0.0.16 --> 0/0
lsi up up
mtun up up
pimd up up
pime up up
pp0 up up
show interfaces terse (vSRX and vSRX 3.0)

user@host> show interfaces terse
Interface Admin Link Proto Local Remote

ge-0/0/0 up up
ge-0/0/0.0 up up inet 1.1.65.1/24
ge-0/0/1 up up
708
ge-0/0/2 up up
e-0/0/3 up up
ge-0/0/4 up up
show interfaces controller (Channelized E1 IQ with Logical E1)

user@host> show interfaces controller ce1-1/2/6
Controller Admin Link

ce1-1/2/6 up up
e1-1/2/6 up up
show interfaces controller (Channelized E1 IQ with Logical DS0)

user@host> show interfaces controller ce1-1/2/3
Controller Admin Link

ce1-1/2/3 up up
ds-1/2/3:1 up up
ds-1/2/3:2 up up
show interfaces descriptions

user@host> show interfaces descriptions
Interface Admin Link Description

so-1/0/0 up up M20-3#1
so-2/0/0 up up GSR-12#1
ge-3/0/0 up up SMB-OSPF_Area300
so-3/3/0 up up GSR-13#1
so-3/3/1 up up GSR-13#2
ge-4/0/0 up up T320-7#1
ge-5/0/0 up up T320-7#2
so-7/1/0 up up M160-6#1
ge-8/0/0 up up T320-7#3
ge-9/0/0 up up T320-7#4
so-10/0/0 up up M160-6#2
so-13/0/0 up up M20-3#2
so-14/0/0 up up GSR-12#2
709
ge-15/0/0 up up SMB-OSPF_Area100
ge-15/0/1 up up GSR-13#3
show interfaces destination-class all

user@host> show interfaces destination-class all
Logical interface so-4/0/0.0

Packets Bytes
Destination class (packet-per-second) (bits-per-second)
gold 0 0
( 0) ( 0)
silver 0 0
( 0) ( 0)
Packets Bytes
gold 0 0
( 0) ( 0)
silver 0 0
( 0) ( 0)
show interfaces diagnostics optics

user@host> show interfaces diagnostics optics ge-2/0/0
Physical interface: ge-2/0/0

Laser bias current : 7.408 mA
Laser output power : 0.3500 mW / -4.56 dBm
Module temperature : 23 degrees C / 73 degrees F
Module voltage : 3.3450 V
Receiver signal average optical power : 0.0002 mW / -36.99 dBm
Laser bias current high alarm : Off
Laser bias current low alarm : Off
Laser bias current high warning : Off
Laser bias current low warning : Off
Laser output power high alarm : Off
Laser output power low alarm : Off
Laser output power high warning : Off
Laser output power low warning : Off
Module temperature high alarm : Off
Module temperature low alarm : Off
Module temperature high warning : Off
710
Module temperature low warning : Off

Module voltage high alarm : Off
Module voltage low alarm : Off
Module voltage high warning : Off
Module voltage low warning : Off
Laser rx power high alarm : Off
Laser rx power low alarm : On
Laser rx power high warning : Off
Laser rx power low warning : On
Laser bias current high alarm threshold : 17.000 mA
Laser bias current low alarm threshold : 1.000 mA
Laser bias current high warning threshold : 14.000 mA
Laser bias current low warning threshold : 2.000 mA
Laser output power high alarm threshold : 0.6310 mW / -2.00 dBm
Laser output power low alarm threshold : 0.0670 mW / -11.74 dBm
Laser output power high warning threshold : 0.6310 mW / -2.00 dBm
Laser output power low warning threshold : 0.0790 mW / -11.02 dBm
Module temperature high alarm threshold : 95 degrees C / 203 degrees F
Module temperature low alarm threshold : -25 degrees C / -13 degrees F
Module temperature high warning threshold : 90 degrees C / 194 degrees F
Module temperature low warning threshold : -20 degrees C / -4 degrees F
Module voltage high alarm threshold : 3.900 V
Module voltage low alarm threshold : 2.700 V
Module voltage high warning threshold : 3.700 V
Module voltage low warning threshold : 2.900 V
Laser rx power high alarm threshold : 1.2590 mW / 1.00 dBm
Laser rx power low alarm threshold : 0.0100 mW / -20.00 dBm
Laser rx power high warning threshold : 0.7940 mW / -1.00 dBm
Laser rx power low warning threshold : 0.0158 mW / -18.01 dBm
show interfaces far-end-interval coc12-5/2/0

user@host> show interfaces far-end-interval coc12-5/2/0
Physical interface: coc12-5/2/0, SNMP ifIndex: 121

05:30-current:
ES-L: 1, SES-L: 1, UAS-L: 0
05:15-05:30:
05:00-05:15:
04:45-05:00:
711
04:30-04:45:
04:15-04:30:
04:00-04:15:
...
show interfaces far-end-interval coc1-5/2/1:1

user@host> run show interfaces far-end-interval coc1-5/2/1:1
Physical interface: coc1-5/2/1:1, SNMP ifIndex: 342

05:30-current:
ES-L: 1, SES-L: 1, UAS-L: 0, ES-P: 0, SES-P: 0, UAS-P: 0
05:15-05:30:
05:00-05:15:
04:45-05:00:
04:30-04:45:
04:15-04:30:
04:00-04:15:
show interfaces filters

user@host> show interfaces filters

ge-0/0/0 up up
iso
ge-5/0/0 up up
ge-5/0/0.0 up up any f-any
inet f-inet
multiservice
gr-0/3/0 up up
ip-0/3/0 up up
mt-0/3/0 up up
pd-0/3/0 up up
pe-0/3/0 up up
712
vt-0/3/0 up up
at-1/0/0 up up
at-1/0/0.0 up up inet
iso
at-1/1/0 up down
at-1/1/0.0 up down inet
iso
....
show interfaces flow-statistics (Gigabit Ethernet)

user@host> show interfaces flow-statistics ge-0/0/1.0

Input packets : 5161
Output packets: 83
Security: Zone: zone2
Allowed host-inbound traffic : bootp bfd bgp dns dvmrp ldp msdp nhrp ospf
pgm
pim rip router-discovery rsvp sap vrrp dhcp finger ftp tftp ident-reset http
https ike
netconf ping rlogin rpm rsh snmp snmp-trap ssh telnet traceroute xnm-clear-text
xnm-ssl
lsping
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 2564
Address spoofing: 0
713
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Destination: 203.0.113.1/24, Local: 203.0.113.2, Broadcast: 2.2.2.255
show interfaces interval (Channelized OC12)

user@host> show interfaces interval t3-0/3/0:0
Physical interface: t3-0/3/0:0, SNMP ifIndex: 23

17:43-current:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
17:28-17:43:
SEFS: 0, UAS: 0
17:13-17:28:
SEFS: 0, UAS: 0
16:58-17:13:
SEFS: 0, UAS: 0
16:43-16:58:
...
Interval Total:
LCV: 230, PCV: 1145859, CCV: 455470, LES: 0, PES: 230, PSES: 230,
CES: 230, CSES: 230, SEFS: 230, UAS: 238
714
show interfaces interval (E3)

user@host> show interfaces interval e3-0/3/0
Physical interface: e3-0/3/0, SNMP ifIndex: 23

17:43-current:
SEFS: 0, UAS: 0
17:28-17:43:
SEFS: 0, UAS: 0
17:13-17:28:
SEFS: 0, UAS: 0
16:58-17:13:
SEFS: 0, UAS: 0
16:43-16:58:
....
Interval Total:
LCV: 230, PCV: 1145859, CCV: 455470, LES: 0, PES: 230, PSES: 230,
CES: 230, CSES: 230, SEFS: 230, UAS: 238
show interfaces interval (SONET/SDH) (SRX devices)

user@host> show interfaces interval so-0/1/0
Physical interface: so-0/1/0, SNMP ifIndex: 19

20:02-current:
ES-S: 0, SES-S: 0, SEFS-S: 0, ES-L: 0, SES-L: 0, UAS-L: 0, ES-P: 0,
SES-P: 0, UAS-P: 0
19:47-20:02:
ES-S: 267, SES-S: 267, SEFS-S: 267, ES-L: 267, SES-L: 267, UAS-L: 267,
ES-P: 267, SES-P: 267, UAS-P: 267
19:32-19:47:
SES-P: 56, UAS-P: 46
19:17-19:32:
SES-P: 0, UAS-P: 0
19:02-19:17:
.....
715
show interfaces load-balancing (SRX devices)

user@host> show interfaces load-balancing
Interface State Last change Member count

ams0 Up 1d 00:50 2
ams1 Up 00:00:59 2
show interfaces load-balancing detail (SRX devices)

user@host>show interfaces load-balancing detail
Load-balancing interfaces detail

Interface : ams0
State : Up
Last change : 1d 00:51
Member count : 2
Members :
Interface Weight State
mams-2/0/0 10 Active
mams-2/1/0 10 Active
show interfaces mac-database (All MAC Addresses on a Port SRX devices)

user@host> show interfaces mac-database xe-0/3/3

None, Source filtering: Disabled, Flow control: Enabled
Link flags : None
Logical interface xe-0/3/3.0 (Index 364) (SNMP ifIndex 829)

MAC address Input frames Input bytes Output frames Output bytes
00:00:00:00:00:00 1 56 0 0
00:00:c0:01:01:02 7023810 323095260 0 0
00:00:c0:01:01:03 7023810 323095260 0 0
00:00:c0:01:01:04 7023810 323095260 0 0
00:00:c0:01:01:05 7023810 323095260 0 0
716
00:00:c0:01:01:06 7023810 323095260 0 0

00:00:c0:01:01:07 7023810 323095260 0 0
00:00:c0:01:01:08 7023809 323095214 0 0
00:00:c0:01:01:09 7023809 323095214 0 0
00:00:c0:01:01:0a 7023809 323095214 0 0
00:00:c0:01:01:0b 7023809 323095214 0 0
00:00:c8:01:01:02 30424784 1399540064 37448598 1722635508
00:00:c8:01:01:03 30424784 1399540064 37448598 1722635508
00:00:c8:01:01:04 30424716 1399536936 37448523 1722632058
00:00:c8:01:01:05 30424789 1399540294 37448598 1722635508
00:00:c8:01:01:06 30424788 1399540248 37448597 1722635462
00:00:c8:01:01:07 30424783 1399540018 37448597 1722635462
00:00:c8:01:01:08 30424783 1399540018 37448596 1722635416
00:00:c8:01:01:09 8836796 406492616 8836795 406492570
00:00:c8:01:01:0a 30424712 1399536752 37448521 1722631966
00:00:c8:01:01:0b 30424715 1399536890 37448523 1722632058
Number of MAC addresses : 21
show interfaces mac-database (All MAC Addresses on a Service SRX devices)

user@host> show interfaces mac-database xe-0/3/3

MAC address Input frames Input bytes Output frames Output bytes
00:00:00:00:00:00 1 56 0 0
00:00:c0:01:01:02 7023810 323095260 0 0
00:00:c0:01:01:03 7023810 323095260 0 0
00:00:c0:01:01:04 7023810 323095260 0 0
00:00:c0:01:01:05 7023810 323095260 0 0
00:00:c0:01:01:06 7023810 323095260 0 0
00:00:c0:01:01:07 7023810 323095260 0 0
00:00:c0:01:01:08 7023809 323095214 0 0
00:00:c0:01:01:09 7023809 323095214 0 0
00:00:c0:01:01:0a 7023809 323095214 0 0
00:00:c0:01:01:0b 7023809 323095214 0 0
00:00:c8:01:01:02 31016568 1426762128 38040381 1749857526
00:00:c8:01:01:03 31016568 1426762128 38040382 1749857572
00:00:c8:01:01:04 31016499 1426758954 38040306 1749854076
00:00:c8:01:01:05 31016573 1426762358 38040381 1749857526
00:00:c8:01:01:06 31016573 1426762358 38040381 1749857526
00:00:c8:01:01:07 31016567 1426762082 38040380 1749857480
00:00:c8:01:01:08 31016567 1426762082 38040379 1749857434
717
00:00:c8:01:01:09 9428580 433714680 9428580 433714680

00:00:c8:01:01:0a 31016496 1426758816 38040304 1749853984
00:00:c8:01:01:0b 31016498 1426758908 38040307 1749854122
show interfaces mac-database mac-address

user@host> show interfaces mac-database xe-0/3/3 mac-address (SRX devices) 00:00:c8:01:01:09

None, Source filtering: Disabled, Flow control: Enabled
Link flags : None

MAC address: 00:00:c8:01:01:09, Type: Configured,
Input frames : 4398362
Output frames : 4398360
Policer statistics:
Policer type Discarded frames Discarded bytes
Output aggregate 3992386 183649756
show interfaces mc-ae (SRX devices)

user@host> show interfaces mc-ae ae0 unit 512
Member Links : ae0

Local Status : active
Peer Status : active
Logical Interface : ae0.512
Core Facing Interface : Label Ethernet Interface
ICL-PL : Label Ethernet Interface
show interfaces media (SONET/SDH)

The following example displays the output fields unique to the show interfaces media command for a
SONET interface (with no level of output specified):
718
user@host> show interfaces media so-4/1/2
Physical interface: so-4/1/2, Enabled, Physical link is Up

Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC48,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags : Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 1783 (00:00:00 ago), Output: 1786 (00:00:08 ago)
LCP state: Opened
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Not-configured
SONET alarms : None
SONET defects : None
SONET errors:
BIP-B1: 121, BIP-B2: 916, REI-L: 0, BIP-B3: 137, REI-P: 16747, BIP-BIP2: 0
Received path trace: routerb so-1/1/2
Transmitted path trace: routera so-4/1/2
show interfaces policers (SRX devices)

user@host> show interfaces policers

ge-0/0/0 up up
iso
gr-0/3/0 up up
ip-0/3/0 up up
mt-0/3/0 up up
pd-0/3/0 up up
pe-0/3/0 up up
...
so-2/0/0 up up
so-2/0/0.0 up up inet so-2/0/0.0-in-policer so-2/0/0.0-out-policer
iso
719
so-2/1/0 up down
...
show interfaces policers interface-name (SRX devices)

user@host> show interfaces policers so-2/1/0

so-2/1/0 up down
so-2/1/0.0 up down inet so-2/1/0.0-in-policer so-2/1/0.0-out-policer
iso
inet6
show interfaces queue (SRX devices)
The following truncated example shows the CoS queue sizes for queues 0, 1, and 3. Queue 1 has a queue
buffer size (guaranteed allocated memory) of 9192 bytes.
user@host> show interfaces queue

Queue: 0, Forwarding classes: class0
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
720
High : 0 0 bps
Queue Buffer Usage:
Reserved buffer : 118750000 bytes
Queue-depth bytes :
Current : 0
..
..
..
..
Queue Buffer Usage:
Queue-depth bytes :
Current : 0
..
..
Queued:
..
..
Queue Buffer Usage:
Queue-depth bytes :
Current : 0
..
..
show interfaces redundancy (SRX devices)

user@host> show interfaces redundancy
Interface State Last change Primary Secondary Current status

rsp0 Not present sp-1/0/0 sp-0/2/0 both down
rsp1 On secondary 1d 23:56 sp-1/2/0 sp-0/3/0 primary down
rsp2 On primary 10:10:27 sp-1/3/0 sp-0/2/0 secondary down
rlsq0 On primary 00:06:24 lsq-0/3/0 lsq-1/0/0 both up
show interfaces redundancy (Aggregated Ethernet SRX devices)

user@host> show interfaces redundancy
721
Interface State Last change Primary Secondary Current status

rlsq0 On secondary 00:56:12 lsq-4/0/0 lsq-3/0/0 both up
ae0
ae1
ae2
ae3
ae4
show interfaces redundancy detail (SRX devices)

user@host> show interfaces redundancy detail
Interface : rlsq0
State : On primary
Last change : 00:45:47
Primary : lsq-0/2/0
Secondary : lsq-1/2/0
Current status : both up
Mode : hot-standby
Interface : rlsq0:0
State : On primary
Last change : 00:45:46
Primary : lsq-0/2/0:0
Secondary : lsq-1/2/0:0
Current status : both up
Mode : warm-standby
show interfaces routing brief (SRX devices)

user@host> show interfaces routing brief
Interface State Addresses

so-5/0/3.0 Down ISO enabled
so-5/0/2.0 Up MPLS enabled
ISO enabled
INET 192.168.2.120
INET enabled
so-5/0/1.0 Up MPLS enabled
ISO enabled
INET 192.168.2.130
INET enabled
at-1/0/0.3 Up CCC enabled
722
at-1/0/0.2 Up CCC enabled

at-1/0/0.0 Up ISO enabled
INET 192.168.90.10
INET enabled
lo0.0 Up ISO 47.0005.80ff.f800.0000.0108.0001.1921.6800.5061.00
ISO enabled
INET 127.0.0.1
fxp1.0 Up
fxp0.0 Up INET 192.168.6.90
show interfaces routing detail (SRX devices)

user@host> show interfaces routing detail
so-5/0/3.0
Index: 15, Refcount: 2, State: Up <Broadcast PointToPoint Multicast> Change:<>
Metric: 0, Up/down transitions: 0, Full-duplex
Link layer: HDLC serial line Encapsulation: PPP Bandwidth: 155Mbps
ISO address (null)
State: <Broadcast PointToPoint Multicast> Change: <>
Preference: 0 (120 down), Metric: 0, MTU: 4470 bytes
so-5/0/2.0
Index: 14, Refcount: 7, State: <Up Broadcast PointToPoint Multicast> Change:<>
Metric: 0, Up/down transitions: 0, Full-duplex
Link layer: HDLC serial line Encapsulation: PPP Bandwidth: 155Mbps
MPLS address (null)
State: <Up Broadcast PointToPoint Multicast> Change: <>
ISO address (null)
INET address 192.168.2.120
State: <Up Broadcast PointToPoint Multicast Localup> Change: <>
Local address: 192.168.2.120
Destination: 192.168.2.110/32
INET address (null)
...
show interfaces routing-instance all (SRX devices)

user@host> show interfaces terse routing-instance all
723
Interface Admin Link Proto Local Remote Instance

at-0/0/1 up up inet 10.0.0.1/24
ge-0/0/0.0 up up inet 192.168.4.28/24 sample-a
at-0/1/0.0 up up inet6 fe80::a:0:0:4/64 sample-b
so-0/0/0.0 up up inet 10.0.0.1/32
show interfaces snmp-index (SRX devices)

user@host> show interfaces snmp-index 33
Physical interface: so-2/1/1, Enabled, Physical link is Down

Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC48,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384
Link flags : Keepalives
SONET alarms : LOL, PLL, LOS
SONET defects : LOL, PLL, LOF, LOS, SEF, AIS-L, AIS-P
show interfaces source-class all (SRX devices)

user@host> show interfaces source-class all

Packets Bytes
Source class (packet-per-second) (bits-per-second)
gold 1928095 161959980
( 889) ( 597762)
bronze 0 0
( 0) ( 0)
silver 0 0
( 0) ( 0)
Packets Bytes
Source class (packet-per-second) (bits-per-second)
gold 0 0
( 0) ( 0)
bronze 0 0
724
( 0) ( 0)
silver 116113 9753492
( 939) ( 631616)
show interfaces statistics (Fast Ethernet SRX devices)

user@host> show interfaces fe-1/3/1 statistics
Physical interface: fe-1/3/1, Enabled, Physical link is Up

Description: ford fe-1/3/1
Source filtering: Disabled, Flow control: Enabled
Current address: 00:90:69:93:04:dc, Hardware address: 00:90:69:93:04:dc
Input errors: 0, Output errors: 0
Logical interface fe-1/3/1.0 (Index 69) (SNMP ifIndex 50)
Flags: Is-Primary, DCU, SCU-in
Packets Bytes
silver1 0 0
( 0) ( 0)
silver2 0 0
( 0) ( 0)
silver3 0 0
( 0) ( 0)
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10.27.245/24, Local: 10.27.245.2,
Broadcast: 10.27.245.255
Protocol iso, MTU: 1497
Flags: Is-Primary
725
show interfaces switch-port (SRX devices)

user@host# show interfaces ge-slot/0/0 switch-port port-number
Port 0, Physical link is Up

Speed: 100mbps, Auto-negotiation: Enabled
Statistics: Receive Transmit
Total bytes 28437086 21792250
Multiple collisions 23 10
FIFO/CRC/Align errors 0 0
Oversized frames 0
Runt frames 0
Jabber frames 0
Fragment frames 0
Discarded frames 0
Link partner:
Link mode: Full-duplex, Flow control: None, Remote fault: OK, Link
partner Speed: 100 Mbps
Local resolution:
Flow control: None, Remote fault: Link OK
show interfaces transport pm (SRX devices)

user@host> show interfaces transport pm all current et-0/1/0
Physical interface: et-0/1/0, SNMP ifIndex 515

14:45-current Elapse time:900 Seconds
Near End Suspect Flag:False Reason:None
PM COUNT THRESHOLD TCA-ENABLED TCA-RAISED
OTU-BBE 0 800 No No
OTU-ES 0 135 No No
OTU-SES 0 90 No No
OTU-UAS 427 90 No No
Far End Suspect Flag:True Reason:Unknown
OTU-BBE 0 800 No No
726
OTU-ES 0 135 No No
OTU-SES 0 90 No No
OTU-UAS 0 90 No No
Near End Suspect Flag:False Reason:None
ODU-BBE 0 800 No No
ODU-ES 0 135 No No
ODU-SES 0 90 No No
ODU-UAS 427 90 No No
Far End Suspect Flag:True Reason:Unknown
ODU-BBE 0 800 No No
ODU-ES 0 135 No No
ODU-SES 0 90 No No
ODU-UAS 0 90 No No
FEC Suspect Flag:False Reason:None
FEC-CorrectedErr 2008544300 0 NA NA
FEC-UncorrectedWords 0 0 NA NA
BER Suspect Flag:False Reason:None
PM MIN MAX AVG THRESHOLD TCA-ENABLED
TCA-RAISED
BER 3.6e-5 5.8e-5 3.6e-5 10.0e-3 No
Yes
Physical interface: et-0/1/0, SNMP ifIndex 515
14:45-current
Suspect Flag:True Reason:Object Disabled
PM CURRENT MIN MAX AVG THRESHOLD
TCA-ENABLED TCA-RAISED
(MIN)
(MAX) (MIN) (MAX) (MIN) (MAX)
Lane chromatic dispersion 0 0 0 0 0
0 NA NA NA NA
Lane differential group delay 0 0 0 0 0
0 NA NA NA NA
q Value 120 120 120 120 0
0 NA NA NA NA
SNR 28 28 29 28 0
0 NA NA NA NA
Tx output power(0.01dBm) -5000 -5000 -5000 -5000 -300
-100 No No No No
727
Rx input power(0.01dBm) -3642 -3665 -3626 -3637 -1800

-500 No No No No
Module temperature(Celsius) 46 46 46 46 -5
75 No No No No
Tx laser bias current(0.1mA) 0 0 0 0 0
0 NA NA NA NA
Rx laser bias current(0.1mA) 1270 1270 1270 1270 0
0 NA NA NA NA
Carrier frequency offset(MHz) -186 -186 -186 -186 -5000
5000 No No No No
show security zones (SRX devices)

user@host> show security zones
Functional zone: management

Description: This is the management zone.
Policy configurable: No
Interfaces bound: 1
Interfaces:
ge-0/0/0.0
Security zone: Host
Description: This is the host zone.
Send reset for non-SYN session TCP packets: Off
Policy configurable: Yes
Interfaces bound: 1
Interfaces:
fxp0.0
Security zone: abc
Description: This is the abc zone.
Interfaces bound: 1
Interfaces:
ge-0/0/1.0
Security zone: def
Description: This is the def zone.
Interfaces bound: 1
Interfaces:
ge-0/0/2.0
728
show interfaces (PPPoE)

Syntax
show interfaces pp0.logical

<descriptions>
<media>
<statistics>
Release Information
Description
(M120 routers, M320 routers, and MX Series routers only). Display status information about the PPPoE
interface.
Options
pp0.logical—Display standard status information about the PPPoE interface.
media—(Optional) Display media-specific information about PPPoE interfaces.
statistics—(Optional) Display PPPoE interface statistics.

view

show interfaces (PPPoE) on page 736
show interfaces (PPPoE over Aggregated Ethernet) on page 736
show interfaces brief (PPPoE) on page 737
show interfaces detail (PPPoE) on page 737
show interfaces extensive (PPPoE on M120 and M320 Routers) on page 738
Output Fields
Table 41 on page 729 lists the output fields for the show interfaces (PPPoE) command. Output fields are
listed in the approximate order in which they appear.
729
Table 41: show interfaces (PPPoE) Output Fields
Physical Interface
Interface index Physical interface index number, which reflects its initialization sequence. detail extensive none
Type Physical interface type (PPPoE). All levels
Link-level type Encapsulation on the physical interface (PPPoE). All levels
MTU MTU size on the physical interface. All levels
Clocking Reference clock source. It can be Internal or External. All levels
Device flags Information about the physical device. Possible values are described in All levels
the “Device Flags” section under Common Output Fields Description.
Interface flags Information about the interface. Possible values are described in the All levels
“Interface Flags” section under Common Output Fields Description.
Link type Physical interface link type: full duplex or half duplex. All levels
Link flags Information about the interface. Possible values are described in the “Link All levels
Input rate Input rate in bits per second (bps) and packets per second (pps). None specified
Output rate Output rate in bps and pps. None specified
Physical Info Physical interface information. All levels
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
730
Table 41: show interfaces (PPPoE) Output Fields (continued)
Current address Configured MAC address. detail extensive
Hardware MAC address of the hardware. detail extensive

address
Alternate link Backup address of the link. detail extensive

address
cleared
physical interface.

IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on detail extensive
statistics the physical interface if IPv6 statistics tracking is enabled.
NOTE: These fields include dropped traffic and exception traffic, as those
fields are not separately defined.

731
Input errors Input errors on the interface: extensive
• Errors—Sum of incoming frame aborts and FCS errors.

checksum (FCS).
threshold.
• Giants—Number of frames received that are larger than the giant
threshold.
Usually, this field reports protocols that the Junos OS does not handle.
• Resource errors—Sum of B chip Tx drops and IXP Tx net transmit drops.
• Carrier transitions —Number of times the interface has gone from down
transitions increments quickly (perhaps once every 10 seconds), then
the cable, the far-end system, or the PIM is malfunctioning.
interface.
• Resource errors—Sum of B chip Tx drops and IXP Tx net transmit drops.
Logical Interface
Index Logical interface index number (which reflects its initialization sequence). detail extensive none
SNMP ifIndex Logical interface SNMP interface index number. detail extensive none
732
Flags Information about the logical interface. Possible values are described in All levels
the “Logical Interface Flags” section under Common Output Fields
Description.
Encapsulation Type of encapsulation configured on the logical interface. All levels
PPP parameters PPP status: detail
• LCP restart timer—Length of time (in milliseconds) between successive

Link Control Protocol (LCP) configuration requests.
• NCP restart timer—Length of time (in milliseconds) between successive
Network Control Protocol (NCP) configuration requests.
PPPoE PPPoE status: All levels
• State—State of the logical interface (up or down).

• Session ID—PPPoE session ID.
• Service name—Type of service required. Can be used to indicate an
Internet service provider (ISP) name or a class or quality of service.
• Configured AC name—Configured access concentrator name.
• Auto-reconnect timeout—Time after which to try to reconnect after a
PPPoE session is terminated, in seconds.
• Idle Timeout—Length of time (in seconds) that a connection can be idle
before disconnecting.
• Underlying interface—Interface on which PPPoE is running.
Link Name of the physical interfaces for member links in an aggregated Ethernet All levels
bundle for a PPPoE over aggregated Ethernet configuration. PPPoE traffic
goes out on these interfaces.
Traffic statistics Total number of bytes and packets received and transmitted on the logical detail extensive
interface. These statistics are the sum of the local and transit statistics.
When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. This counter usually takes
less than 1 second to stabilize.
733
IPv6 transit Number of IPv6 transit bytes and packets received and transmitted on detail extensive
NOTE: The packet and byte counts in these fields include traffic that is
dropped and does not leave the router.

Local statistics Statistics for traffic received from and transmitted to the Routing Engine. detail extensive
When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. This counter usually takes
less than 1 second to stabilize.
Transit statistics Statistics for traffic transiting the router. When a burst of traffic is detail extensive
received, the value in the output packet rate field might briefly exceed
the peak cell rate. This counter usually takes less than 1 second to stabilize.
Keepalive (PPP and HDLC) Configured settings for keepalives. detail extensive
settings
• interval seconds—The time in seconds between successive keepalive
requests. The range is 10 seconds through 32,767 seconds, with a
default of 10 seconds.
• down-countnumber—The number of keepalive packets a destination
must fail to receive before the network takes a link down. The range is
1 through 255, with a default of 3.
• up-count number—The number of keepalive packets a destination must
receive to change a link’s status from down to up. The range is 1 through
255, with a default of 1.
734
Keepalive (PPP and HDLC) Information about keepalive packets. detail extensive
statistics
• Input—Number of keepalive packets received by PPP.
• (last seen 00:00:00 ago)—Time the last keepalive packet was received,
in the format hh:mm:ss.
• Output—Number of keepalive packets sent by PPP and how long ago

the last keepalive packets were sent and received.
• (last seen 00:00:00 ago)—Time the last keepalive packet was sent,
in the format hh:mm:ss.
(MX Series routers with MPCs/MICs) When an MX Series router with

MPCs/MICs is using PPP fast keepalive for a PPP link, the display does
not include the number of keepalive packets received or sent, or the
amount of time since the router received or sent the last keepalive packet.
Input packets Number of packets received on the logical interface. None specified
Output packets Number of packets transmitted on the logical interface. None specified
LCP state (PPP) Link Control Protocol state. none detail extensive
• Conf-ack-received—Acknowledgement was received.

• Conf-ack-sent—Acknowledgement was sent.
• Conf-req-sent—Request was sent.
• Down—LCP negotiation is incomplete (not yet completed or has failed).
• Not-configured—LCP is not configured on the interface.
• Opened—LCP negotiation is successful.
NCP state (PPP) Network Control Protocol state. detail extensive none
• Conf-ack-received—Acknowledgement was received.

• Conf-ack-sent—Acknowledgement was sent.
• Conf-req-sent—Request was sent.
• Down—NCP negotiation is incomplete (not yet completed or has failed).
• Not-configured—NCP is not configured on the interface.
• Opened—NCP negotiation is successful.
735
CHAP state (PPP) Displays the state of the Challenge Handshake Authentication none detail extensive
Protocol (CHAP) during its transaction.
• Chap-Chal-received—Challenge was received but response not yet

sent.
• Chap-Chal-sent—Challenge was sent.
• Chap-Resp-received—Response was received for the challenge sent,
but CHAP has not yet moved into the Success state. (Most likely with
RADIUS authentication.)
• Chap-Resp-sent—Response was sent for the challenge received.
• Closed—CHAP authentication is incomplete.
• Failure—CHAP authentication failed.
• Not-configured—CHAP is not configured on the interface.
• Success—CHAP authentication was successful.
Protocol Protocol family configured on the logical interface. detail extensive none
protocol-family Protocol family configured on the logical interface. If the protocol is inet, brief
the IP address of the interface is also displayed.
MTU MTU size on the logical interface. detail extensive none
Route table Routing table in which the logical interface address is located. For example, detail extensive none
Flags Information about the protocol family flags. Possible values are described detail extensive none
in the “Family Flags” section under Common Output Fields Description.
Addresses, Flags Information about the addresses configured for the protocol family. detail extensive none
Possible values are described in the “Addresses Flags” section under
Common Output Fields Description.
Broadcast Broadcast address. detail extensive none

736
Sample Output
show interfaces (PPPoE)
user@host> show interfaces pp0
Physical interface: pp0, Enabled, Physical link is Up

Type: PPPoE, Link-level type: PPPoE, MTU: 1532
Link type : Full-Duplex
Link flags : None
Logical interface pp0.0 (Index 72) (SNMP ifIndex 72)

Flags: Hardware-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionDown, Session ID: None,
Service name: None, Configured AC name: sapphire,
Auto-reconnect timeout: 100 seconds, Idle timeout: Never,
Underlying interface: at-5/0/0.0 (Index 70)
Input packets : 0
Output packets: 0
LCP state: Not-configured
CHAP state: Closed
Flags: User-MTU, Negotiate-Address
show interfaces (PPPoE over Aggregated Ethernet)

user@host> show interfaces pp0.1073773821
Logical interface pp0.1073773821 (Index 80) (SNMP ifIndex 32584)

Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionUp, Session ID: 1,
Session AC name: alcor, Remote MAC address: 00:00:5e:00:53:01,
Underlying interface: demux0.100 (Index 88)
Link:
ge-1/0/0.32767
737
ge-1/0/1.32767
Input packets : 6
Output packets: 6
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Success
Addresses, Flags: Is-Primary
Local: 203.0.113.1
show interfaces brief (PPPoE)

user@host> show interfaces pp0 brief

Type: PPPoE, Link-level type: PPPoE, MTU: 1532, Speed: Unspecified
Logical interface pp0.0

PPPoE:
inet
show interfaces detail (PPPoE)

user@host> show interfaces pp0 detail

Link flags : None
Physical info : Unspecified
738

Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Traffic statistics:
Logical interface pp0.0 (Index 72) (SNMP ifIndex 72) (Generation 14)
PPPoE:
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
LCP state: Not-configured
CHAP state: Closed
Flags: User-MTU, Negotiate-Address
show interfaces extensive (PPPoE on M120 and M320 Routers)

user@host> show interfaces pp0 extensive

739

Link flags : None
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Logical interface pp0.0 (Index 69) (SNMP ifIndex 96) (Generation 194)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionUp, Session ID: 26,
Session AC name: None, AC MAC address: 00:00:5e:00:53:12,
Service name: None, Configured AC name: None,
Auto-reconnect timeout: Never, Idle timeout: Never,
Underlying interface: ge-3/0/1.0 (Index 67)
Traffic statistics:
Input bytes : 252
Output bytes : 296
Input packets: 7
Output packets: 8
Input bytes : 0
Output bytes : 0
740
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 252
Output bytes : 296
Input packets: 7
Output packets: 8
Transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 1 (last seen 00:00:00 ago)
Output: 1 (last sent 00:00:03 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Closed
Flags: None
Destination: 203.0.113.2, Local: 203.0.113.1, Broadcast: Unspecified,
Generation: 206
741
show interfaces demux0 (Demux Interfaces)

Syntax
show interfaces demux0.logical-interface-number

<descriptions>
<media>
<statistics>
Release Information
Command introduced in Junos OS Release 9.0.
Description
(MX Series and M Series routers only) Display status information about the specified demux interface.
Options
none—Display standard information about the specified demux interface.

view

show interfaces demux0 (Demux) on page 749
show interfaces demux0 (PPPoE over Aggregated Ethernet) on page 750
show interfaces demux0 extensive (Targeted Distribution for Aggregated Ethernet Links) on page 751
show interfaces demux0 (ACI Interface Set Configured) on page 751
Output Fields
742
Table 42 on page 742 lists the output fields for the show interfaces demux0 (Demux Interfaces) command.
Table 42: show interfaces demux0 (Demux Interfaces) Output Fields
Physical Interface
Physical interface Name of the physical interface. brief detail

extensive none
Interface index Index number of the physical interface, which reflects its initialization brief detail
sequence. extensive none
Enabled State of the interface. Possible values are described in the “Enabled Field” brief detail
section under Common Output Fields Description. extensive none
Physical link Status of the physical link (Up or Down). detail extensive
none
Admin Administrative state of the interface (Up or Down). terse
Interface index Index number of the physical interface, which reflects its initialization detail extensive
sequence. none
Link Status of the physical link (Up or Down). terse
Targeting Status of aggregated Ethernet links that are configured with targeted extensive
summary distribution (primary or backup)
Bandwidth Bandwidth allocated to the aggregated Ethernet links that are configured extensive
with targeted distribution.
Proto Protocol family configured on the interface. terse
SNMP ifIndex SNMP index number for the physical interface. detail extensive
none
Type Type of interface. Software-Pseudo indicates a standard software interface brief detail
with no associated hardware device. extensive none
Link-level type Encapsulation being used on the physical interface. brief detail
extensive
743
Table 42: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
MTU Maximum transmission unit size on the physical interface. brief detail
extensive
Clocking Reference clock source: Internal (1) or External (2). brief detail
extensive
Speed Speed at which the interface is running. brief detail

extensive
Device flags Information about the physical device. Possible values are described in brief detail
the “Device Flags” section under Common Output Fields Description. extensive none
Interface flags Information about the interface. Possible values are described in the brief detail
“Interface Flags” section under Common Output Fields Description. extensive none
Link type Data transmission type. detail extensive

none
Link flags Information about the link. Possible values are described in the “Link Flags” detail extensive
section under Common Output Fields Description. none
Physical info Information about the physical interface. detail extensive
Hold-times Current interface hold-time up and hold-time down, in milliseconds. detail extensive
Current address Configured MAC address. detail extensive
Hardware Hardware MAC address. detail extensive

address
Alternate link Backup address of the link. detail extensive

address
Last flapped Date, time, and how long ago the interface went from down to up. The detail extensive
format is Last flapped: year-month-day hour:minute:second:timezone none
PDT (04:33:20 ago).
cleared
744
physical interface.

• IPv6 transit statistics—Number of IPv6 transit bytes and packets
received and transmitted on the physical interface if IPv6 statistics
tracking is enabled.
NOTE: These fields include dropped traffic and exception traffic, as

those fields are not separately defined.
• Input bytes—Number of bytes received on the interface

Input errors Input errors on the interface whose definitions are as follows: extensive

checksum (FCS).
threshold.
• Giants—Number of frames received that are larger than the giant packet
threshold.
Usually, this field reports protocols that the Junos OS does not handle.
Input Rate Input rate in bits per second (bps) and packets per second (pps). none
745

interface.
Output Rate Output rate in bps and pps. none
Logical Interface
Logical interface Name of the logical interface. brief detail

extensive none
Index Index number of the logical interface, which reflects its initialization detail extensive
sequence. none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive
none
Flags Information about the logical interface. Possible values are described in brief detail
the “Logical Interface Flags” section under Common Output Fields extensive none
Description.
Encapsulation Encapsulation on the logical interface. brief extensive none
ACI VLAN: Name of the dynamic profile that defines the agent circuit identifier (ACI) brief detail
Dynamic Profile interface set. If configured, the ACI interface set enables the underlying extensive none
demux interface to create dynamic VLAN subscriber interfaces based on
ACI information.
746
Demux Specific IP demultiplexing (demux) values: detail extensive

none
• Underlying interface—The underlying interface that the demux interface
uses.
• Index—Index number of the logical interface.
• Family—Protocol family configured on the logical interface.
• Source prefixes, total—Total number of source prefixes for the
underlying interface.
• Destination prefixes, total—Total number of destination prefixes for
the underlying interface.
• Prefix—inet family prefix.
protocol-family Protocol family configured on the logical interface. brief

on the interface set.
• IPv6 transit statistics—Number of IPv6 transit bytes and packets
received and transmitted on the logical interface if IPv6 statistics
tracking is enabled.
NOTE: The packet and byte counts in these fields include traffic that
is dropped and does not leave the router.

Local statistics Number of transit bytes and packets received and transmitted on the local detail extensive
interface.

747
Transit statistics Number and rate of bytes and packets transiting the switch. detail extensive

IPv6 Transit Number of IPv6 transit bytes and packets received and transmitted on detail extensive

Input packets Number of packets received on the interface. none
Output packets Number of packets transmitted on the interface. none
Protocol Protocol family. Possible values are described in the “Protocol Field” detail extensive
section under Common Output Fields Description. none
MTU Maximum transmission unit size on the logical interface. detail extensive
none
Maximum labels Maximum number of MPLS labels configured for the MPLS protocol family detail extensive
on the logical interface. none
Route table Route table in which the logical interface address is located. For example, detail extensive
Flags Information about protocol family flags. Possible values are described in detail extensive
the “Family Flags” section under Common Output Fields Description. none
748
Mac-Validate Number of MAC address validation failures for packets and bytes. This detail extensive
Failures field is displayed when MAC address validation is enabled for the logical none
interface.
Addresses, Flags Information about the address flags. Possible values are described in the detail extensive
“Addresses Flags” section under Common Output Fields Description. none
Destination IP address of the remote side of the connection. detail extensive

statistics none
Local IP address of the logical interface. detail extensive

terse none
Remote IP address of the remote interface. terse
Broadcast Broadcast address of the logical interlace. detail extensive

none
Link Name of the physical interfaces for member links in an aggregated Ethernet detail extensive
bundle for a PPPoE over aggregated Ethernet configuration. PPPoE traffic none
goes out on these interfaces.
Dynamic-profile Name of the PPPoE dynamic profile assigned to the underlying interface. detail extensive
none
Service Name Name of the PPPoE service name table assigned to the PPPoE underlying detail extensive
Table interface. none
Max Sessions Maximum number of dynamic PPPoE logical interfaces that the router detail extensive
can activate on the underlying interface. none
Duplicate State of duplicate protection: On or Off. Duplicate protection prevents detail extensive
Protection the activation of another dynamic PPPoE logical interface on the same none
underlying interface when a dynamic PPPoE logical interface for a client
with the same MAC address is already active on that interface.
Direct Connect State of the configuration to ignore DSL Forum VSAs: On or Off. When detail extensive
configured, the router ignores any of these VSAs received from a directly none
connected CPE device on the interface.
749
AC Name Name of the access concentrator. detail extensive

none
Sample Output
show interfaces demux0 (Demux)
user@host> show interfaces demux0
Physical interface: demux0, Enabled, Physical link is Up

Type: Software-Pseudo, Link-level type: Unspecified, MTU: 9192, Clocking: 1,
Speed: Unspecified
Link flags : None
Last flapped : Never
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
750
Logical interface demux0.0 (Index 87) (SNMP ifIndex 84) (Generation 312)
Demux:
Underlying interface: ge-2/0/1.0 (Index 74)
Family Inet Source prefixes, total 1
Prefix: 203.0.113/24
Traffic statistics:
Input bytes : 0
Output bytes : 1554
Input packets: 0
Output packets: 37
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 1554
Input packets: 0
Output packets: 37
Transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Generation: 434
show interfaces demux0 (PPPoE over Aggregated Ethernet)

user@host> show interfaces demux0.100
751

Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ]
Encapsulation: ENET2
Demux:
Link:
ge-1/0/0
ge-1/1/0
Input packets : 0
Output packets: 0
Protocol pppoe
Dynamic Profile: pppoe-profile,
Service Name Table: service-table1,
Max Sessions: 100, Duplicate Protection: On,
AC Name: pppoe-server-1
show interfaces demux0 extensive (Targeted Distribution for Aggregated Ethernet Links)
user@host> show interfaces demux0.1073741824 extensive
Logical interface demux0.1073741824 (Index 75) (SNMP ifIndex 558) (Generation

346)
Demux:
Link:
ge-1/0/0
ge-1/1/0
ge-2/0/7
ge-2/0/8
Targeting summary:
ge-1/1/0, primary, Physical link is Up
ge-2/0/8, backup, Physical link is Up
Bandwidth: 1000mbps
show interfaces demux0 (ACI Interface Set Configured)

user@host> show interfaces demux0.1073741827

Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1802 0x8100.302 ] Encapsulation:
752
ENET2
Demux: Source Family Inet
ACI VLAN:
Dynamic Profile: aci-vlan-set-profile
Demux:
Underlying interface: ge-1/0/0 (Index 138)
Input packets : 18
Output packets: 16
Flags: Sendbcast-pkt-to-re, Unnumbered
Addresses, Flags: Primary Is-Default Is-Primary
Local: 203.0.113.119
Protocol pppoe
Dynamic Profile: aci-vlan-pppoe-profile,
AC Name: nbc
753
show interfaces queue

Syntax
show interfaces queue

<aggregate | remaining-traffic>
<both-ingress-egress>
<egress>
<forwarding-class forwarding-class>
<ingress>
< interface-name>
<l2-statistics>
<buffer-occupancy>
Release Information
both-ingress-egress, egress, and ingress options introduced in Junos OS Release 7.6.
Command introduced in Junos OS Release 9.0 for EX Series.
l2-statistics option introduced in Junos OS Release 12.1.
buffer-occupancy statement introduced in Junos OS Release 19.1R1 for QFX5000 Series switches.
Description
Display class-of-service (CoS) queue information for physical interfaces.
Options
none—Show detailed CoS queue statistics for all physical interfaces.
aggregate—(Optional) Display the aggregated queuing statistics of all logical interfaces that have
traffic-control profiles configured. (Not on the QFX Series.)
both-ingress-egress—(Optional) On Gigabit Ethernet Intelligent Queuing 2 (IQ2) PICs, display both ingress
and egress queue statistics. (Not on the QFX Series.)
egress—(Optional) Display egress queue statistics.
forwarding-class forwarding-class—(Optional) Forwarding class name for this queue. Shows detailed CoS
statistics for the queue associated with the specified forwarding class.
ingress—(Optional) On Gigabit Ethernet IQ2 PICs, display ingress queue statistics. (Not on the QFX Series.)
interface-name—(Optional) Show detailed CoS queue statistics for the specified interface.
l2-statistics—(Optional) Display Layer 2 statistics for MLPPP, FRF.15, and FRF.16 bundles
754
buffer-occupancy—Displays the peak buffer occupancy for each queue while buffer-monitor-enable is
enabled at the [edit chassis fpc slot-number traffic-manager] hierarchy level.
remaining-traffic—(Optional) Display the remaining-traffic queue statistics of all logical interfaces that
have traffic-control profiles configured.
Overhead for Layer 2 Statistics
Transmitted packets and transmitted byte counts are displayed for the Layer 2 level with the addition
of encapsulation overheads applied for fragmentation, as shown in Table 43 on page 754. Others
counters, such as packets and bytes queued (input) and drop counters, are displayed at the Layer 3
level. In the case of link fragmentation and interleaving (LFI) for which fragmentation is not applied,
corresponding Layer 2 overheads are added, as shown in Table 43 on page 754.
Table 43: Layer 2 Overhead and Transmitted Packets or Byte Counts
Protocol Fragmentation LFI
First fragmentation Second to n fragmentations
Bytes Bytes
MLPPP (Long) 13 12 8
MLPPP (short) 11 10 8
MLFR (FRF15) 12 10 8
MFR (FRF16) 10 8 -
MCMLPPP(Long) 13 12 -
MCMLPPP(Short) 11 10 -
Layer 2 Statistics—Fragmentation Overhead Calculation
MLPPP/MC-MLPPP Overhead details:

===============================
Fragment 1:
Outer PPP header : 4 bytes

755
Long or short sequence MLPPP header : 4 bytes or 2 bytes

Inner PPP header : 1 byte
HDLC flag and FCS bytes : 4 bytes
Fragments 2 .. n :

Long or short sequence MLPPP header : 4 bytes or 2 bytes
HDLC flag and FCS bytes : 4 bytes
MLFR (FRF15) Overhead details:

=============================
Fragment 1:
Framerelay header : 2 bytes
Control,NLPID : 2 bytes
Fragmentaion header : 2 bytes
Inner proto : 2 bytes
HDLC flag and FCS : 4 bytes
Fragments 2 ...n :

MFR (FRF16) Overhead details:

==============================
Fragment 1:
Inner proto : 2 bytes
Fragments 2 ...n :
756
Overhead with LFI
MLPPP(Long & short sequence):

============================
MLFR (FRF15):
=============
The following examples show overhead for different cases:
• A 1000-byte packet is sent to a mlppp bundle without any fragmentation. At the Layer 2 level, bytes
transmitted is 1013 in 1 packet. This overhead is for MLPPP long sequence encap.
• A 1000-byte packet is sent to a mlppp bundle with a fragment threshold of 250byte. At the Layer
2 level, bytes transmitted is 1061 bytes in 5 packets.
• A 1000-byte LFI packet is sent to an mlppp bundle. At the Layer 2 level, bytes transmitted is 1008
in 1 packet.
remaining-traffic—(Optional) Display the queuing statistics of all logical interfaces that do not have
traffic-control profiles configured. (Not on the QFX Series.)
Additional Information
For rate-limited interfaces hosted on Modular Interface Cards (MICs), Modular Port Concentrators (MPCs),
or Enhanced Queuing DPCs, rate-limit packet-drop operations occur before packets are queued for
transmission scheduling. For such interfaces, the statistics for queued traffic do not include the packets
that have already been dropped due to rate limiting, and consequently the displayed statistics for queued
traffic are the same as the displayed statistics for transmitted traffic.
NOTE: For rate-limited interfaces hosted on other types of hardware, rate-limit packet-drop
operations occur after packets are queued for transmission scheduling. For these other interface
types, the statistics for queued traffic include the packets that are later dropped due to rate
limiting, and consequently the displayed statistics for queued traffic equals the sum of the
statistics for transmitted and rate-limited traffic.
On M Series routers (except for the M320 and M120 routers), this command is valid only for a PIC installed
on an enhanced Flexible PIC Concentrator (FPC).
757
Queue statistics for aggregated interfaces are supported on the M Series and T Series routers only. Statistics
for an aggregated interface are the summation of the queue statistics of the child links of that aggregated
interface. You can view the statistics for a child interface by using the show interfaces statistics command
for that child interface.
When you configure tricolor marking on a 10-port 1-Gigabit Ethernet PIC, for queues 6 and 7 only, the
output does not display the number of queued bytes and packets, or the number of bytes and packets
dropped because of RED. If you do not configure tricolor marking on the interface, these statistics are
available for all queues.
For the 4-port Channelized OC12 IQE PIC and 1-port Channelized OC48 IQE PIC, the Packet Forwarding
Engine Chassis Queues field represents traffic bound for a particular physical interface on the PIC. For all
other PICs, the Packet Forwarding Engine Chassis Queues field represents the total traffic bound for the
PIC.
For Gigabit Ethernet IQ2 PICs, the show interfaces queue command output does not display the number
of tail-dropped packets. This limitation does not apply to Packet Forwarding Engine chassis queues.
When fragmentation occurs on the egress interface, the first set of packet counters shows the
postfragmentation values. The second set of packet counters (under the Packet Forwarding Engine Chassis
Queues field) shows the prefragmentation values.
The behavior of the egress queues for the Routing Engine-Generated Traffic is not same as the configured
queue for MLPPP and MFR configurations.
For related CoS operational mode commands, see the CLI Explorer.

view
Release Description
18.3R1 Starting with Junos OS 18.3R1, the Tail-dropped packets counter is supported on PTX
Series Packet Transport Routers.
16.1 Starting with Junos OS Release 16.1, Last-packet enqueued output field is introduced.
Monitoring Interface Status and Traffic

Monitoring Interfaces That Have CoS Components
Defining CoS Schedulers and Scheduler Maps (CLI Procedure)
758
Configuring CoS Traffic Classification for Ingress Queuing on Oversubscribed Ports on EX8200 Line Cards
(CLI Procedure)
ATM Interfaces User Guide for Routing Devices
Layer 2 Bridging, Address Learning, and Forwarding User Guide

show interfaces queue (Rate-Limited Interface on a Gigabit Ethernet MIC in an MPC) on page 766
show interfaces queue (Aggregated Ethernet on a T320 Router) on page 767
show interfaces queue (Gigabit Ethernet on a T640 Router) on page 769
show interfaces queue aggregate (Gigabit Ethernet Enhanced DPC) on page 770
show interfaces queue (Gigabit Ethernet IQ2 PIC) on page 775
show interfaces queue both-ingress-egress (Gigabit Ethernet IQ2 PIC) on page 779
show interfaces queue ingress (Gigabit Ethernet IQ2 PIC) on page 782
show interfaces queue egress (Gigabit Ethernet IQ2 PIC) on page 784
show interfaces queue remaining-traffic (Gigabit Ethernet Enhanced DPC) on page 786
show interfaces queue (Channelized OC12 IQE Type 3 PIC in SONET Mode) on page 789
show interfaces queue (QFX Series) on page 803
show interfaces queue l2-statistics (lsq interface) on page 804
show interfaces queue lsq (lsq-ifd) on page 805
show interfaces queue (Aggregated Ethernet on a MX series Router) on page 807
show interfaces queue ge-0/0/0 (EX2200 Switch) on page 810
show interfaces queue xe-6/0/39 (Line Card with Oversubscribed Ports in an EX8200 Switch) on page 811
show interfaces queue xe-0/0/2 buffer-occupancy (QFX5000 Series switch) on page 814
Output Fields
Table 44 on page 758 lists the output fields for the show interfaces queue command. Output fields are
listed in the approximate order in which they appear.
Table 44: show interfaces queue Output Fields
Physical interface Name of the physical interface.
Enabled State of the interface. Possible values are described in the “Enabled Field” section under
Common Output Fields Description.
Interface index Physical interface's index number, which reflects its initialization sequence.
SNMP ifIndex SNMP index number for the interface.
Forwarding classes Total number of forwarding classes supported on the specified interface.
supported
759
Table 44: show interfaces queue Output Fields (continued)
Forwarding classes in Total number of forwarding classes in use on the specified interface.
use
Ingress queues On Gigabit Ethernet IQ2 PICs only, total number of ingress queues supported on the specified
supported interface.
Ingress queues in use On Gigabit Ethernet IQ2 PICs only, total number of ingress queues in use on the specified
interface.
Output queues Total number of output queues supported on the specified interface.
supported
Output queues in use Total number of output queues in use on the specified interface.
Egress queues Total number of egress queues supported on the specified interface.
supported
Egress queues in use Total number of egress queues in use on the specified interface.
Queue counters CoS queue number and its associated user-configured forwarding class name. Displayed on
(Ingress) IQ2 interfaces.

NOTE: This field is not supported on QFX5100, QFX5110, QFX5200, and QFX5210 switches
due to hardware limitations.

Burst size (Logical interfaces on IQ PICs only) Maximum number of bytes up to which the logical interface
can burst. The burst size is based on the shaping rate applied to the interface.
The following output fields are applicable to both interface component and Packet Forwarding component in the
show interfaces queue command:
Queue Queue number.
Forwarding classes Forwarding class name.

760
Queued Packets Number of packets queued to this queue.
NOTE: For Gigabit Ethernet IQ2 interfaces, the Queued Packets count is calculated by the
Junos OS interpreting one frame buffer as one packet. If the queued packets are very large
or very small, the calculation might not be completely accurate for transit traffic. The count
is completely accurate for traffic terminated on the router.
For rate-limited interfaces hosted on MICs or MPCs only, this statistic does not include traffic
dropped due to rate limiting. For more information, see “Additional Information” on page 756.
This field is not supported on EX Series switches due to hardware limitations.
Queued Bytes Number of bytes queued to this queue. The byte counts vary by interface hardware. For more
information, see Table 45 on page 763.
For rate-limited interfaces hosted on MICs or MPCs only, this statistic does not include traffic
dropped due to rate limiting. For more information, see “Additional Information” on page 756.
This field is not supported on EX Series switches due to hardware limitations.
Transmitted Packets Number of packets transmitted by this queue. When fragmentation occurs on the egress
interface, the first set of packet counters shows the postfragmentation values. The second
set of packet counters (displayed under the Packet Forwarding Engine Chassis Queues field)
shows the prefragmentation values.
NOTE: For Layer 2 statistics, see “Overhead for Layer 2 Statistics” on page 754
Transmitted Bytes Number of bytes transmitted by this queue. The byte counts vary by interface hardware. For
more information, see Table 45 on page 763.
NOTE: On MX Series routers, this number can be inaccurate when you issue the command
for a physical interface repeatedly and in quick succession, because the statistics for the child
nodes are collected infrequently. Wait ten seconds between successive iterations to avoid
this situation.
NOTE: For Layer 2 statistics, see “Overhead for Layer 2 Statistics” on page 754
761
Tail-dropped packets Number of packets dropped because of tail drop.
NOTE: Starting with Junos OS 18.3R1, the Tail-dropped packets counter is supported on
PTX Series Packet Transport Routers.
RL-dropped packets Number of packets dropped due to rate limiting.
For rate-limited interfaces hosted on MICs, MPCs, and Enhanced Queuing DPCs only, this
statistic is not included in the queued traffic statistics. For more information, see “Additional
Information” on page 756.
NOTE: The RL-dropped packets counter is not supported on the PTX Series Packet Transport
Routers, and is omitted from the output.
RL-dropped bytes Number of bytes dropped due to rate limiting.
For rate-limited interfaces hosted on MICs, MPCs, and Enhanced Queuing DPCs only, this
statistic is not included in the queued traffic statistics. For more information, see “Additional
Information” on page 756.
RED-dropped Number of packets dropped because of random early detection (RED).

packets
the total number of dropped packets is displayed. On all other M Series routers, the output
classifies dropped packets into the following categories:
• Low, non-TCP—Number of low-loss priority non-TCP packets dropped because of RED.
• Low, TCP—Number of low-loss priority TCP packets dropped because of RED.
• High, non-TCP—Number of high-loss priority non-TCP packets dropped because of RED.
• High, TCP—Number of high-loss priority TCP packets dropped because of RED.
• (MX Series routers with enhanced DPCs, and T Series routers with enhanced FPCs only)
The output classifies dropped packets into the following categories:
• Low—Number of low-loss priority packets dropped because of RED.
• Medium-low—Number of medium-low loss priority packets dropped because of RED.
• Medium-high—Number of medium-high loss priority packets dropped because of RED.
• High—Number of high-loss priority packets dropped because of RED.
762
RED-dropped bytes Number of bytes dropped because of RED. The byte counts vary by interface hardware. For
more information, see Table 45 on page 763.
only the total number of dropped bytes is displayed. On all other M Series routers, the
output classifies dropped bytes into the following categories:
• Low, non-TCP—Number of low-loss priority non-TCP bytes dropped because of RED.
• Low, TCP—Number of low-loss priority TCP bytes dropped because of RED.
• High, non-TCP—Number of high-loss priority non-TCP bytes dropped because of RED.
• High, TCP—Number of high-loss priority TCP bytes dropped because of RED.
Queue-depth bytes Displays queue-depth average, current, peak, and maximum values for RTP queues. Because
queue-depth values cannot be aggregated, displays the values for RTP queues regardless of
whether aggregate, remaining-traffic, or neither option is selected.
Peak (QFX5000 Series switches only) Diplays the peak buffer occupancy for the queue while
buffer-monitor-enable is enabled at the [edit chassis fpc slot-number traffic-manager] hierarchy
level.
Last-packet Starting with Junos OS Release 16.1, Last-packet enqueued output field is introduced. If
enqueued packet-timestamp is enabled for an FPC, shows the day, date, time, and year in the format
day-of-the-week month day-date hh:mm:ss yyyy when a packet was enqueued in the CoS queue.
When the timestamp is aggregated across all active Packet Forwarding Engines, the latest
timestamp for each CoS queue is reported.
Byte counts vary by interface hardware. Table 45 on page 763 shows how the byte counts on the outbound
interfaces vary depending on the interface hardware. Table 45 on page 763 is based on the assumption
that outbound interfaces are sending IP traffic with 478 bytes per packet.
763
Table 45: Byte Count by Interface Hardware
Interface Output
Hardware Level Byte Count Includes Comments
Gigabit Interface Queued: 490 bytes per packet, representing 478 bytes The 12 additional bytes
Ethernet IQ of Layer 3 packet + 12 bytes include 6 bytes for the
and IQE PICs destination MAC address +
Transmitted: 490 bytes per packet, representing 478
4 bytes for the VLAN +
bytes of Layer 3 packet + 12 bytes
2 bytes for the Ethernet
RED dropped: 496 bytes per packet representing 478 type.

For RED dropped, 6 bytes
are added for the source
MAC address.
Packet Queued: 478 bytes per packet, representing 478 bytes –

forwarding of Layer 3 packet
component
Transmitted: 478 bytes per packet, representing
478 bytes of Layer 3 packet
764
Table 45: Byte Count by Interface Hardware (continued)
Interface Output
Non-IQ PIC Interface T Series, TX Series, T1600, and MX Series routers: The Layer 2 overhead is 14
bytes for non-VLAN traffic
• Queued: 478 bytes of Layer 3 packet. and 18 bytes for VLAN
• Transmitted: 478 bytes of Layer 3 packet. traffic.
T4000 routers with Type 5 FPCs :
• Queued: 478 bytes of Layer 3 packet + the full Layer

2 overhead including 4 bytes CRC + the full Layer 1
overhead 8 bytes preamble + 12 bytes Inter frame
Gap.
• Transmitted: 478 bytes of Layer 3 packet + the full
Layer 2 overhead including 4 bytes CRC + the full
Layer 1 overhead 8 bytes preamble + 12 bytes
Interframe Gap.
M Series routers:
• Queued: 478 bytes of Layer 3 packet.

• Transmitted: 478 bytes of Layer 3 packet + the full
Layer 2 overhead.
PTX Series Packet Transport Routers:
• Queued: The sum of the transmitted bytes and the

RED dropped bytes.
• Transmitted: Full Layer 2 overhead (including all L2
encapsulation and CRC) + 12 inter-packet gap + 8 for
the preamble.
• RED dropped: Full Layer 2 overhead (including all L2
encapsulation and CRC) + 12 inter-packet gap + 8 for
the preamble (does not include the VLAN header or
MPLS pushed bytes).
765
Interface Output
IQ and IQE Interface Queued: 482 bytes per packet, representing 478 bytes The additional 4 bytes are
PICs with a of Layer 3 packet + 4 bytes for the Layer 2
SONET/SDH Point-to-Point Protocol
interface (PPP) header.
RED dropped: 482 bytes per packet, representing 478

Packet Queued: 478 bytes per packet, representing 478 bytes For transmitted packets, the
forwarding of Layer 3 packet additional 8 bytes includes
component 4 bytes for the PPP header
and 4 bytes for a cookie.
Non-IQ PIC Interface T Series, TX Series, T1600, and MX Series routers: For transmitted packets, the
with a additional 5 bytes includes
SONET/SDH • Queued: 478 bytes of Layer 3 packet. 4 bytes for the PPP header
interface • Transmitted: 478 bytes of Layer 3 packet. and 1 byte for the packet
M Series routers: loss priority (PLP).
• Queued: 478 bytes of Layer 3 packet.

• Transmitted: 483 bytes per packet, representing 478
• RED dropped: 478 bytes per packet, representing 478
bytes of Layer 3 packet
Interfaces Interface The default Frame Relay overhead is 7 bytes. If you

configured configure the Frame Check Sequence (FCS) to 4 bytes,
with Frame then the overhead increases to 10 bytes.
Relay
Encapsulation
766
Interface Output
1-port Interface Queued: 478 bytes of Layer 3 packet + the full Layer 2 The Layer 2 overhead is 18
10-Gigabit overhead including CRC. bytes for non-VLAN traffic
Ethernet IQ2 and 22 bytes for VLAN
Transmitted: 478 bytes of Layer 3 packet + the full Layer
and IQ2–E traffic.
2 overhead including CRC.
PICs
4-port 1G IQ2 Packet Queued: 478 bytes of Layer 3 packet. –

and IQ2-E forwarding
Transmitted: 478 bytes of Layer 3 packet.
PICs component
8-port 1G IQ2
and IQ2-E
PICs
Sample Output
show interfaces queue (Rate-Limited Interface on a Gigabit Ethernet MIC in an MPC)
The following example shows queue information for the rate-limited interface ge-4/2/0 on a Gigabit
Ethernet MIC in an MPC. For rate-limited queues for interfaces hosted on MICs or MPCs, rate-limit packet
drops occur prior to packet output queuing. In the command output, the nonzero statistics displayed in
the RL-dropped packets and RL-dropped bytes fields quantify the traffic dropped to rate-limit queue 0
output to 10 percent of 1 gigabyte (100 megabits) per second. Because the RL-dropped traffic is not
included in the Queued statistics, the statistics displayed for queued traffic are the same as the statistics
for transmitted traffic.
user@host> show interfaces queue ge-4/2/0

Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 131300649 141751 pps
Bytes : 11287964840 99793248 bps
Transmitted:
767
Packets : 131300649 141751 pps

Bytes : 11287964840 99793248 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
show interfaces queue (Aggregated Ethernet on a T320 Router)
The following example shows that the aggregated Ethernet interface, ae1, has traffic on queues af1 and
af12:
user@host> show interfaces queue ae1
Physical interface: ae1, Enabled, Physical link is Up

Interface index: 158, SNMP ifIndex: 33 Forwarding classes: 8 supported, 8 in use
Output queues: 8 supported, 8 in use
Queued:
Packets : 5 0 pps
Bytes : 242 0 bps
Transmitted:
Packets : 5 0 pps
Bytes : 242 0 bps
Queued:
Packets : 42603765 595484 pps
768
Bytes : 5453281920 609776496 bps

Transmitted:
Packets : 42603765 595484 pps
Bytes : 5453281920 609776496 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queue: 3, Forwarding classes: nc
Queued:
Packets : 45 0 pps
Bytes : 3930 0 bps
Transmitted:
Packets : 45 0 pps
Bytes : 3930 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
769

Queued:
Packets : 31296413 437436 pps
Bytes : 4005940864 447935200 bps
Transmitted:
Packets : 31296413 437436 pps
Bytes : 4005940864 447935200 bps
Queue: 7, Forwarding classes: nc2
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
show interfaces queue (Gigabit Ethernet on a T640 Router)
user@host> show interfaces queue

Output queues: 8 supported, 8 in use
Queued:
Packets : 13 0 pps
Bytes : 622 0 bps
Transmitted:
Packets : 13 0 pps
Bytes : 622 0 bps
770
Queued:
Packets : 1725947945 372178 pps
Bytes : 220921336960 381110432 bps
Transmitted:
Packets : 1725947945 372178 pps
Bytes : 220921336960 381110432 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 571 0 pps
Bytes : 49318 336 bps
Transmitted:
Packets : 571 0 pps
Bytes : 49318 336 bps
show interfaces queue aggregate (Gigabit Ethernet Enhanced DPC)
user@host> show interfaces queue ge-2/2/9 aggregate

Queued:
Packets : 148450735 947295 pps
Bytes : 8016344944 409228848 bps
Transmitted:
771
Packets : 76397439 487512 pps

Bytes : 4125461868 210602376 bps
Low : 72053285 459783 pps
High : 0 0 pps
Low : 3890877444 198626472 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 410278257 473940 pps
Bytes : 22156199518 204742296 bps
Transmitted:
Packets : 4850003 4033 pps
Bytes : 261900162 1742256 bps
Low : 405425693 469907 pps
High : 0 0 pps
772

Low : 21892988124 203000040 bps
High : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 76605230 485376 pps
Bytes : 5209211400 264044560 bps
Transmitted:
Packets : 76444631 484336 pps
Bytes : 5198235612 263478800 bps
Low : 160475 1040 pps
High : 0 0 pps
Low : 10912300 565760 bps
High : 0 0 bps
773
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 4836136 3912 pps
Bytes : 333402032 2139056 bps
Transmitted:
Packets : 3600866 1459 pps
Bytes : 244858888 793696 bps
Low : 1225034 2450 pps
High : 0 0 pps
Low : 83302312 1333072 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
774
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps

Queued:
Packets : 77059796 486384 pps
Bytes : 3544750624 178989576 bps
Transmitted:
Packets : 77059797 486381 pps
Bytes : 3544750670 178988248 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
775
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 4846580 3934 pps
Bytes : 222942680 1447768 bps
Transmitted:
Packets : 4846580 3934 pps
Bytes : 222942680 1447768 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
show interfaces queue (Gigabit Ethernet IQ2 PIC)
user@host> show interfaces queue ge-7/1/3

776

Interface index: 170, SNMP ifIndex: 70 Forwarding classes: 16 supported, 4 in
use Ingress queues: 4 supported, 4 in use
Queued:
Packets : 418390039 10 pps
Bytes : 38910269752 7440 bps
Transmitted:
Packets : 418390039 10 pps
Bytes : 38910269752 7440 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 451552 512 bps
Transmitted:
Bytes : 451552 512 bps
Forwarding classes: 16 supported, 4 in use Egress queues: 4 supported, 4 in use
777

Queued:
Bytes : 143292 0 bps
Transmitted:
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 6894286 7888 bps
Transmitted:
Bytes : 6894286 7888 bps
778


Queued:
Transmitted:
Low, non-TCP : 0 0 pps
Low, TCP : 0 0 pps
High, non-TCP : 0 0 pps
High, TCP : 0 0 pps
Low, non-TCP : 0 0 bps
Low, TCP : 0 0 bps
High, non-TCP : 0 0 bps
High, TCP : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low, TCP : 0 0 pps
High, TCP : 0 0 pps
Low, TCP : 0 0 bps
High, TCP : 0 0 bps
779
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low, TCP : 0 0 pps
High, TCP : 0 0 pps
Low, TCP : 0 0 bps
High, TCP : 0 0 bps
Queued:
Bytes : 13756799 9568 bps
Transmitted:
Bytes : 13756799 9568 bps
Low, TCP : 0 0 pps
High, TCP : 0 0 pps
Low, TCP : 0 0 bps
High, TCP : 0 0 bps
show interfaces queue both-ingress-egress (Gigabit Ethernet IQ2 PIC)
user@host> show interfaces queue ge-6/2/0 both-ingress-egress

780

Queued:
Packets : Not Available
Bytes : 0 0 bps
Transmitted:
Packets : 254 0 pps
Bytes : 16274 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
781
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 3 0 pps
Bytes : 126 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
782
Bytes : 3383717100 0 bps

Transmitted:
Bytes : 3383717100 0 bps
Queued:
Bytes : 3383716770 0 bps
Transmitted:
Bytes : 3383716770 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 3809052 232 bps
Transmitted:
Bytes : 3809052 232 bps
show interfaces queue ingress (Gigabit Ethernet IQ2 PIC)
user@host> show interfaces queue ge-6/2/0 ingress

783

Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 288 0 pps
Bytes : 18450 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
784
show interfaces queue egress (Gigabit Ethernet IQ2 PIC)
user@host> show interfaces queue ge-6/2/0 egress

Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 3 0 pps
Bytes : 126 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
785
Bytes : 0 0 bps
Queued:
Bytes : 3383717100 0 bps
Transmitted:
Bytes : 3383717100 0 bps
Queued:
Bytes : 3383716770 0 bps
Transmitted:
Bytes : 3383716770 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Bytes : 3819840 0 bps
Transmitted:
Bytes : 3819840 0 bps
786

show interfaces queue remaining-traffic (Gigabit Ethernet Enhanced DPC)
user@host> show interfaces queue ge-2/2/9 remaining-traffic

Queued:
Packets : 110208969 472875 pps
Bytes : 5951284434 204282000 bps
Transmitted:
Packets : 110208969 472875 pps
Bytes : 5951284434 204282000 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
787
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
788
Packets : 109355853 471736 pps

Bytes : 7436199152 256627968 bps
Transmitted:
Packets : 109355852 471736 pps
Bytes : 7436198640 256627968 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
789
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
show interfaces queue (Channelized OC12 IQE Type 3 PIC in SONET Mode)
user@host> show interfaces queue t3-1/1/0:7
Physical interface: t3-1/1/0:7, Enabled, Physical link is Up
Description: full T3 interface connect to 6ce13 t3-3/1/0:7 for FR testing - Lam
Queue: 0, Forwarding classes: DEFAULT

790
Queued:
Packets : 214886 13449 pps
Bytes : 9884756 5164536 bps
Transmitted:
Packets : 214886 13449 pps
Bytes : 9884756 5164536 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: REALTIME
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
791
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: PRIVATE
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps

792
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 3, Forwarding classes: CONTROL
Queued:
Packets : 60 0 pps
Bytes : 4560 0 bps
Transmitted:
Packets : 60 0 pps
Bytes : 4560 0 bps
Low : 0 0 pps
High : 0 0 pps
793
Low : 0 0 bps
High : 0 0 bps
Queue: 4, Forwarding classes: CLASS_B_OUTPUT
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
794
High : 0 0 bps
Queue: 5, Forwarding classes: CLASS_C_OUTPUT
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 6, Forwarding classes: CLASS_V_OUTPUT
Queued:
Packets : 0 0 pps
795
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 7, Forwarding classes: CLASS_S_OUTPUT, GETS
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
796
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 0, Forwarding classes: DEFAULT
Queued:
Packets : 371365 23620 pps
Bytes : 15597330 7936368 bps
Transmitted:
Packets : 371365 23620 pps
Bytes : 15597330 7936368 bps

797
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 1, Forwarding classes: REALTIME
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
798
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: PRIVATE
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
799
High : 0 0 bps
Queue: 3, Forwarding classes: CONTROL
Queued:
Bytes : 2641754 56 bps
Transmitted:
Bytes : 2641754 56 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 4, Forwarding classes: CLASS_B_OUTPUT
Queued:
800
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 5, Forwarding classes: CLASS_C_OUTPUT
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
801
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 6, Forwarding classes: CLASS_V_OUTPUT
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
802
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 7, Forwarding classes: CLASS_S_OUTPUT, GETS
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps

803
Low : 0 0 bps
High : 0 0 bps
show interfaces queue (QFX Series)
user@switch> show interfaces queue xe-0/0/15

Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Total-dropped packets: 0 0 pps
Total-dropped bytes : 0 0 bps
Queue: 3, Forwarding classes: fcoe
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
0 bps
Queue: 4, Forwarding classes: no-loss
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
804
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Queue: 8, Forwarding classes: mcast
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
show interfaces queue l2-statistics (lsq interface)
user@switch> show interfaces queue lsq-2/2/0.2 l2-statistics
Logical interface lsq-2/2/0.2 (Index 69) (SNMP ifIndex 1598)

Burst size: 0
Queued:
Packets : 1 0 pps
Bytes : 1001 0 bps
Transmitted:
Packets : 5 0 pps
Bytes : 1062 0 bps
805

Queued:
Packets : 1 0 pps
Bytes : 1500 0 bps
Transmitted:
Packets : 6 0 pps
Bytes : 1573 0 bps
Queue: 2, Forwarding classes: af
Queued:
Packets : 1 0 pps
Bytes : 512 0 bps
Transmitted:
Packets : 3 0 pps
Bytes : 549 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
=========
show interfaces queue lsq (lsq-ifd)
user@switch> show interfaces queue lsq-1/0/0
Logical interface lsq-1/0/0 (Index 348) (SNMP ifIndex 660)

Burst size: 0
806
Queued:
Bytes : 29622008 5145472 bps
Transmitted:
Bytes : 29622008 5145472 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue: 2, Forwarding classes: af
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
807
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queued:
Bytes : 11849123 2057600 bps
Transmitted:
Bytes : 11849123 2057600 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
show interfaces queue (Aggregated Ethernet on a MX series Router)

user@host> show interfaces queue ae0 remaining-traffic
Physical interface: ae0 , Enabled, Physical link is Up

808

Queued:
Packets : 16 0 pps
Bytes : 1896 0 bps
Transmitted:
Packets : 16 0 pps
Bytes : 1896 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue-depth bytes :
Average : 0
Current : 0
Peak : 0
Maximum : 119013376
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
809
High : 0 0 bps
Queue-depth bytes :
Average : 0
Current : 0
Peak : 0
Maximum : 32768
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue-depth bytes :
Average : 0
Current : 0
Peak : 0
Maximum : 32768
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Low : 0 0 pps
810
High : 0 0 pps
Low : 0 0 bps
High : 0 0 bps
Queue-depth bytes :
Average : 0
Current : 0
Peak : 0
Maximum : 6258688
show interfaces queue ge-0/0/0 (EX2200 Switch)

user@switch> show interfaces queue ge–0/0/0

Queued:
Transmitted:
Packets : 0
Bytes : 0
Tail-dropped packets : 0
Queued:
Transmitted:
Packets : 0
Bytes : 0
Queued:
Transmitted:
Packets : 0
Bytes : 0
Queued:
Transmitted:
Packets : 0
811
Bytes : 0
show interfaces queue xe-6/0/39 (Line Card with Oversubscribed Ports in an EX8200 Switch)
user@switch> show interfaces queue xe-6/0/39

Transmitted:
Packets : 337069086018
Bytes : 43144843010304
PFE chassis queues: 1 supported, 1 in use
Transmitted:
Packets : 0
Bytes : 0
Queued:
Transmitted:
Packets : 334481399932
Bytes : 44151544791024
Queued:
Transmitted:
Packets : 0
Bytes : 0
Queue: 2, Forwarding classes: mcast-be
Queued:
Transmitted:
Packets : 274948977
Bytes : 36293264964
Queue: 4, Forwarding classes: mcast-ef
Queued:
Transmitted:
812
Packets : 0
Bytes : 0
Queued:
Transmitted:
Packets : 0
Bytes : 0
Queue: 6, Forwarding classes: mcast-af
Queued:
Transmitted:
Packets : 0
Bytes : 0
Queued:
Transmitted:
Packets : 46714
Bytes : 6901326

Queued:
Transmitted:
Packets : 739338141426
Bytes : 94635282101928
RED-dropped packets : 5606426444
Low : 5606426444
High : 0
RED-dropped bytes : 683262846464
Low : 683262846464
High : 0
Queued:
Transmitted:
Packets : 0
Bytes : 0
Low : 0
813
High : 0
Low : 0
High : 0
Queue: 2, Forwarding classes: mcast-be
Queued:
Transmitted:
Packets : 0
Bytes : 0
Low : 0
High : 0
Low : 0
High : 0
Queue: 4, Forwarding classes: mcast-ef
Queued:
Transmitted:
Packets : 0
Bytes : 0
Low : 0
High : 0
Low : 0
High : 0
Queued:
Transmitted:
Packets : 0
Bytes : 0
Low : 0
High : 0
Low : 0
High : 0
Queue: 6, Forwarding classes: mcast-af
Queued:
Transmitted:
Packets : 0
814
Bytes : 0
Low : 0
High : 0
Low : 0
High : 0
Queued:
Transmitted:
Packets : 97990
Bytes : 14987506
Low : 0
High : 0
Low : 0
High : 0
show interfaces queue xe-0/0/2 buffer-occupancy (QFX5000 Series switch)

user@switch> show interfaces queue xe-0/0/2 buffer-occupancy

Queue: 0, Forwarding classes: fc0
Queue-depth bytes :
Peak : 1786720
Queue: 3, Forwarding classes: fcoe
Queue-depth bytes :
Peak : 0
Queue: 4, Forwarding classes: no-loss
Queue-depth bytes :
Peak : 0
Queue-depth bytes :
815
Peak : 416
Queue: 8, Forwarding classes: mcast
Queue-depth bytes :
Peak : 0
816
show subscribers
Syntax
show subscribers
<detail | extensive | terse>
<aci-interface-set-name aci-interface-set-name>
<address address>
<agent-circuit-identifier agent-circuit-identifier>
<agent-remote-identifier agent-remote-identifier>
<aggregation-interface-set-name interface-set-name>
<client-type client-type>
<count>
<id session-id <accounting-statistics>>
<interface interface <accounting-statistics>>
<logical-system logical-system>
<mac-address mac-address>
<physical-interface physical-interface-name>
<profile-name profile-name>
<routing-instance routing-instance>
<stacked-vlan-id stacked-vlan-id>
<subscriber-state subscriber-state>
<user-name user-name>
<vci vci-identifier>
<vpi vpi-identifier>
<vlan-id vlan-id>
Release Information
Command introduced in Junos OS Release 9.3.
client-type, mac-address, subscriber-state, and extensive options introduced in Junos OS Release 10.2.
count option usage with other options introduced in Junos OS Release 10.2.
Options aci-interface-set-name and agent-circuit-identifier introduced in Junos OS Release 12.2.
The physical-interface and user-name options introduced in Junos OS Release 12.3.
Options vci and vpi introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
Options vci and vpi supported in Junos OS Release 13.2 and later releases. (Not supported in Junos OS
Release 13.1.)
Enhanced subscriber management supported in Junos OS Release 15.1R3 on MX Series routers.
accounting-statistics option added in Junos OS Release 15.1R3 and 17.4R1 on MX Series routers.
aggregation-interface-set-name option added in Junos OS Release 18.4R1 on MX Series routers.
Description
817
Display information for active subscribers.
Options
detail | extensive | terse—(Optional) Display the specified level of output.
aci-interface-set-name—(Optional) Display all dynamic subscriber sessions that use the specified agent
circuit identifier (ACI) interface set. Use the ACI interface set name generated by the router, such as
aci-1003-ge-1/0/0.4001, and not the actual ACI value found in the DHCP or PPPoE control packets.
address—(Optional) Display subscribers whose IP address matches the specified address. You must specify
the IPv4 or IPv6 address prefix without a netmask (for example, 192.0.2.0). If you specify the IP address
as a prefix with a netmask (for example, 192.0.2.0/32), the router displays a message that the IP address
is invalid, and rejects the command.
agent-circuit-identifier—(Optional) Display all dynamic subscriber sessions whose ACI value matches the
specified string. You can specify either the complete ACI string or a substring. To specify a substring,
you must enter characters that form the beginning of the string, followed by an asterisk (*) as a wildcard
to substitute for the remainder of the string. The wildcard can be used only at the end of the specified
substring; for example:
user@host1> show subscribers agent-circuit-identifier substring*
Junos OS Release Substring Support
Junos OS Release 13.3R1 You can specify a substring without a wildcard.
Starting in Junos OS Release 14.1R1 You must specify the complete ACI string; you cannot specify
a wildcard.
Starting in Junos OS Release 15.1R7, 16.1R7, 16.2R3, You can specify a substring, but you must include the wildcard
17.1R3, 17.2R3, 17.3R3, 17.4R2, 18.1R2, 18.2R1 character at the end of the substring.
agent-remote-identifier—(Optional) Display all dynamic subscriber sessions whose ARI value matches the
specified string. You must specify the complete ACI string; you cannot specify a wildcard.
aggregation-interface-set-name interface-set-name—(Optional) Display summary information for the

specified aggregation node interface set, including interface, VLAN ID, username and LS:RI.
client-type—(Optional) Display subscribers whose client type matches one of the following client types:
• dhcp—DHCP clients only.
• dotlx—Dotlx clients only.
• essm—ESSM clients only.

818
• fixed-wireless-access—Fixed wireless access clients only.
• fwauth—FwAuth (authenticated across a firewall) clients only.
• l2tp—L2TP clients only.
• mlppp—MLPPP clients only.
• ppp—PPP clients only.
• pppoe—PPPoE clients only.
• static—Static clients only.
• vlan—VLAN clients only.
• vlan-oob—VLAN out-of-band (ANCP-triggered) clients only.
• vpls-pw—VPLS pseudowire clients only.
• xauth—Xauth clients only.
count—(Optional) Display the count of total subscribers and active subscribers for any specified option.
You can use the count option alone or with the address, client-type, interface, logical-system,
mac-address, profile-name, routing-instance, stacked-vlan-id, subscriber-state, or vlan-id options.
id session-id—(Optional) Display a specific subscriber session whose session ID matches the specified
subscriber ID. You can display subscriber IDs by using the show subscribers extensive or the show
subscribers interface extensive commands.
id session-id accounting-statistics—(Optional) Display accurate subscriber accounting statistics for a

subscriber session with the specified ID. Requires the actual-transmit-statistics statement to be
configured in the dynamic profile for the dynamic logical interface. If the statement is not configured,
a value of 0 is displayed for accounting statistics.
interface—(Optional) Display subscribers whose interface matches the specified interface.
interface accounting-statistics—(Optional) Display subscriber accounting statistics for the specified interface.
Requires the actual-transmit-statistics statement to be configured in the dynamic profile for the
dynamic logical interface.
logical-system—(Optional) Display subscribers whose logical system matches the specified logical system.
mac-address—(Optional) Display subscribers whose MAC address matches the specified MAC address.
physical-interface-name—(M120, M320, and MX Series routers only) (Optional) Display subscribers whose
physical interface matches the specified physical interface.
profile-name—(Optional) Display subscribers whose dynamic profile matches the specified profile name.
routing-instance—(Optional) Display subscribers whose routing instance matches the specified routing
instance.
819
stacked-vlan-id—(Optional) Display subscribers whose stacked VLAN ID matches the specified stacked
VLAN ID.
subscriber-state—(Optional) Display subscribers whose subscriber state matches the specified subscriber
state (ACTIVE, CONFIGURED, INIT, TERMINATED, or TERMINATING).
user-name—(M120, M320, and MX Series routers only) (Optional) Display subscribers whose username
matches the specified subscriber name.
vci-identifier—(MX Series routers with MPCs and ATM MICs with SFP only) (Optional) Display active ATM
subscribers whose ATM virtual circuit identifier (VCI) matches the specified VCI identifier. The range
of values is 0 through 255.
vpi-identifier—(MX Series routers with MPCs and ATM MICs with SFP only) (Optional) Display active ATM
subscribers whose ATM virtual path identifier (VPI) matches the specified VPI identifier. The range of
values is 0 through 65,535.
vlan-id—(Optional) Display subscribers whose VLAN ID matches the specified VLAN ID, regardless of
whether the subscriber uses a single-tagged or double-tagged VLAN. For subscribers using a
double-tagged VLAN, this option displays subscribers where the inner VLAN tag matches the specified
VLAN ID. To display only subscribers where the specified value matches only double-tagged VLANs,
use the stacked-vlan-id stacked-vlan-id option to match the outer VLAN tag.
NOTE: Because of display limitations, logical system and routing instance output values are
truncated when necessary.

view
show subscribers summary

Verifying and Managing Configurations for Dynamic VLANs Based on Access-Line Identifiers

show subscribers (IPv4) on page 831
show subscribers (IPv6) on page 831
show subscribers (IPv4 and IPv6 Dual Stack) on page 831
show subscribers (Single Session DHCP Dual Stack) on page 831
820
show subscribers (Single Session DHCP Dual Stack detail) on page 832
show subscribers (LNS on MX Series Routers) on page 832
show subscribers (L2TP Switched Tunnels) on page 833
show subscribers aggregation-interface-set-name on page 833
show subscribers client-type dhcp detail on page 833
show subscribers client-type dhcp detail (DHCPv6) on page 834
show subscribers client-type dhcp extensive on page 835
show subscribers client-type fixed-wireless-access on page 835
show subscribers client-type fixed-wireless-access detail (Detail) on page 836
show subscribers client-type vlan-oob detail on page 836
show subscribers count on page 837
show subscribers address detail (IPv6) on page 837
show subscribers detail (IPv4) on page 838
show subscribers detail (IPv6) on page 838
show subscribers detail (pseudowire Interface for GRE Tunnel) on page 839
show subscribers detail (IPv6 Static Demux Interface) on page 839
show subscribers detail (L2TP LNS Subscribers on MX Series Routers) on page 840
show subscribers detail (L2TP Switched Tunnels) on page 840
show subscribers detail (Tunneled Subscriber) on page 841
show subscribers detail (IPv4 and IPv6 Dual Stack) on page 841
show subscribers detail (ACI Interface Set Session) on page 842
show subscribers detail (PPPoE Subscriber Session with ACI Interface Set) on page 843
show subscribers extensive on page 843
show subscribers extensive (Aggregation Node Interface Set and DSL Forum Attributes) on page 844
show subscribers extensive (Passive Optical Network Circuit Interface Set) on page 845
show subscribers extensive (DNS Addresses from Access Profile or Global Configuration) on page 846
show subscribers extensive (DNS Addresses from RADIUS) on page 847
show subscribers extensive (IPv4 DNS Addresses from RADIUS, IPv6 from Access Profile or Global
Configuration) on page 847
show subscribers extensive (RPF Check Fail Filter) on page 848
show subscribers extensive (L2TP LNS Subscribers on MX Series Routers) on page 848
show subscribers extensive (IPv4 and IPv6 Dual Stack) on page 849
show subscribers extensive (ADF Rules ) on page 850
show subscribers extensive (Effective Shaping-Rate) on page 851
show subscribers extensive (PPPoE Subscriber Access Line Rates on page 851
show subscribers extensive (Subscriber Session Using PCEF Profile) on page 853
show subscribers aci-interface-set-name detail (Subscriber Sessions Using Specified ACI Interface
Set) on page 854
show subscribers agent-circuit-identifier detail (Subscriber Sessions Using Specified ACI
Substring) on page 855
show subscribers id accounting-statistics on page 856
show subscribers interface accounting-statistics on page 856
show subscribers interface extensive on page 857
821
show subscribers logical-system terse on page 858

show subscribers physical-interface count on page 858
show subscribers routing-instance inst1 count on page 859
show subscribers stacked-vlan-id detail on page 859
show subscribers stacked-vlan-id vlan-id detail (Combined Output) on page 859
show subscribers stacked-vlan-id vlan-id interface detail (Combined Output for a Specific
Interface) on page 859
show subscribers user-name detail on page 860
show subscribers vlan-id on page 860
show subscribers vlan-id detail on page 860
show subscribers vpi vci extensive (PPPoE-over-ATM Subscriber Session) on page 861
show subscribers address detail (Enhanced Subscriber Management) on page 861
Output Fields
Table 46 on page 821 lists the output fields for the show subscribers command. Output fields are listed in
the approximate order in which they appear.
Table 46: show subscribers Output Fields
Interface Interface associated with the subscriber. The router or switch displays subscribers whose
interface matches or begins with the specified interface.
The * character indicates a continuation of addresses for the same session.
IP Address/VLAN ID Subscriber IP address or VLAN ID associated with the subscriber in the form tpid.vlan-id
No IP address or VLAN ID is assigned to an L2TP tunnel-switched session. For these subscriber

sessions the value is Tunnel-switched.
User Name Name of subscriber.
LS:RI Logical system and routing instance associated with the subscriber.
Type Subscriber client type (DHCP, FWA, GRE, L2TP, PPP, PPPoE, STATIC-INTERFACE, VLAN).
IP Address Subscriber IPv4 address.

822
Table 46: show subscribers Output Fields (continued)
IP Netmask Subscriber IP netmask.
(MX Series) This field displays 255.255.255.255 by default. For tunneled or terminated PPP
subscribers only, this field displays the actual value of Framed-IP-Netmask when the
SDB_FRAMED_PROTOCOL attribute in the session database is equal to
AUTHD_FRAMED_PROTOCOL_PPP. This occurs in the use case where the LNS generates
access-internal routes when it receives Framed-IP-Netmask from RADIUS during authorization.
When it receives Framed-Pool from RADIUS, the pool mask is ignored and the default /32
mask is used.
Primary DNS IP address of primary DNS server.

Address
This field is displayed with the extensive option only when the address is provided by RADIUS.
Secondary DNS IP address of secondary DNS server.

Address
IPv6 Primary DNS IPv6 address of primary DNS server.

Address
IPv6 Secondary DNS IPv6 address of secondary DNS server.

Address
Domain name server IP addresses for the DNS server, displayed in order of configuration.
inet
This field is displayed with the extensive option only when the addresses are derived from
the access profile or the global access configuration.
Domain name server IPv6 addresses for the DNS server, displayed in order of configuration.
inet6
This field is displayed with the extensive option only when the addresses are derived from
the access profile or the global access configuration.
Primary WINS IP address of primary WINS server.

Address
Secondary WINS IP address of secondary WINS server.

Address
IPv6 Address Subscriber IPv6 address, or multiple addresses.

823
IPv6 Prefix Subscriber IPv6 prefix. If you are using DHCPv6 prefix delegation, this is the delegated prefix.
IPv6 User Prefix IPv6 prefix obtained through NDRA.
IPv6 Address Pool Subscriber IPv6 address pool. The IPv6 address pool is used to allocate IPv6 prefixes to the
DHCPv6 clients.
IPv6 Network Prefix Length of the network portion of the IPv6 address.
Length
IPv6 Prefix Length Length of the subscriber IPv6 prefix.
Logical System Logical system associated with the subscriber.
Routing Instance Routing instance associated with the subscriber.
Interface (Enhanced subscriber management for MX Series routers) Name of the enhanced subscriber
management logical interface, in the form demux0.nnnn (for example, demux0.3221225472),
to which access-internal and framed subscriber routes are mapped.
Interface Type Whether the subscriber interface is Static or Dynamic.

824
Interface Set Internally generated name of the dynamic ACI or ALI interface set used by the subscriber
session. The prefix of the name indicates the string received in DHCP or PPPoE control packets
on which the interface set is based. For ALI interface sets, the prefix indicates that the value
is configured as a trusted option to identify the subscriber line.
The name of the interface set uses one of the following prefixes:
• aci—ACI; for example, aci-1033-demux0.3221225524. This is the only prefix allowed for
ACI interface sets.
• ari—ARI; for example, ari-1033-demux0.3221225524.
• aci+ari—Both the ACI and ARI; for example, aci+ari-1033-demux0.3221225524.
• noids—Neither the ACI nor the ARI were received; for example,
noids-1033-demux0.3221225524.
NOTE: ACI interface sets are configured with the agent-circuit-identifier autoconfiguration
stanza. ALI interface sets are configured with the line-identity autoconfiguration stanza.
Besides dynamic ACI and ALI interface sets, this field can be an interface set based on a
substring of the ARI string. This occurs when the dynamic profile includes the predefined
variable $junos-pon-id-interface-set-name, and the profile is applied for a passive optical
network (PON). The ARI string is inserted by the optical line terminal (OLT). The final substring
in the string, unique for the PON, identifies individual subscriber circuits, and is used as the
name of the interface set.
Interface Set Type Interface type of the ACI interface set: Dynamic. This is the only ACI interface set type currently
supported.
Interface Set Session Identifier of the dynamic ACI interface set entry in the session database.
ID
Underlying Interface Name of the underlying interface for the subscriber session.
Dynamic Profile Dynamic profile used for the subscriber.

Name
Dynamic Profile Version number of the dynamic profile used for the subscriber.
Version
MAC Address MAC address associated with the subscriber.
State Current state of the subscriber session (Init, Configured, Active, Terminating, Tunneled).
825
L2TP State Current state of the L2TP session, Tunneled or Tunnel-switched. When the value is
Tunnel-switched, two entries are displayed for the subscriber; the first entry is at the LNS
interface on the LTS and the second entry is at the LAC interface on the LTS.
Tunnel switch Profile Name of the L2TP tunnel switch profile that initiates tunnel switching.
Name
Local IP Address IP address of the local gateway (LAC).
Remote IP Address IP address of the remote peer (LNS).
PFE Flow ID Forwarding flow identifier.
VLAN Id VLAN ID associated with the subscriber in the form tpid.vlan-id.
Stacked VLAN Id Stacked VLAN ID associated with the subscriber in the form tpid.vlan-id.
RADIUS Accounting RADIUS accounting ID associated with the subscriber.

ID
Agent Circuit ID For the dhcp client type, option 82 agent circuit ID associated with the subscriber. The ID is
displayed as an ASCII string unless the value has nonprintable characters, in which case it is
displayed in hexadecimal format.
For the vlan-oob client type, the agent circuit ID or access-loop circuit identifier that identifies
the subscriber line based on the subscriber-facing DSLAM interface on which the subscriber
request originates.
Agent Remote ID For the dhcp client type, option 82 agent remote ID associated with the subscriber. The ID is
displayed as an ASCII string unless the value has nonprintable characters, in which case it is
displayed in hexadecimal format.
For the vlan-oob client type, the agent remote ID or access-loop remote identifier that identifies
the subscriber line based on the NAS-facing DSLAM interface on which the subscriber request
originates.
826
Aggregation Value of the $junos-aggregation-interface-set-name predefined variable; one of the following:

Interface-set Name
• When the hierarchical-access-network-detection option is configured for the access lines
and the value of the Access-Aggregation-Circuit-ID-ASCII attribute (TLV 0x0003) received
either in the ANCP Port Up message or PPPoE PADR IA tags begins with a # character,
then the variable takes the value of the remainder of the string after the # character.
• When the hierarchical-access-network-detection option is not configured, or if the sting
does not begin with the # character, then the variable takes the value specified with the
predefined-variable-defaults statement.
Accounting Statistics Actual transmitted subscriber accounting statistics by session ID or interface. Service accounting
statistics are not included. These statistics do not include overhead bytes or dropped packets;
they are the accurate statistics used by RADIUS. The statistics are counted when the
actual-transmit-statistics statement is included in the dynamic profile.
DHCP Relay IP IP address used by the DHCP relay agent.

Address
ATM VPI (MX Series routers with MPCs and ATM MICs with SFP only) ATM virtual path identifier (VPI)
on the subscriber’s physical interface.
ATM VCI (MX Series routers with MPCs and ATM MICs with SFP only) ATM virtual circuit identifier
(VCI) for each VPI configured on the subscriber interface.
Login Time Date and time at which the subscriber logged in.
DHCPV6 Options len = number of hex values in the message. The hex values specify the type, length, value
(TLV) for DHCPv6 options.
Server DHCP len = number of hex values in the message. The hex values specify the type, length, value
Options (TLV) for DHCP options.
Server DHCPV6 len = number of hex values in the message. The hex values specify the type, length, value
Options (TLV) for DHCPv6 options.
DHCPV6 Header len = number of hex values in the message. The hex values specify the type, length, value
(TLV) for DHCPv6 options.
Effective Actual downstream traffic shaping rate for the subscriber, in kilobits per second.
shaping-rate
827
IPv4 Input Service Input service set in access dynamic profile.

Set
IPv4 Output Service Output service set in access dynamic profile.

Set
PCEF Profile PCEF profile in access dynamic profile.
PCEF Rule/Rulebase PCC rule or rulebase used in dynamic profile.
Dynamic Values for variables that are passed into the dynamic profile from RADIUS.
configuration
Service activation Time at which the first family in this service became active.
time
IPv4 rpf-check Fail Name of the filter applied by the dynamic profile to IPv4 packets that fail the RPF check.
Filter Name
IPv6 rpf-check Fail Name of the filter applied by the dynamic profile to IPv6 packets that fail the RPF check.
Filter Name
DHCP Options len = number of hex values in the message. The hex values specify the type, length, value
(TLV) for DHCP options, as defined in RFC 2132.
Session ID ID number for a subscriber session.
Underlying Session For DHCPv6 subscribers on a PPPoE network, displays the session ID of the underlying PPPoE
ID interface.
Service Sessions Number of service sessions (that is, a service activated using RADIUS CoA) associated with
the subscribers.
Service Session ID ID number for a subscriber service session.
Service Session Service session profile name.

Name
Session Timeout Number of seconds of access provided to the subscriber before the session is automatically
(seconds) terminated.
828
Idle Timeout Number of seconds subscriber can be idle before the session is automatically terminated.
(seconds)
IPv6 Delegated Name of the pool used for DHCPv6 prefix delegation.
Address Pool
IPv6 Delegated Length of the prefix configured for the IPv6 delegated address pool.
Network Prefix
Length
IPv6 Interface Address assigned by the Framed-Ipv6-Prefix AAA attribute. This field is displayed only when
Address the predefined variable $junos-ipv6-address is used in the dynamic profile.
IPv6 Framed Interface ID assigned by the Framed-Interface-Id AAA attribute.

Interface Id
ADF IPv4 Input Filter Name assigned to the Ascend-Data-Filter (ADF) interface IPv4 input filter (client or service
Name session). The filter name is followed by the rules (in hexadecimal format) associated with the
ADF filter and the decoded rule in Junos OS filter style.
ADF IPv4 Output Name assigned to the Ascend-Data-Filter (ADF) interface IPv4 output filter (client or service
Filter Name session). The filter name is followed by the rules (in hexadecimal format) associated with the
ADF IPv6 Input Filter Name assigned to the Ascend-Data-Filter (ADF) interface IPv6 input filter (client or service
Name session). The filter name is followed by the rules (in hexadecimal format) associated with the
ADF IPv6 Output Name assigned to the Ascend-Data-Filter (ADF) interface IPv6 output filter (client or service
Filter Name session). The filter name is followed by the rules (in hexadecimal format) associated with the
IPv4 Input Filter Name assigned to the IPv4 input filter (client or service session).
Name
IPv4 Output Filter Name assigned to the IPv4 output filter (client or service session).
Name
IPv6 Input Filter Name assigned to the IPv6 input filter (client or service session).
Name
829
IPv6 Output Filter Name assigned to the IPv6 output filter (client or service session).
Name
IFL Input Filter Name Name assigned to the logical interface input filter (client or service session).
IFL Output Filter Name assigned to the logical interface output filter (client or service session).
Name
DSL type PPPoE subscriber’s access line type reported by the PPPoE intermediate agent in a PADI or
PADO packet in the Vendor-Specific-Tags TLV in subattribute DSL-Type (0x0091). The DSL
type is one of the following types: ADSL, ADSL2, ADSL2+, OTHER, SDSL, VDSL, or VDSL2.
Frame/Cell Mode Mode type of the PPPoE subscriber’s access line determined by the PPPoE daemon based on
the received subattribute DSL-Type (0x0091):
• Cell—When the DSL line type is one of the following: ADSL, ADSL2, or ADSL2+.
• Frame—When the DSL line type is one of the following: OTHER, SDSL, VDSL, or VDSL2.
The value is stored in the subscriber session database.
Overhead accounting Number of bytes added to or subtracted from the actual downstream cell or frame overhead
bytes to account for the technology overhead of the DSL line type. The value is determined by the
PPPoE daemon based on the received subattribute DSL-Type (0x0091). The value is stored
in the subscriber session database.
Actual upstream data Unadjusted upstream data rate for the PPPoE subscriber’s access line reported by the PPPoE
rate intermediate agent in a PADI or PADO packet in the Vendor-Specific-Tags TLV in subattribute
Actual-Net-Data-Rate-Upstream (0x0081).
Actual downstream Unadjusted downstream data rate for the PPPoE subscriber’s access line reported by the
data rate PPPoE intermediate agent in a PADI or PADO packet in the Vendor-Specific-Tags TLV in
subattribute Actual-Net-Data-Rate-Downstream (0x0082).
Adjusted Adjusted downstream data rate for the PPPoE subscriber’s access line, calculated by the PPPoE
downstream data daemon and stored in the subscriber session database.
rate
Adjusted upstream Adjusted upstream data rate for the PPPoE subscriber’s access line, calculated by the PPPoE
data rate daemon and stored in the subscriber session database.
830
Local TEID-U Tunnel endpoint identifier on the BNG for the GTP-U user plane tunnel to the eNodeB. The
identifier is allocated by the BNG.
A fully qualified local TEID-C consists of this identifier and the GTPU Tunnel Local IP address
value.
Local TEID-C Tunnel endpoint identifier on the BNG for the GTP-C control plane tunnel to the MME. The
identifier is allocated by the BNG.
A fully qualified local TEID-C consists of this identifier and the GTPC Local IP address value.
Remote TEID-U Tunnel endpoint identifier on the eNodeB for the GTP-U user plane tunnel to the BNG. The
identifier is allocated by the eNodeB.
A fully qualified remote TEID-U consists of this identifier and the GTPU Tunnel Remote IP
address value.
Remote TEID-C Tunnel endpoint identifier on the MME for the GTP-C control plane tunnel to the BNG. The
identifier is allocated by the MME.
A fully qualified remote TEID-C consists of this identifier and the GTPC Remote IP address
value.
GTPU Tunnel IP address of the S1-U interface on the eNodeB for the GTP-U tunnel endpoint.
Remote IP address
A fully qualified remote TEID-U consists of this address and the Remote TEID-U value.
GTPU Tunnel Local IP address of the S1-U interface on the BNG for the GTP-U tunnel endpoint.
IP address
A fully qualified local TEID-U consists of this address and the Local TEID-U value
GTPC Remote IP IP address of the S11 interface on the MME for the GTP-C tunnel endpoint.
address
A fully qualified remote TEID-C consists of this address and the Remote TEID-C value.
GTPC Local IP IP address of the S11 interface on the BNG for the GTP-C tunnel endpoint.
address
A fully qualified local TEID-C consists of this address and the Local TEID-C value.
Access Point Name Access point name (APN) for the user equipment. The APN corresponds to the connection
and service parameters that the subscriber’s mobile device can use for connecting to the
carrier’s gateway to the Internet.
831
Sample Output
show subscribers (IPv4)
user@host> show subscribers
Interface IP Address/VLAN ID User Name LS:RI

ge-1/3/0.1073741824 10 default:default
demux0.1073741824 203.0.113.10 WHOLESALER-CLIENT default:default
demux0.1073741825 203.0.113.3 RETAILER1-CLIENT test1:retailer1
show subscribers (IPv6)


ge-1/0/0.0 2001:db8:c0:0:0:0/74 WHOLESALER-CLIENT default:default
* 2001:db8:1/128 subscriber-25 default:default
show subscribers (IPv4 and IPv6 Dual Stack)


demux0.1073741834 0x8100.1002 0x8100.1
default:default
demux0.1073741835 0x8100.1001 0x8100.1
default:default
pp0.1073741836 203.0.113.13 dualstackuser1@example1.com
default:ASP-1
* 2001:db8:1::/48
* 2001:db8:1:1::/64
pp0.1073741837 203.0.113.33 dualstackuser2@example1.com
default:ASP-1
* 2001:db8:1:2:5::/64
show subscribers (Single Session DHCP Dual Stack)

832

demux0.1073741364 192.168.10.10 dual-stack-retail35
default:default
2001:db8::100:0:0:0/74
default:default
2001:db8:3ffe:0:4::/64
show subscribers (Single Session DHCP Dual Stack detail)

user@host> show subscribers id 27 detail
Type: DHCP
User Name: dual-stack-retail33
IP Address: 10.10.0.53
IPv6 Address: 2001:db8:3000:0:0:8003::2
IPv6 Prefix: 2001:db8:3ffe:0:4::/64
Logical System: default
Routing Instance: default
Interface: ae0.3221225472
Interface type: Static
Underlying Interface: ae0.3221225472
Dynamic Profile Name: dhcp-retail-18
MAC Address: 00:00:5E:00:53:02
State: Active
DHCP Relay IP Address: 10.10.0.1
Radius Accounting ID: 27
Session ID: 27
PFE Flow ID: 2
Stacked VLAN Id: 2000
VLAN Id: 1
Login Time: 2014-05-15 10:12:10 PDT
DHCP Options: len 60
00 08 00 02 00 00 00 01 00 0a 00 03 00 01 00 00 64 01 01 02
00 06 00 04 00 03 00 19 00 03 00 0c 00 00 00 00 00 00 00 00
00 00 00 00 00 19 00 0c 00 00 00 00 00 00 00 00 00 00 00 00
show subscribers (LNS on MX Series Routers)


si-4/0/0.1 192.0.2.0 user@example.com default:default
833
show subscribers (L2TP Switched Tunnels)


si-2/1/0.1073741842 Tunnel-switched user@example.com default:default
si-2/1/0.1073741843 Tunnel-switched user@example.com default:default
show subscribers aggregation-interface-set-name

user@host> show subscribers aggregation-interface-set-name FRA*
Interface IP Address/VLAN ID User Name

LS:RI
ge-1/0/0.3221225472 50 ancp
default:isp1-subscriber
show subscribers client-type dhcp detail

user@host> show subscribers client-type dhcp detail
Type: DHCP
IP Address: 203.0.113.29
IP Netmask: 255.255.0.0
Interface: demux0.1073744127
Interface type: Dynamic
Dynamic Profile Name: dhcp-demux
MAC Address: 00:00:5e:00:53:98
State: Active
Radius Accounting ID: user :2304
Login Time: 2009-08-25 14:43:52 PDT
Type: DHCP
IP Address: 203.0.113.27
IP Netmask: 255.255.0.0
834

Dynamic Profile Name: dhcp-demux-prof
MAC Address: 00:00:5e:00:53:f3
State: Active
Radius Accounting ID: 1234 :2560
Login Time: 2009-08-25 14:43:56 PDT
show subscribers client-type dhcp detail (DHCPv6)

user@host> show subscribers client-type dhcp detail
Type: DHCP
User Name: DEFAULTUSER
IPv6 Address: 2001:db8::2
IPv6 Prefix: 2001:db8:1::/64
Underlying Interface: demux0.3221225602
Dynamic Profile Name: client-profile
MAC Address: 00:00:5E:00:53:01
State: Active
Session ID: 142
PFE Flow ID: 148
Stacked VLAN Id: 1
VLAN Id: 1
Login Time: 2018-03-29 12:27:38 EDT
00 08 00 02 00 00 00 01 00 0e 00 01 00 01 22 4f d0 33 00 11
01 00 00 01 00 03 00 0c 00 00 00 0a 00 04 9d 40 00 07 62 00
00 19 00 0c 00 00 00 0b 00 04 9d 40 00 07 62 00
Server DHCPV6 Options: len 94
00 0a 00 06 11 22 33 44 55 66 00 11 00 09 00 00 0c 4c 00 02
00 01 aa 00 11 00 20 00 00 0a 4c 00 02 00 02 32 33 00 03 00
03 34 35 36 00 05 00 06 31 32 33 34 35 36 00 06 00 01 31 00
11 00 09 00 00 0b 4c 00 02 00 01 bb 00 11 00 12 00 00 0d e9
00 01 00 03 aa bb cc 00 02 00 03 dd ee cc
DHCPV6 Header: len 4
01 fc e4 96
835
show subscribers client-type dhcp extensive

user@host> show subscribers client-type dhcp extensive
Type: DHCP
User Name: user
IP Netmask: 255.0.0.0
IPv6 Address: 2001:db8:3::103
IPv6 Prefix: 2001:db8::/68
Domain name server inet6: 2001:db8:1 abcd::2
Interface: ge-0/0/0.0
Underlying Interface: ge-0/0/0.0
MAC Address: 00:00:5e:00:53:01
State: Configured
Session ID: 10
PFE Flow ID: 2
VLAN Id: 100
Agent Circuit ID: ge-0/0/0:100
Agent Remote ID: ge-0/0/0:100
Login Time: 2017-05-23 12:52:22 IST
DHCPV6 Options: len 69
00 01 00 0e 00 01 00 01 59 23 e3 31 00 10 94 00 00 01 00 08
00 02 00 00 00 19 00 29 00 00 00 00 00 04 9d 40 00 07 62 00
00 1a 00 19 00 09 3a 80 00 27 8d 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
Server DHCP Options: len 13
3a 04 00 00 00 ff 00 3b 04 00 00 0f 00
Server DHCPV6 Options: len 8
00 0a 00 04 ab cd ef ab
DHCPV6 Header: len 4
01 00 00 04
IP Address Pool: al_pool30
IPv6 Address Pool: ia_na_pool
IPv6 Delegated Address Pool: prefix_delegate_pool
show subscribers client-type fixed-wireless-access

user@host> show subscribers client-type fixed-wireless-access
836
Interface IP Address/VLAN ID User Name

LS:RI
ps1.3221225472 192.0.2.10 505024101215074
default:default
ps1.3221225473 192.0.2.11 505024101215075
default:default
show subscribers client-type fixed-wireless-access detail (Detail)

user@host> show subscribers client-type fixed-wireless-access detail
Type: FWA
User Name: 505024101215074
IP Netmask: 255.255.0.0
Interface: ps1.3221225472
Dynamic Profile Name: fwa-profile
State: Active
Session ID: 1
PFE Flow ID: 11
Login Time: 2019-04-10 14:10:12 PDT
Local TEID-U: 1
Local TEID-C: 1
Remote TEID-U: 2000000
Remote TEID-C: 1000000
GTPU Tunnel Remote IP Address: 203.0.113.1.3
GTPU Tunnel Local IP Address: 203.0.113.2.5
GTPC Remote IP Address: 203.0.113.1.2
GTPC Local IP Address: 203.0.113.1.1
Access Point Name: user21
show subscribers client-type vlan-oob detail

user@host> show subscribers client-type vlan-oob detail
Type: VLAN-OOB
User Name: L2WS.line-aci-1.line-ari-1
Routing Instance: ISP1
837

Underlying Interface: ge-1/0/0
Dynamic Profile Name: Prof_L2WS
Dynamic Profile Version: 1
State: Active
Session ID: 77
VLAN Id: 126
Core-Facing Interface: ge-2/1/1
VLAN Map Id: 6
Inner VLAN Map Id: 2001
Agent Circuit ID: line-aci-1
Agent Remote ID: line-ari-1
Login Time: 2013-10-29 14:43:52 EDT
show subscribers count

user@host> show subscribers count
Total Subscribers: 188, Active Subscribers: 188
show subscribers address detail (IPv6)

user@host> show subscribers address 203.0.113.137 detail
Type: PPPoE
User Name: pppoeTerV6User1Svc
IP Address: 203.0.113.137
IPv6 User Prefix: 2001:db8:0:c88::/32
Interface: pp0.1073745151
Dynamic Profile Name: pppoe-client-profile
MAC Address: 00:00:5e:00:53:53
Session Timeout (seconds): 31622400
Idle Timeout (seconds): 86400
State: Active
Radius Accounting ID: example demux0.8201:6544
Session ID: 6544
Agent Circuit ID: ifl3720
838
Agent Remote ID: ifl3720

Login Time: 2012-05-21 13:37:27 PDT
Service Sessions: 1
show subscribers detail (IPv4)

Type: DHCP
IP Address: 203.0.113.29
IP Netmask: 255.255.0.0
Primary DNS Address: 192.0.2.0
Secondary DNS Address: 192.0.2.1
Primary WINS Address: 192.0.2.3
Secondary WINS Address: 192.0.2.4
MAC Address: 00:00:5e:00:53:98
State: Active
Radius Accounting ID: example :2304
Idle Timeout (seconds): 600
Login Time: 2009-08-25 14:43:52 PDT
35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 08 33 04 00 00
00 3c 0c 15 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 36 2f
33 2d 37 2d 30 37 05 01 06 0f 21 2c
Service Sessions: 2
show subscribers detail (IPv6)

Type: DHCP
User Name: pd-user1
IPv6 Prefix: 2001:db8:ffff:1::/32
MAC Address: 00:00:5e:00:53:03
839
State: Active
Session ID: 1
Login Time: 2011-08-25 12:12:26 PDT
00 08 00 02 00 00 00 01 00 0a 00 03 00 01 00 51 ff ff 00 03
00 06 00 02 00 19 00 19 00 0c 00 00 00 00 00 00 00 00 00 00
00 00
show subscribers detail (pseudowire Interface for GRE Tunnel)


ps0.3221225484 192.0.2.2
ps0.3221225485 192.0.2.3
demux0.3221225486 1 default:default
demux0.3221225487 1 default:default
demux0.3221225488 198.51.0.1 default:default
demux0.3221225489 198.51.0.2 default:default
show subscribers detail (IPv6 Static Demux Interface)

Type: STATIC-INTERFACE
User Name: user@example.com
IPv6 Prefix: 2001:db8:3:4:5:6:7:aa/32
Interface: demux0.1
Dynamic Profile Name: junos-default-profile
State: Active
Login Time: 2010-05-18 14:33:56 EDT
840
show subscribers detail (L2TP LNS Subscribers on MX Series Routers)

Type: L2TP
IP Address: 203.0.113.58
IP Netmask: 255.255.0.0
Interface: si-5/2/0.1073749824
Dynamic Profile Name: dyn-lns-profile2
State: Active
Session ID: 8001
Login Time: 2011-04-25 20:27:50 IST
show subscribers detail (L2TP Switched Tunnels)

Type: L2TP
Interface: si-2/1/0.1073741842
Dynamic Profile Name: dyn-lts-profile
State: Active
L2TP State: Tunnel-switched
Tunnel switch Profile Name: ce-lts-profile
Local IP Address: 203.0.113.51
Remote IP Address: 192.0.2.0
Session ID: 21
Login Time: 2013-01-18 03:01:11 PST
Type: L2TP
Interface: si-2/1/0.1073741843
841
Dynamic Profile Name: dyn-lts-profile

State: Active
L2TP State: Tunnel-switched
Tunnel switch Profile Name: ce-lts-profile
Local IP Address: 203.0.113.31
Remote IP Address: 192.0.2.1
Session ID: 22
Login Time: 2013-01-18 03:01:14 PST
show subscribers detail (Tunneled Subscriber)

Type: PPPoE
User Name: user1@example.com
Interface: pp0.1
State: Active, Tunneled
show subscribers detail (IPv4 and IPv6 Dual Stack)

Type: VLAN
Dynamic Profile Name: svlanProfile
State: Active
Session ID: 1
Stacked VLAN Id: 0x8100.1001
VLAN Id: 0x8100.1
Login Time: 2011-11-30 00:18:04 PST
Type: PPPoE
User Name: dualstackuser1@example1.com
IP Address: 203.0.113.13
IPv6 Prefix: 2001:db8:1::/32
IPv6 User Prefix: 2001:db8:1:1::/32
842
Routing Instance: ASP-1

Dynamic Profile Name: dualStack-Profile1
MAC Address: 00:00:5e:00:53:02
State: Active
Session ID: 2
Login Time: 2011-11-30 00:18:05 PST
Type: DHCP
IPv6 Prefix: 2001:db8:1::/32
MAC Address: 00:00:5e:00:53:02
State: Active
Radius Accounting ID: test :3
Session ID: 3
Underlying Session ID: 2
Login Time: 2011-11-30 00:18:35 PST
00 08 00 02 0b b8 00 01 00 0a 00 03 00 01 00 00 64 03 01 02
00 06 00 02 00 19 00 19 00 0c 00 00 00 00 00 00 00 00 00 00
00 00
show subscribers detail (ACI Interface Set Session)

Type: VLAN
Interface: ge-1/0/0
Interface Set: aci-1001-ge-1/0/0.2800
Interface Set Session ID: 0
Dynamic Profile Name: aci-vlan-set-profile-2
State: Active
Session ID: 1
843
Agent Circuit ID: aci-ppp-dhcp-20

Login Time: 2012-05-26 01:54:08 PDT
show subscribers detail (PPPoE Subscriber Session with ACI Interface Set)
Type: PPPoE
User Name: ppphint2
IP Address: 203.0.113.15
Interface Set: aci-1001-demux0.1073741824
Interface Set Type: Dynamic
Dynamic Profile Name: aci-vlan-pppoe-profile
MAC Address: 00:00:5e:00:53:02
State: Active
Session ID: 3
Agent Circuit ID: aci-ppp-dhcp-dvlan-50
Login Time: 2012-03-07 13:46:53 PST
show subscribers extensive

user@host> show subscribers extensive
Type: DHCP
User Name: pd-user1
IPv6 Prefix: 2001:db8:ffff:1::/32
MAC Address: 00:00:5e:00:53:03
State: Active
Session ID: 1
Login Time: 2011-08-25 12:12:26 PDT
844

00 08 00 02 00 00 00 01 00 0a 00 03 00 01 00 51 ff ff 00 03
00 06 00 02 00 19 00 19 00 0c 00 00 00 00 00 00 00 00 00 00
00 00
IPv6 Address Pool: pd_pool
IPv6 Network Prefix Length: 48
show subscribers extensive (Aggregation Node Interface Set and DSL Forum Attributes)
Type: VLAN-OOB
User Name: ancp
Routing Instance: isp1-subscriber
Interface: ge-1/0/0.3221225472
Interface Set: FRA-DPU-C-100
Core IFL Name: ge-1/0/4.0
Dynamic Profile Name: Prof_L2BSA
State: Active
Session ID: 1
PFE Flow ID: 13
VLAN Id: 50
VLAN Map Id: 20
Inner VLAN Tag Protocol Id: 0x88a8
Agent Circuit ID: circuit 201
Agent Remote ID: remote-id
Aggregation Interface-set Name: FRA-DPU-C-100
Login Time: 2018-05-29 08:43:42 EDT
Accounting interval: 72000
Dynamic configuration:
junos-cos-scheduler-map: 100m
junos-inner-vlan-tag-protocol-id: 0x88a8
junos-vlan-map-id: 20
Type: PPPoE
IP Address: 192.85.128.1
IP Netmask: 255.255.255.255
845
Interface Set: ge-1/0/0
Dynamic Profile Name: pppoe-client-profile-with-cos
MAC Address: 00:10:94:00:00:03
State: Active
Session ID: 3
PFE Flow ID: 16
Stacked VLAN Id: 50
VLAN Id: 7
Aggregation Interface-set Name: FRA-DPU-C-100
Login Time: 2018-05-29 08:43:45 EDT
IP Address Pool: pool-1
DSL type: G.fast
Frame/cell mode: Frame
Overhead accounting bytes: 10
Actual upstream data rate: 100000 kbps
Actual downstream data rate: 200000 kbps
Calculated downstream data rate: 180000 kbps
Calculated upstream data rate: 90000 kbps
Adjusted upstream data rate: 80000 kbps
Adjusted downstream data rate: 160000 kbps
DSL Line Attributes
Actual upstream data rate: 100000
Actual downstream data rate: 200000
DSL type: G.fast
Access Aggregation Circuit ID: #FRA-DPU-C-100
Attribute type: 0xAA, Attribute length: 4
198 51 100 78
show subscribers extensive (Passive Optical Network Circuit Interface Set)

user@host> show subscribers client-type dhcp extensive
Type: DHCP
IP Address: 192.0.2.136
IP Netmask: 255.255.0.0
846

Interface Set: otl01.xyz101-202
Dynamic Profile Name: dhcp-profile
MAC Address: 00:00:5e:00:53:02
State: Active
Radius Accounting ID: user :19
Session ID: 19
VLAN Id: 1100
Agent Remote ID: ABCD01234|100M|AAAA01234|otl01.xyz101-202
Login Time: 2017-03-29 10:30:46 PDT

35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 02 33 04 00 00
17 70 0c 15 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 32 2f
32 2d 31 2d 31 37 05 01 06 0f 21 2c 52 2b 02 29 41 42 43 44
30 31 32 33 34 7c 31 30 30 4d 7c 41 41 41 41 30 31 32 33 34
7c 6f 74 6c 30 31 2e 78 79 7a 31 30 31 2d 32 30 32
IP Address Pool: POOL-V4
show subscribers extensive (DNS Addresses from Access Profile or Global Configuration)
Type: DHCP
User Name: test-user@example-com
IP Address: 192.0.2.119
IP Netmask: 255.255.255.255
Domain name server inet: 198.51.100.1 198.51.100.2
IPv6 Address: 2001:db8::1:11
Domain name server inet6: 2001:db8:5001::12 2001:db8:3001::12
MAC Address: 00:00:5E:00:53:00
State: Active
Session ID: 5
Login Time: 2017-01-31 11:16:21 IST
847

35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 03 33 04 00 00
00 3c 0c 16 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 35 2f
31 32 2d 30 2d 30 37 05 01 06 0f 21 2c
IP Address Pool: v4-pool
show subscribers extensive (DNS Addresses from RADIUS)

Type: DHCP
IP Address: 192.0.2.119
IP Netmask: 255.255.255.255
IPv6 Primary DNS Address: 2001:db8:5001::12
IPv6 Secondary DNS Address: 2001:db8:3001::12
MAC Address: 00:00:5E:00:53:00
State: Active
Session ID: 5
Login Time: 2017-01-31 11:16:21 IST
35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 03 33 04 00 00
00 3c 0c 16 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 35 2f
31 32 2d 30 2d 30 37 05 01 06 0f 21 2c
show subscribers extensive (IPv4 DNS Addresses from RADIUS, IPv6 from Access Profile or Global
Configuration)
Type: DHCP
IP Address: 192.0.2.119
848
IP Netmask: 255.255.255.255
Domain name server inet6: 2001:db8:5001::12 2001:db8:3001::12
MAC Address: 00:00:5E:00:53:00
State: Active
Session ID: 5
Login Time: 2017-01-31 11:16:21 IST
35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 03 33 04 00 00
00 3c 0c 16 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 35 2f
31 32 2d 30 2d 30 37 05 01 06 0f 21 2c
show subscribers extensive (RPF Check Fail Filter)

...
Type: VLAN
Interface: ae0.1073741824
Dynamic Profile Name: vlan-prof
State: Active
Session ID: 9
VLAN Id: 100
Login Time: 2011-08-26 08:17:00 PDT
IPv4 rpf-check Fail Filter Name: rpf-allow-dhcp
IPv6 rpf-check Fail Filter Name: rpf-allow-dhcpv6
...
show subscribers extensive (L2TP LNS Subscribers on MX Series Routers)

849
Type: L2TP
IP Address: 203.0.113.58
IP Netmask: 255.255.0.0
Interface: si-5/2/0.1073749824
Dynamic Profile Name: dyn-lns-profile2
State: Active
Session ID: 8001
Login Time: 2011-04-25 20:27:50 IST
IPv4 Input Filter Name: classify-si-5/2/0.1073749824-in
IPv4 Output Filter Name: classify-si-5/2/0.1073749824-out
show subscribers extensive (IPv4 and IPv6 Dual Stack)

Type: VLAN
Dynamic Profile Name: svlanProfile
State: Active
Session ID: 1
VLAN Id: 0x8100.1
Login Time: 2011-11-30 00:18:04 PST
Type: PPPoE
User Name: dualstackuser1@example1.com
IP Address: 203.0.113.13
IPv6 Prefix: 2001:db8:1::/32
IPv6 User Prefix: 2001:db8:1:1::/32
Dynamic Profile Name: dualStack-Profile1
MAC Address: 00:00:5e:00:53:02
850
State: Active
Session ID: 2
Login Time: 2011-11-30 00:18:05 PST
IPv6 Delegated Network Prefix Length: 48
IPv6 Interface Address: 2001:db8:2016:1:1::1/64
IPv6 Framed Interface Id: 1:1:2:2
IPv4 Input Filter Name: FILTER-IN-pp0.1073741825-in
IPv4 Output Filter Name: FILTER-OUT-pp0.1073741825-out
IPv6 Input Filter Name: FILTER-IN6-pp0.1073741825-in
IPv6 Output Filter Name: FILTER-OUT6-pp0.1073741825-out
Type: DHCP
IPv6 Prefix: 2001:db8:1::/32
MAC Address: 00:00:5e:00:53:02
State: Active
Radius Accounting ID: test :3
Session ID: 3
Underlying Session ID: 2
Login Time: 2011-11-30 00:18:35 PST
00 08 00 02 0b b8 00 01 00 0a 00 03 00 01 00 00 64 03 01 02
00 06 00 02 00 19 00 19 00 0c 00 00 00 00 00 00 00 00 00 00
00 00
IPv6 Delegated Network Prefix Length: 48
show subscribers extensive (ADF Rules )

...
Service Session ID: 12
Service Session Name: SERVICE-PROFILE
State: Active
Family: inet
ADF IPv4 Input Filter Name: __junos_adf_12-demux0.3221225474-inet-in
Rule 0: 010101000b0101020b020200201811
from {
source-address 203.0.113.232;
851
destination-address 198.51.100.0/24;
protocol 17;
}
then {
accept;
}
show subscribers extensive (Effective Shaping-Rate)

Type: VLAN
Interface Set: ifset-1
Underlying Interface: ae1
Dynamic Profile Name: svlan-dhcp-test
State: Active
Session ID: 1
VLAN Id: 0x8100.201
Login Time: 2011-11-30 00:18:04 PST
Effective shaping-rate: 31000000k
...
show subscribers extensive (PPPoE Subscriber Access Line Rates

Type: PPPoE
IP Address: 198.51.100.1
IP Netmask: 255.255.255.255
Dynamic Profile Name: pppoe-client-profile-with-cos
MAC Address: 00:00:5e:00:53:02
State: Active
852
Session ID: 4
PFE Flow ID: 14
Stacked VLAN Id: 40
VLAN Id: 1
Agent Circuit ID: circuit0
Agent Remote ID: remote0
Login Time: 2017-04-06 15:52:32 PDT
User Name: DAVE-L2BSA-SERVICE

Routing Instance: isp-1-subscriber
Interface: ge-1/2/4.3221225472
Interface Set: ge-1/2/4
Core IFL Name: ge-1/3/4.0
Dynamic Profile Name: L2BSA-88a8-400LL1300VO
State: Active
Session ID: 1
PFE Flow ID: 14
VLAN Id: 13
VLAN Map Id: 102
Agent Circuit ID: circuit-aci-3
Agent Remote ID: remote49-3
Login Time: 2017-04-05 16:59:29 EDT
Service Sessions: 4
IFL Input Filter Name: L2BSA-CP-400LL1300VO-ge-1/2/4.3221225472-in
IFL Output Filter Name: L2BSA-CP-400LL1300VO-ge-1/2/4.3221225472-out
DSL type: VDSL
Frame/Cell Mode: Frame
Overhead accounting bytes: -10
Actual upstream data rate: 1024 kbps
Actual downstream data rate: 4096 kbps
Adjusted downstream data rate: 3686 kbps
Adjusted upstream data rate: 922 kbps
junos-vlan-map-id: 102
Service Session Name: SRL-L1
State: Active
Family: inet, inet6
853
IFL Input Filter Name: L2BSA-FWF-in-10048-ge-1/2/4.3221225472-in

IFL Output Filter Name: L2BSA-FWF-out-25088-ge-1/2/4.3221225472-out
Service Activation time: 2017-04-05 16:59:30 EDT
l2bsa-fwf-in: L2BSA-FWF-in-10048
l2bsa-fwf-out: L2BSA-FWF-out-25088
rldown: 25088
rlup: 10048
show subscribers extensive (Subscriber Session Using PCEF Profile)

Type: VLAN
Dynamic Profile Name: svlan-dhcp
State: Active
Session ID: 59
PFE Flow ID: 71
VLAN Id: 0x8100.2
Login Time: 2017-03-28 08:23:08 PDT
Type: DHCP
User Name: pcefuser
Dynamic Profile Name: dhcp-client-prof
MAC Address: 00:00:5e:00:53:01
State: Active
Session ID: 60
PFE Flow ID: 73
Stacked VLAN Id: 1
VLAN Id: 2
854
Login Time: 2017-03-28 08:23:08 PDT

Service Sessions: 1
DHCP Options: len 9
35 01 01 37 04 01 03 3a 3b
IP Address Pool: pool-ipv4
IPv4 Input Service Set: tdf-service-set
IPv4 Output Service Set: tdf-service-set
PCEF Profile: pcef-prof-1
PCEF Rule/Rulebase: default
junos-input-service-filter: svc-filt-1
junos-input-service-set: tdf-service-set
junos-output-service-filter: svc-filt-1
junos-output-service-set: tdf-service-set
junos-pcef-profile: pcef-prof-1
junos-pcef-rule: default

Service Session Name: pcef-serv-prof
State: Active
Family: inet
IPv4 Input Service Set: tdf-service-set
IPv4 Output Service Set: tdf-service-set
PCEF Profile: pcef-prof-1
PCEF Rule/Rulebase: limit-fb
Service Activation time: 2017-03-28 08:31:19 PDT
pcef-prof: pcef-prof-1
pcef-rule1: limit-fb
svc-filt: svc-filt-1
svc-set: tdf-service-set
show subscribers aci-interface-set-name detail (Subscriber Sessions Using Specified ACI Interface Set)
user@host> show subscribers aci-interface-set-name aci-1003-ge-1/0/0.4001 detail
Type: VLAN
Interface: ge-1/0/0.
Dynamic Profile Name: aci-vlan-set-profile
State: Active
855
Session ID: 13
Agent Circuit ID: aci-ppp-vlan-10
Login Time: 2012-03-12 10:41:56 PDT
Type: PPPoE
User Name: ppphint2
IP Address: 203.0.113.17
MAC Address:
State: Active
Session ID: 14
Login Time: 2012-03-12 10:41:57 PDT
show subscribers agent-circuit-identifier detail (Subscriber Sessions Using Specified ACI Substring)
user@host> show subscribers agent-circuit-identifier aci-ppp-vlan detail
Type: VLAN
Interface: ge-1/0/0.
Dynamic Profile Name: aci-vlan-set-profile
State: Active
Session ID: 13
Login Time: 2012-03-12 10:41:56 PDT
Type: PPPoE
User Name: ppphint2
IP Address: 203.0.113.17
856

MAC Address: 00:00:5e:00:53:52
State: Active
Session ID: 14
Login Time: 2012-03-12 10:41:57 PDT
show subscribers id accounting-statistics

user@host> show subscribers id 601 accounting-statistics
Session ID: 601

Accounting Statistics:
Input packets: 5263
IPv6:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
show subscribers interface accounting-statistics

user@host> show subscribers interface pp0.3221226949 accounting-statistics
Session ID: 501

Input packets: 5263
IPv6:
857
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Session ID: 502

Input bytes : 87654
Input packets: 3322
IPv6:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Session ID: 503

Input packets: 7448
IPv6:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
show subscribers interface extensive

user@host> show subscribers interface demux0.1073741826 extensive
Type: VLAN
User Name: user@test.example.com
Routing Instance: testnet
Dynamic Profile Name: profile-vdemux-relay-23qos
MAC Address: 00:00:5e:00:53:04
State: Active
Session ID: 12
858

VLAN Id: 0x8100.2902
Login Time: 2011-10-20 16:21:59 EST
Type: DHCP
User Name: user@test.example.com
IP Netmask: 255.255.255.0
Routing Instance: testnet
MAC Address: 00:00:5e:00:53:04
State: Active
Session ID: 21
Login Time: 2011-10-20 16:24:33 EST
Service Sessions: 2

Service Session Name: SUB-QOS
State: Active

Service Session Name: service-cb-content
State: Active
IPv4 Input Filter Name: content-cb-in-demux0.1073741826-in
IPv4 Output Filter Name: content-cb-out-demux0.1073741826-out
show subscribers logical-system terse

user@host> show subscribers logical-system test1 terse

show subscribers physical-interface count

user@host> show subscribers physical-interface ge-1/0/0 count
Total subscribers: 3998, Active Subscribers: 3998

859
show subscribers routing-instance inst1 count

user@host> show subscribers routing-instance inst1 count
Total Subscribers: 188, Active Subscribers: 183
show subscribers stacked-vlan-id detail

user@host> show subscribers stacked-vlan-id 101 detail
Type: VLAN
Interface: ge-1/2/0.1073741824
Dynamic Profile Name: svlan-prof
State: Active
VLAN Id: 0x8100.100
Login Time: 2009-03-27 11:57:19 PDT
show subscribers stacked-vlan-id vlan-id detail (Combined Output)

user@host> show subscribers stacked-vlan-id 101 vlan-id 100 detail
Type: VLAN
Interface: ge-1/2/0.1073741824
State: Active
VLAN Id: 0x8100.100
Login Time: 2009-03-27 11:57:19 PDT
show subscribers stacked-vlan-id vlan-id interface detail (Combined Output for a Specific Interface)
user@host> show subscribers stacked-vlan-id 101 vlan-id 100 interface ge-1/2/0.* detail
Type: VLAN
Interface: ge-1/2/0.1073741824
State: Active
860
VLAN Id: 0x8100.100

Login Time: 2009-03-27 11:57:19 PDT
show subscribers user-name detail

user@host> show subscribers user-name larry1 detail
Type: DHCP
User Name: larry1
IP Address: 203.0.113.37
IP Netmask: 255.255.0.0
Dynamic Profile Name: foo
MAC Address: 00:00:5e:00:53:01
State: Active
Session ID: 1
Login Time: 2011-11-07 08:25:59 PST
35 01 01 39 02 02 40 3d 07 01 00 10 94 00 00 01 33 04 00 00
00 3c 0c 15 63 6c 69 65 6e 74 5f 50 6f 72 74 20 2f 2f 32 2f
37 2d 30 2d 30 37 05 01 06 0f 21 2c
show subscribers vlan-id

user@host> show subscribers vlan-id 100
Interface IP Address User Name

ge-1/0/0.1073741824
ge-1/2/0.1073741825
show subscribers vlan-id detail

user@host> show subscribers vlan-id 100 detail
Type: VLAN
Interface: ge-1/0/0.1073741824
Dynamic Profile Name: vlan-prof-tpid
861
State: Active
VLAN Id: 100
Login Time: 2009-03-11 06:48:54 PDT
Type: VLAN
Interface: ge-1/2/0.1073741825
Dynamic Profile Name: vlan-prof-tpid
State: Active
VLAN Id: 100
Login Time: 2009-03-11 06:48:54 PDT
show subscribers vpi vci extensive (PPPoE-over-ATM Subscriber Session)

user@host> show subscribers vpi 40 vci 50 extensive
Type: PPPoE
User Name: testuser
IP Address: 203.0.113.2
IP Netmask: 255.255.0.0
Interface: pp0.0
MAC Address: 00:00:5e:00:53:02
State: Active
Session ID: 2
ATM VPI: 40
ATM VCI: 50
Login Time: 2012-12-03 07:49:26 PST
IP Address Pool: pool_1
IPv6 Framed Interface Id: 200:65ff:fe23:102
show subscribers address detail (Enhanced Subscriber Management)

user@host> show subscribers address 203.0.113.111 detail
Type: DHCP
User Name: simple_filters_service
IP Address: 203.0.113.111
862

MAC Address: 00:00:5e:00:53:0f
State: Active
Session ID: 11
PFE Flow ID: 15
Stacked VLAN Id: 210
VLAN Id: 209
Login Time: 2014-03-24 12:53:48 PDT
Service Sessions: 1
DHCP Options: len 3
35 01 01

Config Guide Hierarchical Cos

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Config Guide Hierarchical Cos

Uploaded by

Copyright:

Available Formats

®

Hierarchical Class of Service User Guide

Juniper Networks, Inc.

YEAR 2000 NOTICE

END USER LICENSE AGREEMENT

Documentation and Release Notes | xiv

Using the Examples in This Manual | xiv

Merging a Full Example | xv

Merging a Snippet | xvi

Documentation Conventions | xvi

Documentation Feedback | xix

Requesting Technical Support | xix

Self-Help Online Tools and Resources | xx

Creating a Service Request with JTAC | xx

1 Hierarchical Class of Service

Hierarchical Class of Service Overview | 2

Hierarchical Class of Service Network Scenarios | 6

Understanding Hierarchical Scheduling | 7

Hierarchical Scheduling Terminology | 8

Scheduler Node-Level Designations in Hierarchical Scheduling | 8

Hierarchical Scheduling at Non-Leaf Nodes | 9

Priority Propagation in Hierarchical Scheduling | 10

Configuring Hierarchical Schedulers for CoS | 13

Hierarchical Schedulers and Traffic Control Profiles | 14

Example: Building a Four-Level Hierarchy of Schedulers | 16

Configuring the Interface Sets | 17

Configuring the Interfaces | 17

Configuring the Traffic Control Profiles | 18

Configuring the Schedulers | 19

Configuring the Drop Profiles | 20

Configuring the Scheduler Maps | 20

Applying the Traffic Control Profiles | 21

Understanding Scheduling and Shaping of Traffic Routed to GRE Tunnels | 22

Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs | 43

Understanding Hierarchical Scheduling for MIC and MPC Interfaces | 46

Scheduler Node Scaling for MIC and MPC Interfaces | 47

Hierarchical Scheduling Priority Levels for MIC and MPC Interfaces | 47

Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces | 49

Queuing Models Supported for MIC and MPC Interfaces | 52

Limited Scale Per-Unit Queuing MPCs | 52

Hierarchical Queuing MICs and MPCs | 52

Scheduler Node Levels for MIC and MPC Interfaces | 53

Scheduler Node Levels for Per-Unit Queuing MPCs | 53

Scheduler Node Levels for Hierarchical Queuing MICs and MPCs | 54

Queue Scaling for MPCs | 55

Managing Remaining Queues | 56

Jitter Reduction in Hierarchical CoS Queues | 58

Queue Jitter as a Function of the Maximum Number of Queues | 58

Default Maximum Queues for Hierarchical Queuing MICs and MPCs | 58

Shaping Rate Granularity as a Function of the Rate Wheel Update Period | 59

Example: Reducing Jitter in Hierarchical CoS Queues | 61

Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview | 68

Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces | 69

Example: Configuring Scheduling Modes on Aggregated Interfaces | 70

Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip | 76

2 Hierarchical CoS for Subscriber Management

Hierarchical Class of Service for Subscriber Management Overview | 80

Understanding Hierarchical CoS for Subscriber Interfaces | 81

Two-Level Hierarchical Scheduling | 82

Three-Level Hierarchical Scheduling | 84

Interface Hierarchy Versus CoS Hierarchy | 86

Four-Level Hierarchical Scheduling | 87

Hardware Requirements for Dynamic Hierarchical CoS | 89